-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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] HeapAttackIT testLookupExplosionManyMatches failing #121481
Comments
…ExplosionManyMatches #121481
This has been muted on branch main Mute Reasons:
Build Scans: |
Pinging @elastic/es-analytical-engine (Team:Analytics) |
@nik9000 , this one also somehow returned a result. I'd appreciate if you could take a look :)
|
Despite this saying "should have failed but didn't" this is actually a timeout. In the
This one didn't fail:
Everything failed. The whole build seems broken. Timeout in the Analyzer. In |
There isn't an |
Reenables some heap attack tests, bumping their memory requirements to try and force a failure on all CI machines. Previously some CI machines weren't failing, invalidating the test on those machines. Close elastic#121481 Close elastic#121465
Reenables some heap attack tests, bumping their memory requirements to try and force a failure on all CI machines. Previously some CI machines weren't failing, invalidating the test on those machines. Close elastic#121481 Close elastic#121465
Reenables some heap attack tests, bumping their memory requirements to try and force a failure on all CI machines. Previously some CI machines weren't failing, invalidating the test on those machines. Close elastic#121481 Close elastic#121465
* ESQL: Reenable heap attacks (#121565) Reenables some heap attack tests, bumping their memory requirements to try and force a failure on all CI machines. Previously some CI machines weren't failing, invalidating the test on those machines. Close #121481 Close #121465 * Unmute --------- Co-authored-by: Alexander Spies <alexander.spies@elastic.co>
Reenables some heap attack tests, bumping their memory requirements to try and force a failure on all CI machines. Previously some CI machines weren't failing, invalidating the test on those machines. Close elastic#121481 Close elastic#121465
Build Scans:
Reproduction Line:
Applicable branches:
8.x
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
Issue Reasons:
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
The text was updated successfully, but these errors were encountered: