-
Notifications
You must be signed in to change notification settings - Fork 158
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
[CI] [Integration tests] Enable ARM tests for common test groups #6902
Conversation
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 wasn't able to see these arm:sudo tests running as part of the PR. Is there a way to see if they run (successfully)?
ARM tests are passing, however the PR is blocked by a knows flaky test: #6924 |
This PR #6897 is merged, if you can rebase, the error that you're seeing in the integration tests should be resolved. |
buildkite test this |
|
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.
LGTM
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.
Thanks! I now see the three arm:sudo tests (upgrade-flavor/standalone-upgrade/fleet) . The fleet
one of them seems to be having a flaky test testing/integration TestSetLogLevelFleetManaged is this flakiness tracked somewhere?
Yes, here is the issue for the flaky test |
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @pazone |
* [CI] [Integration tests] Enable ARM tests for common test groups * Added a comment * [CI] Added .buildkite/bk.integration.pipeline.yml to extended trigger paths (cherry picked from commit 694cec8)
* [CI] [Integration tests] Enable ARM tests for common test groups * Added a comment * [CI] Added .buildkite/bk.integration.pipeline.yml to extended trigger paths (cherry picked from commit 694cec8)
* [CI] [Integration tests] Enable ARM tests for common test groups * Added a comment * [CI] Added .buildkite/bk.integration.pipeline.yml to extended trigger paths (cherry picked from commit 694cec8)
* [CI] [Integration tests] Enable ARM tests for common test groups * Added a comment * [CI] Added .buildkite/bk.integration.pipeline.yml to extended trigger paths (cherry picked from commit 694cec8)
* [CI] [Integration tests] Enable ARM tests for common test groups * Added a comment * [CI] Added .buildkite/bk.integration.pipeline.yml to extended trigger paths (cherry picked from commit 694cec8)
…stic#6902) * [CI] [Integration tests] Enable ARM tests for common test groups * Added a comment * [CI] Added .buildkite/bk.integration.pipeline.yml to extended trigger paths
What does this PR do?
Why is it important?
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself