Skip to content
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 Failure (assert offset == o) in TimeQueryTest.test_timequery #17201

Closed
vbotbuildovich opened this issue Mar 20, 2024 · 11 comments
Closed

CI Failure (assert offset == o) in TimeQueryTest.test_timequery #17201

vbotbuildovich opened this issue Mar 20, 2024 · 11 comments
Labels
area/cloud-storage Shadow indexing subsystem auto-triaged used to know which issues have been opened from a CI job ci-failure sev/medium Bugs that do not meet criteria for high or critical, but are more severe than low.

Comments

@vbotbuildovich
Copy link
Collaborator

vbotbuildovich commented Mar 20, 2024

https://buildkite.com/redpanda/vtools/builds/12363

Module: rptest.tests.timequery_test
Class: TimeQueryTest
Method: test_timequery
Arguments: {
    "spillover": true,
    "batch_cache": false,
    "cloud_storage": true
}
test_id:    TimeQueryTest.test_timequery
status:     FAIL
run time:   33.746 seconds

AssertionError()
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 184, in _do_run
    data = self.run_test()
  File "/usr/local/lib/python3.10/dist-packages/ducktape/tests/runner_client.py", line 269, in run_test
    return self.test_context.function(self.test)
  File "/usr/local/lib/python3.10/dist-packages/ducktape/mark/_mark.py", line 481, in wrapper
    return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
  File "/home/ubuntu/redpanda/tests/rptest/services/cluster.py", line 104, in wrapped
    r = f(self, *args, **kwargs)
  File "/home/ubuntu/redpanda/tests/rptest/tests/timequery_test.py", line 372, in test_timequery
    self._do_test_timequery(cloud_storage, batch_cache, spillover)
  File "/home/ubuntu/redpanda/tests/rptest/tests/timequery_test.py", line 346, in _do_test_timequery
    self._test_timequery(cluster=self.redpanda,
  File "/home/ubuntu/redpanda/tests/rptest/tests/timequery_test.py", line 210, in _test_timequery
    assert offset == o
AssertionError

JIRA Link: CORE-1895

@vbotbuildovich vbotbuildovich added auto-triaged used to know which issues have been opened from a CI job ci-failure labels Mar 20, 2024
@michael-redpanda
Copy link
Contributor

Note to developer: please provide a message with the assertion when addressing this issue

@michael-redpanda michael-redpanda added the area/cloud-storage Shadow indexing subsystem label Mar 20, 2024
@michael-redpanda michael-redpanda changed the title CI Failure (key symptom) in TimeQueryTest.test_timequery CI Failure (assert offset == o) in TimeQueryTest.test_timequery Mar 20, 2024
@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

1 similar comment
@vbotbuildovich
Copy link
Collaborator Author

@dotnwat dotnwat added the sev/medium Bugs that do not meet criteria for high or critical, but are more severe than low. label Apr 6, 2024
@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

@vbotbuildovich
Copy link
Collaborator Author

@WillemKauf
Copy link
Contributor

WillemKauf commented May 15, 2024

Without going into the details of the CI failure itself, whats interesting about this is that it has only been triggered in CDT over the last few months, and every report of it failing also has a number of other failed ducktapes with it- usually node operation or partition moving tests.

Most specifically, this seems to fail quite often with rptest.tests.cloud_storage_timing_stress_test::CloudStorageTimingStressTest.test_cloud_storage_with_partition_moves and rptest.tests.node_pool_migration_test::NodePoolMigrationTest.test_migrating_redpanda_nodes_to_new_pool.

So, that leads me to ask the question, is ducktape parallelization and the interaction of these tests responsible for the failures seen in the TimeQueryTest?

Timequeries seem very stable on their own.

@vbotbuildovich
Copy link
Collaborator Author

@piyushredpanda
Copy link
Contributor

Closing older-bot-filed CI issues as we transition to a more reliable system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cloud-storage Shadow indexing subsystem auto-triaged used to know which issues have been opened from a CI job ci-failure sev/medium Bugs that do not meet criteria for high or critical, but are more severe than low.
Projects
None yet
Development

No branches or pull requests

5 participants