-
Notifications
You must be signed in to change notification settings - Fork 577
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
Run tests after builds are done, regardless of they failed or succeeded #5729
Conversation
.github/workflows/pr-realm-js.yml
Outdated
@@ -234,6 +234,7 @@ jobs: | |||
integration-tests: | |||
name: Integration tests (${{matrix.variant.target}}) for ${{ matrix.variant.environment }} on ${{ matrix.variant.os }} | |||
needs: [bundle, build, ios-xcframework] | |||
if: ${{ always() }} |
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'm surprised that this does anything. Could you add a synthetic build failure (possibly in a pr on top of this, or just in a commit that you will rebase away) to see how it works?
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.
Sure. I just pushed a commit that will fail the windows runners
d8b5259
to
7f1d2b9
Compare
7f1d2b9
to
6fcc311
Compare
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'm not 100% qualified to review the code, but it did seem to work as intended. Just remember to squash before or as part of merging to keep the intentional build-break out of history.
@RedBeard0531 I rebased and removed the commit that breaks builds. Seems the x64 build is breaking for other reasons, but one can see the tests still run! |
What, How & Why?
It would be good to know that which tests are passing, even if the builds aren't.
This closes # ???
☑️ ToDos
Compatibility
label is updated or copied from previous entryCOMPATIBILITY.md
package.json
s (if updating internal packages)Breaking
label has been applied or is not necessaryIf this PR adds or changes public API's: