-
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 testLookupExplosionBigStringManyMatches failing #121465
Comments
…ExplosionBigStringManyMatches #121465
This has been muted on branch main Mute Reasons:
Build Scans: |
Pinging @elastic/es-analytical-engine (Team:Analytics) |
@nik9000 , could you please take a look at this one? Maybe this test needs further tuning, in the topmost build scan I found:
|
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
…ExplosionBigStringManyMatches #121465
This has been muted on branch 8.x Mute Reasons:
Build Scans:
|
* 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 <[email protected]>
I've re-muted this test because it is still failing, causing PR failures. See https://gradle-enterprise.elastic.co/s/3kezzxetjkumw/console-log/task/:test:external-modules:test-esql-heap-attack:javaRestTest?anchor=15&page=1 |
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
OK. I'm going to make the test scale it's memory usage higher and higher until it breaks. It should break in the first round, but it looks like some CI nodes are... fun! And if that still doesn't break I'll be quite surprised. |
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes elastic#121465
This has been muted on branch 8.18 Mute Reasons:
Build Scans:
|
…ExplosionBigStringManyMatches #121465
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes elastic#121465
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes elastic#121465
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes elastic#121465
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes #121465
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes #121465
This causes the ESQL heap attack tests to grow their memory usage if they first don't cause a circuit breaking exception. It just tries again with more data. That's slow, but it should stop this from failing quite as much. And it'll give us even more information about failures. Closes #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: