-
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
Disable flakiest tests #14706
Disable flakiest tests #14706
Conversation
@@ -23,7 +23,8 @@ | |||
|
|||
public class TestS3WrongRegionPicked | |||
{ | |||
@Test | |||
// Disabled due to flakiness per https://nineinchnick.github.io/trino-cicd/reports/flaky/ |
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.
It's already fixed #14615
@@ -125,7 +125,8 @@ public void testDatabricksCanReadTrinoCheckpoint() | |||
} | |||
} | |||
|
|||
@Test(groups = {DELTA_LAKE_DATABRICKS, PROFILE_SPECIFIC_TESTS}) | |||
// Disabled due to flakiness per https://nineinchnick.github.io/trino-cicd/reports/flaky/ | |||
@Test(groups = {DELTA_LAKE_DATABRICKS, PROFILE_SPECIFIC_TESTS}, enabled = false) |
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.
I don't think disabling this test helps to fix Retry-After failure. The failed place isn't deterministic.
@@ -79,7 +79,8 @@ private void testDatabricksCanReadFromCtasTableCreatedByTrinoWithSpecialCharacte | |||
} | |||
} | |||
|
|||
@Test(groups = {DELTA_LAKE_DATABRICKS, PROFILE_SPECIFIC_TESTS}) | |||
// Disabled due to flakiness per https://nineinchnick.github.io/trino-cicd/reports/flaky/ | |||
@Test(groups = {DELTA_LAKE_DATABRICKS, PROFILE_SPECIFIC_TESTS}, enabled = false) |
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.
I don't think disabling this test helps to fix Retry-After failure. The failed place isn't deterministic.
@@ -716,6 +716,11 @@ public void testLimitPushdown() | |||
assertThat(query("SELECT name FROM nation LIMIT 30")).isNotFullyPushedDown(LimitNode.class); // Use high limit for result determinism | |||
} | |||
|
|||
// Empty override is to disable test due to flakiness per https://nineinchnick.github.io/trino-cicd/reports/flaky/ |
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.
Please leave GitHub issue link instead of https://nineinchnick.github.io/trino-cicd/reports/flaky/. The link isn't helpful when we access the page in the future.
Description
Using data from @nineinchnick's reports on flaky tests @ https://nineinchnick.github.io/trino-cicd/reports/flaky/, I've taken a look at the flakiest tests that have failed within the last week and disabled them to hopefully address some of our ongoing CI failure issues.
Four tests being disabled, and their error messages when failing:
TestS3WrongRegionPicked.testS3WrongRegionSelection
[Expecting throwable message: ]
TestKuduConnectorTest.testAggregation
[Execution of 'actual' query failed: SELECT count(regionkey) FROM nation, Execution of 'actual' query failed: SELECT min(regionkey), max(regionkey) FROM nation, Execution of 'actual' query failed: SELECT regionkey, count(*) FROM nation GROUP BY regionkey]
TestDeltaLakeDatabricksPartitioningCompatibility > testTrinoCanReadFromCtasTableCreatedByDatabricksWithSpecialCharactersInPartitioningColumn
[java.sql.SQLException: [Databricks][DatabricksJDBCDriver](500593) Communication link failure. Failed to connect to server. Reason: HTTP retry after response received with no Retry-After header, error: HTTP Response code: 503, Error message: Unknown.]
TestDeltaLakeDatabricksCheckpointsCompatibility > testTrinoUsesCheckpointInterval
[java.sql.SQLException: [Databricks][DatabricksJDBCDriver](500593) Communication link failure. Failed to connect to server. Reason: HTTP retry after response received with no Retry-After header, error: HTTP Response code: 503, Error message: Unknown.]
It looks like other tests in the DeltaLakeDatabricks compatibility tests have errored out in the past with a connection error, I'm not sure if these particular tests are more prone to this error or if they're just the ones getting unlucky as of late. It may not make much sense to disable them, would appreciate feedback on that.
Non-technical explanation
Disabling flaky tests.
Release notes
(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text: