-
Notifications
You must be signed in to change notification settings - Fork 3.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
Potential regression in spilled ORDER BY #16406
Comments
Marked release-blocker, because it looks like a regression after 409. |
https://nineinchnick.github.io/trino-cicd/reports/flaky/ currently doesn't include "spilled" (like in |
The annotation processing job has been failing recently, and we're relying on these annotations to create that report. We do have all the test reports downloaded from GHA artifacts, but there are no XML functions in Trino to process them. We'd have to create another job to convert them to JSON. I just opened ScaCap/action-surefire-report#138 to address failures in annotation processing. |
This error can be seen in man test's and in different combinations:
Root cause stack trace is always the same
|
I added some debug prints into OrderByOperator and run TestSpilledOrderByQueries locally (it fails quite consistently locally, failing method varies) Example failure gave me the log (i've filtered this down to a single operator instance based in identity hash code)
It's clear the operator spilled multiple time, the last one between finish and getOutput
in As described in #16409, before #15575 such iterator would not fail (would return 0 pages). Question: why is |
@findepi is this a potential correctness issue? could |
I don't think so. Per
getOutput() cannot be called before finishMemoryRevoke is run.
|
example from #16400 build https://github.com/trinodb/trino/actions/runs/4351418003/jobs/7603093117
The text was updated successfully, but these errors were encountered: