fix(e2e): Fix up suite release reporter workflow #19173
Merged
Conversation
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
solves inheretance issue minor fixes reporter definition moved back to workflow calls solves concurrences clashes
HajekOndrej
approved these changes
May 30, 2025
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.
The orchestration was broken in my original PR. I could not know before merge since the workflow did not exist.
Here is test run - https://github.com/orgs/trezor/projects/110/views/4?sliceBy%5Bvalue%5D=fix-e2e-reporter-orchestration-4bf9d0c
Our test project contains link to the workflow for convinience.
solves inheretance issue
minor fixes
reporter definition moved back to workflow calls
solves concurrences clashes
🔍🖥️ Suite web test results: View in Currents
🔍🖥️ Suite desktop test results: View in Currents