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

chore(bors): Check for e2e-tests passing before merging #888

Merged
merged 1 commit into from
Jul 4, 2023

Conversation

klochowicz
Copy link
Contributor

New end to end tests are not supposed to be flaky; check whether they pass
before merging.

@holzeis
Copy link
Contributor

holzeis commented Jul 4, 2023

New end to end tests are not supposed to be flaky; check whether they pass before merging.

What tests are supposed to be flaky? 😅 🤪

@klochowicz
Copy link
Contributor Author

New end to end tests are not supposed to be flaky; check whether they pass before merging.

What tests are supposed to be flaky? 😅 🤪

The ones I don't dare to name anymore 😂 (the ones that used to be in this file, and we removed them 😉)

@holzeis holzeis self-requested a review July 4, 2023 07:55
New end to end tests are not supposed to be flaky; check whether they pass
before merging.
@klochowicz klochowicz force-pushed the chore/enable-e2e-tests-on-bors branch from 983af7f to 0c60e04 Compare July 4, 2023 07:56
@klochowicz
Copy link
Contributor Author

bors r+

@bors
Copy link
Contributor

bors bot commented Jul 4, 2023

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot merged commit 65bce17 into main Jul 4, 2023
7 checks passed
@bors bors bot deleted the chore/enable-e2e-tests-on-bors branch July 4, 2023 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants