Remove Test Reports step from workflow - #3413
Merged
Merged
Conversation
Removed Test Reports step from timing-tests workflow.
raboof
approved these changes
Aug 6, 2026
raboof
left a comment
Member
There was a problem hiding this comment.
I don't think this action adds much anyway. When the tests fail, I just look at the logs to find the stacktraces and test reports.
I'd like seeing test failure details more easily in theory, but in practice I agree I haven't found much use for this particular step
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.
Removed Test Reports step from timing-tests workflow.
Our timing tests plan is failing every night. https://github.com/apache/pekko/actions/workflows/timing-tests.yml
This action is now not allowed due to apache/infrastructure-actions#828
Can't find any of the replacements in this allowed list:
https://github.com/apache/infrastructure-actions/blob/main/actions.yml
I don't think this action adds much anyway. When the tests fail, I just look at the logs to find the stacktraces and test reports.