[CDRIVER-1112] Upload test results to Evergreen Created: 12/Feb/16 Updated: 10/Aug/16 Resolved: 16/Feb/16 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Hannes Magnusson | Assignee: | Hannes Magnusson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | C Driver in Evergreen | ||||||||
| Description |
|
https://github.com/evergreen-ci/evergreen/wiki/Project-Files#attachresults Evergreen supports attaching test results and shows pretty statistics and fluffy boxes from that info. Would be nice to see which tests are generally failing like this. Should also be able to give indication if we are getting slower or faster etc |
| Comments |
| Comment by Hannes Magnusson [ 16/Feb/16 ] |
|
Closing this. One improvement would be to change the testname in the logfile as Evergreen currently treats it as a directory/filename combination and only shows the trailing path. |
| Comment by Githook User [ 16/Feb/16 ] |
|
Author: {u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}Message: This isn't unix timestamp, but its only used for calculating how |
| Comment by Githook User [ 13/Feb/16 ] |
|
Author: {u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}Message: This allows us to always submit test results as per |
| Comment by Githook User [ 12/Feb/16 ] |
|
Author: {u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}Message: Only the basics included so far |
| Comment by Githook User [ 12/Feb/16 ] |
|
Author: {u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}Message: Now they match the Evergreen test results format |
| Comment by A. Jesse Jiryu Davis [ 12/Feb/16 ] |
|
This would be great. I think we need to fix whatever's wrong with the "fork" test option first, so the suite can recover from a failed test instead of aborting. |