This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
update-to-available-version #540
Merged
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
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
| Test | Results |
|---|---|
| Failed | 1 |
| Passed | 71 |
| Skipped | 20 |
| Total | 92 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Initializing / End-To-End Tests / fleet_fleet_mode_agent / Un-installing the installed centos agent – Fleet Mode Agent
|
there is one test failing and it is unrelated to this pr change as it was seen passing in the first run before updating master branch in. so i'm merging. |
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?
updates minor version in string, so it can be found and that agent artifact used in test
Why is it important?
Screenshots
need to check if the upgrade test was ever back-ported out of master, it may not have been. also, it is disabled as of now - hence why the tests are not failing on master due to this. a future PR could enhance the api call used to not require regular maintenance like this... but we likely won't have many 7.10 hot-fix patch releases so it matters only a little for now