-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cdash_analyze_and_report.py: Write test data to file #304
Labels
Comments
bartlettroscoe
added a commit
to bartlettroscoe/TriBITS
that referenced
this issue
Feb 27, 2020
bartlettroscoe
added a commit
to bartlettroscoe/TriBITS
that referenced
this issue
Feb 27, 2020
I also changed formatting of another option to improve maintainability.
bartlettroscoe
added a commit
to bartlettroscoe/TriBITS
that referenced
this issue
Feb 27, 2020
I think this is correct. Now I just need to check this to be sure.
bartlettroscoe
added a commit
to bartlettroscoe/TriBITS
that referenced
this issue
Feb 27, 2020
bartlettroscoe
added a commit
to bartlettroscoe/TriBITS
that referenced
this issue
Feb 27, 2020
bartlettroscoe
added a commit
that referenced
this issue
Feb 27, 2020
bartlettroscoe
added a commit
that referenced
this issue
Feb 27, 2020
Needed as part of trilinos/Trilinos#3887 Build/Test Cases Summary Enabled Packages: Enabled all Packages 0) MPI_DEBUG => passed: passed=361,notpassed=0 (1.40 min) 1) SERIAL_RELEASE => passed: passed=361,notpassed=0 (1.22 min) Other local commits for this build/test group: d9134b4
I just pushed the merge commit 96ff001. Putting this in review for now but this looks good. |
No word from Reed yet to see if he has used this data or not yet. |
This has been used by Grover for a long time. |
Relates to my epic SEPW-215 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add option
--write-test-data-to-file=<file>
that will pretty-print the list of Python dicts for the status of all of the tests with issue trackers (which will include test history for all tests with issue trackers 'twip', 'twim', 'twif', etc.).This will make it possible to write other tools that reads in this file and then do things like a: Update the GitHub issues directly for when the status of the attached tests change, when they are all passing, weekly status updates; b: Re-open closed GitHub issues if tests are still failing associated with the issue tracker; c: Remove entries from the
*.csv
files for tests with issue trackers that are all passing and the associated issue tacker are closed. See trilinos/Trilinos#3887.The text was updated successfully, but these errors were encountered: