[SERVER-21289] Make use of the "View Logs" link for performance tests Created: 09/Oct/15 Updated: 14/Apr/16 Resolved: 14/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chung-yen Chang | Assignee: | David Daly |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Performance E (01/11/16), Performance F (02/01/16) | ||||
| Participants: | |||||
| Description |
|
For all performance tests in projects (mongo perf, system performance and longevity), the "View Logs" links on the top right corner return "404 page not found". It would be very helpful to have those links show some more information on why a test is marked failed. Currently a test can fail due to comparison against 1) last commit, 2) 7-days ago or 3) baseline. Being able to know which was the case without having to go through the entire log would be very nice. One of the most straightforward things to do is to have all links pointing to the output from analysis script. It would be nice to have some way to differentiate individual tests but this is definitely a good starting point. |
| Comments |
| Comment by David Daly [ 14/Jan/16 ] |
|
This is a duplicate for SERVER-20410 |