This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
chore(ci): be more specific about the underlying ARM OS #1341
Conversation
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
v1v
approved these changes
Jul 20, 2021
cachedout
approved these changes
Jul 20, 2021
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
mergify bot
pushed a commit
that referenced
this pull request
Jul 20, 2021
(cherry picked from commit 964b8a1)
mergify bot
pushed a commit
that referenced
this pull request
Jul 20, 2021
(cherry picked from commit 964b8a1)
mergify bot
pushed a commit
that referenced
this pull request
Jul 20, 2021
(cherry picked from commit 964b8a1)
mdelapenya
added a commit
that referenced
this pull request
Jul 20, 2021
mdelapenya
added a commit
that referenced
this pull request
Jul 20, 2021
mdelapenya
added a commit
that referenced
this pull request
Jul 20, 2021
I'd say that with the current frequency it's enough, but I see your point: we could maybe keep a PR open simply running the offending test suite. 🤔 Does it make sense, right? |
|
I thought this PR will remain open, that was the reason for my question, since it's merged then it was not valid :) |
|
We can send a new one simplifying the test layout, including the proposed cron |
8 tasks
mdelapenya
added a commit
to mdelapenya/e2e-testing
that referenced
this pull request
Jul 27, 2021
* master: chore: read elastic-agent logs using native OS' log manager (elastic#1368) Add kubernetes autodiscover scenario without autodiscover (elastic#1361) fix: expose fleet-server port (elastic#1348) chore: improve the automation for the stack version bump (elastic#1351) bump stack version 8.0.0-a6334483 (elastic#1350) bump stack version 8.0.0-1e9bea0f (elastic#1346) chore(ci): be more specific about the underlying ARM OS (elastic#1341) fix: apply container name to elastic-agent Docker services (elastic#1336)
8 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR do?
It forces
centos-8-armas the label used by Jenkins to grab the CI workers when the tests need to be run on ARM.Why is it important?
We are seeing certain flakiness in one single scenario for Debian (See #1271) and we'd like to narrow down the issue: because we have multiple ARM CI workers under the
armlabel, we want to always use the same.Checklist
make unit-test), and they are passing locallymake noticein the proper directory)Author's Checklist
Related issues