Use abbreviated output for stestr run in CI#15827
Merged
jakelishman merged 1 commit intoQiskit:mainfrom Mar 17, 2026
Merged
Conversation
This commit updates how we use stestr in CI to enable abbreviated output instead of the full output. Our test suite has grown to the point that printing each individual test case as a new line when it completes will overflow the github actions line limit for CI job logs. This makes it very inconvenient to identify the cause of a failure when a test fails because unless it's in the tests that get displayed before github stops displaying it you have to download the full log file (which you can view in the browser still but without the highlighting or direct link support). stestr has a less verbose output mode where it prints a single character for each test. `.` if a test succeeds, `F` for failure, etc. Test failures are still printed in full as is the summary footer. It's just the output of tests as they execute which is different. While this doesn't give the same level of diagnostic detail that the full output normally does it will not exceed github's limit. As a small side benefit from the benchmarking I did many years ago stestr actually executes slightly faster in this mode because it doesn't have to write nearly as much to stdout.
Collaborator
|
One or more of the following people are relevant to this code:
|
jakelishman
reviewed
Mar 17, 2026
Member
jakelishman
left a comment
There was a problem hiding this comment.
Do you want to update the tox config too, or leave that as-is?
Member
Author
|
I left it as-is for now I did start there though before pushing. Local terminals don't have the same line limit as GitHub and it's simple enough to do |
jakelishman
approved these changes
Mar 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This commit updates how we use stestr in CI to enable abbreviated output instead of the full output. Our test suite has grown to the point that printing each individual test case as a new line when it completes will overflow the github actions line limit for CI job logs. This makes it very inconvenient to identify the cause of a failure when a test fails because unless it's in the tests that get displayed before github stops displaying it you have to download the full log file (which you can view in the browser still but without the highlighting or direct link support). stestr has a less verbose output mode where it prints a single character for each test.
.if a test succeeds,Ffor failure, etc. Test failures are still printed in full as is the summary footer. It's just the output of tests as they execute which is different. While this doesn't give the same level of diagnostic detail that the full output normally does it will not exceed github's limit. As a small side benefit from the benchmarking I did many years ago stestr actually executes slightly faster in this mode because it doesn't have to write nearly as much to stdout.Details and comments