-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[ui, ci] Ember Exam failures should cause overall test failures #24603
Open
philrenaud
wants to merge
3
commits into
main
Choose a base branch
from
b-ui/ember-audit-test-artifacts-continue-on-error
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+17
−5
Open
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -24,7 +24,6 @@ | |
{{content-for "body"}} | ||
|
||
<script src="{{rootURL}}assets/vendor.js"></script> | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🙄 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is because of
But I'm going to try to make this workflow file part of that, too. |
||
<script src="{{rootURL}}assets/nomad-ui.js"></script> | ||
|
||
{{content-for "body-footer"}} | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if we're checking the
exam
step's outcome specifically, do we need "Express timeout failure" above?also, if you
exit 1
here, the Upload step below wouldn't run. presumably you'd want the test results even if something failed?but also, does
continue-on-error
at the job level, moved up to line 39, mean that all steps are continued, so thisexit 1
would be ignored just like any error thatyarn exam
might have spit out?I don't recall exactly the nuances of when which type of results are skipped, and I don't think I've done a job-level continue-on-error... if you're not sure either, I'd suggest making a little repo that's just for testing github actions, and creating little toy workflows so you can iterate more quickly. I suppose you could do that in a branch in this repo, but I like to do it in branches in my own lil experiment repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think probably I wouldn't want to upload the results in that case, actually; the point of uploading partition results outside of the running test step is to do look-backs and measure test timing, etc.
Although: if I also wanted to measure flakiness, I guess I would still want to upload things if there was a failure.
I think I need to think about this a bit more.