-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
opt: unoptimized-query-oracle/disable-rules=half failed due to timeout #86308
Comments
This one looks like a rule cycle between We might be able to solve this without losing testing coverage by modifying |
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ 5c2c62ecf1bea60c807edc6b4da22d900ad4ae03:
Parameters: |
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ a0d8839aa6164af81a9ebb140147d3baf5321287:
Parameters: |
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ cb55144cdec54d2a70f074ad64b4eca5e6c6891a:
Parameters: |
This commit decreases the likelihood of rule cycles occuring during optimizer tests with disabled rules. `DerivePruneCols` and `DeriveRejectNullCols` now check whether propagating their corresponding properties would trigger a disabled rule (if it wasn't disabled), and avoid propagating in that case. This is necessary to avoid cases where a `Select` or `Project` gets repeatedly pushed down and eliminated. Addresses cockroachdb#86308 Release note: None Release justification: testing-only change
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ 80c274877a917580af62be6eb0cd48c8c7ae9c08:
Parameters: |
This commit decreases the likelihood of rule cycles occuring during optimizer tests with disabled rules. `DerivePruneCols` and `DeriveRejectNullCols` now check whether propagating their corresponding properties would trigger a disabled rule (if it wasn't disabled), and avoid propagating in that case. This is necessary to avoid cases where a `Select` or `Project` gets repeatedly pushed down and eliminated. Addresses cockroachdb#86308 Release note: None Release justification: testing-only change
@DrewKimball I'm assigning you to this issue since you've already been doing a lot of work to investigate these failures. Feel free to close it out once #86631 merges. I'll open up a separate issue for the non-timeout failures. |
Opened up #86790 to cover the two non-timeout failures. |
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ 524fd14da3fefcd849f44a835cc5f88f5dbdadcc:
Parameters: |
This commit decreases the likelihood of rule cycles occuring during optimizer tests with randomly disabled rules. `DerivePruneCols` and `DeriveRejectNullCols` now check whether propagating their corresponding properties would trigger a disabled rule (if it wasn't disabled), and avoid propagating in that case. This is necessary to avoid cases where a `Select` or `Project` gets repeatedly pushed down and eliminated. Addresses cockroachdb#86308 Release note: None Release justification: testing-only change
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ 770ff3c545a51752490403da64d56fb397f49c5e:
Parameters: |
Opened #87023 for the most recent non-timeout failure |
I'm going to remove the release-blocker label on this one since the timeout failures should not be release blockers |
Should we be running the unoptimized query oracle with with the |
@yuzefovich just merged #86625 so now I think we run 50% of these tests with |
Actually it looks like that change was only for the |
👍 I created #87051 to track doing that. |
This commit decreases the likelihood of rule cycles occuring during optimizer tests with randomly disabled rules. `DerivePruneCols` and `DeriveRejectNullCols` now check whether propagating their corresponding properties would trigger a disabled rule (if it wasn't disabled), and avoid propagating in that case. This is necessary to avoid cases where a `Select` or `Project` gets repeatedly pushed down and eliminated. Addresses cockroachdb#86308 Release note: None Release justification: testing-only change
86631: opt: don't propagate rule props when corresponding rule is disabled r=DrewKimball a=DrewKimball This commit decreases the likelihood of rule cycles occuring during optimizer tests with disabled rules. `DerivePruneCols` and `DeriveRejectNullCols` now check whether propagating their corresponding properties would trigger a disabled rule (if it wasn't disabled), and avoid propagating in that case. This is necessary to avoid cases where a `Select` or `Project` gets repeatedly pushed down and eliminated. Addresses #86308 Release note: None Release justification: testing-only change Co-authored-by: DrewKimball <[email protected]>
@DrewKimball Where would you see this in a |
Here's an example from a recent timeout (#87031):
In this case, we can be pretty sure that since |
Closing this, since the timeouts and |
Cool! I didn't realize we logged disabled rules like that. |
roachtest.unoptimized-query-oracle/disable-rules=half failed with artifacts on master @ b173a16715e71e94115820374da1eb350b3b459d:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-18687
The text was updated successfully, but these errors were encountered: