Skip to content
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

Merged
merged 3 commits into from
Apr 13, 2023

Conversation

takameyer
Copy link
Contributor

What, How & Why?

It would be good to know that which tests are passing, even if the builds aren't.

This closes # ???

☑️ ToDos

  • 📝 Changelog entry
  • 📝 Compatibility label is updated or copied from previous entry
  • 📝 Update COMPATIBILITY.md
  • 🚦 Tests
  • 🔀 Executed flexible sync tests locally if modifying flexible sync
  • 📦 Updated internal package version in consuming package.jsons (if updating internal packages)
  • 📱 Check the React Native/other sample apps work if necessary
  • 📝 Public documentation PR created or is not necessary
  • 💥 Breaking label has been applied or is not necessary

If this PR adds or changes public API's:

  • typescript definitions file is updated
  • jsdoc files updated

@@ -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() }}
Copy link
Contributor

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?

Copy link
Contributor Author

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

Copy link
Contributor

@RedBeard0531 RedBeard0531 left a 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.

@takameyer
Copy link
Contributor Author

takameyer commented Apr 13, 2023

@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!

@takameyer takameyer merged commit 1d232b0 into main Apr 13, 2023
@takameyer takameyer deleted the test-workflow branch April 13, 2023 12:19
papafe added a commit that referenced this pull request Apr 17, 2023
* main:
  Update core to v13.9.1 (#5739)
  Implement `User.state` (#5712)
  Rename `local-mongodb` to enable app replacements (#5734)
  Update return type of 'assert.never'. (#5718)
  Run tests after builds are done, regardless of they failed or succeeded (#5729)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants