-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Skip ESTF failures #136912
Skip ESTF failures #136912
Conversation
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: cc @matschaffer |
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.
Wouldn't it be nice if we could easily regenerate archives on the fly to account for different contexts? :D
@@ -12,7 +12,10 @@ import { getLifecycleMethods } from '../data_stream'; | |||
export default function ({ getService }) { | |||
const supertest = getService('supertest'); | |||
|
|||
describe('instance detail mb', () => { | |||
describe('instance detail mb', function () { |
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.
Is there a reason for swapping to function, rather than arrow function?
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.
Wouldn't it be nice if we could easily regenerate archives on the fly to account for different contexts? :D
I see what you did there ;)
Is there a reason for swapping to function, rather than arrow function?
As far as I know you need this
in order to add test tags. But I could switch it if you know another way to add the tags.
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
* Skip ESTF failures * Right, can't tag stabby lambdas (cherry picked from commit 63c7bee)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
* Skip ESTF failures * Right, can't tag stabby lambdas (cherry picked from commit 63c7bee) # Conflicts: # x-pack/test/api_integration/apis/monitoring/apm/instance_mb.js # x-pack/test/api_integration/apis/monitoring/apm/instances_mb.js
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
Summary
Fixes 5 new ESTF failure issues all exhibiting this diff.
This arrises from the API integration tests being run on cloud (in containers) while the archive data for assertions is not from a containerized system.
Fixes #136878
Fixes #136879
Fixes #136880
Fixes #136893
Fixes #136894
Fixes #105355
Fixes #105356
Fixes #98419
Fixes #105357
Fixes #98420