-
Notifications
You must be signed in to change notification settings - Fork 42
Conversation
@@ -35,6 +35,7 @@ pipeline { | |||
string(name: 'SLACK_CHANNEL', defaultValue: 'observablt-bots', description: 'The Slack channel(s) where errors will be posted. For multiple channels, use a comma-separated list of channels') | |||
string(name: 'ELASTIC_AGENT_DOWNLOAD_URL', defaultValue: '', description: 'If present, it will override the download URL for the Elastic agent artifact. (I.e. https://snapshots.elastic.co/7.11.0-d52afba4/downloads/beats/elastic-agent/elastic-agent-7.11.0-SNAPSHOT-linux-x86_64.tar.gz') | |||
string(name: 'ELASTIC_AGENT_VERSION', defaultValue: '7.x-SNAPSHOT', description: 'SemVer version of the stand-alone elastic-agent to be used for Fleet tests. You can use here the tag of your PR to test your changes') | |||
string(name: 'ELASTIC_AGENT_STALE_VERSION', defaultValue: '7.10.0', description: 'SemVer version of the stale stand-alone elastic-agent to be used for Fleet upgrade tests.') |
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.
@michalpristas what version should we use as stale in 7.x? Same question will come up for the backport to 7.10.x
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
|
Test | Results |
---|---|
Failed | 3 |
Passed | 18 |
Skipped | 0 |
Total | 21 |
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_agent_endpoint_integration / [empty] – TEST-fleet.xml
- Name:
Initializing / End-To-End Tests / fleet_fleet_mode_agent / [empty] – TEST-fleet.xml
- Name:
Initializing / End-To-End Tests / fleet_stand_alone_agent / [empty] – TEST-fleet.xml
The errors I see in this PR against 7.x branch, which are the same errors as in any 7.x CI build (see https://beats-ci.elastic.co/job/e2e-tests/job/e2e-testing-mbp/job/7.x/35/), are related to Kibana not being able to start:
@EricDavisX @ph do we know if Did not mention it, but same code in 7.10.x passes the tests |
Digging even more into the Kibana error, the container logs are not clear to me:
|
Closing in favour of #558 |
What does this PR do?
It cherry-picks all commits in that PR, manually resolving conflicts.
Why is it important?
Keep 7.x branch up-to-date
Checklist
make notice
in the proper directory)Author's Checklist
Related issues
Follow-ups
Once merged using squash, try to backport that resulting commit to 7.10.x too