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

[x86, release]: topology_custom.test_read_repair #15371

Closed
yaronkaikov opened this issue Sep 12, 2023 · 5 comments
Closed

[x86, release]: topology_custom.test_read_repair #15371

yaronkaikov opened this issue Sep 12, 2023 · 5 comments
Labels
area/raft symptom/ci stability Issues that failed in ScyllaDB CI - tests and framework triage/master Looking for assignee
Milestone

Comments

@yaronkaikov yaronkaikov added triage/master Looking for assignee symptom/ci stability Issues that failed in ScyllaDB CI - tests and framework area/raft labels Sep 12, 2023
@yaronkaikov
Copy link
Contributor Author

@mykaul @avikivity We should probably try to get a quick fix for this or remove it temporarily from gating (until it is stable again)

@mykaul
Copy link
Contributor

mykaul commented Sep 12, 2023

The failures are a bit odd:

test_read_repair.py::test_incremental_read_repair[row-tombstone]
  /jenkins/workspace/scylla-master/next/scylla/test/topology_custom/test_read_repair.py:310: RuntimeWarning: coroutine 'ScyllaRESTAPIClient.keyspace_flush' was never awaited
    manager.api.keyspace_flush(node.ip_addr, "ks")
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

test_read_repair.py::test_incremental_read_repair[row-tombstone]
  /jenkins/workspace/scylla-master/next/scylla/test/topology_custom/test_read_repair.py:311: RuntimeWarning: coroutine 'ScyllaRESTAPIClient.keyspace_compaction' was never awaited
    manager.api.keyspace_compaction(node.ip_addr, "ks")
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more info.

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
- generated xml file: /scylladir/testlog/x86_64/release/xml/topology_custom.test_read_repair.2.xunit.xml -

Some await missing?
@bhalevy - does the test belong to your team?
Regardless, let's remove it from gating until we resolve it.

@denesb
Copy link
Contributor

denesb commented Sep 13, 2023

I reverted the PR that introduced it: #14923.

@denesb denesb closed this as completed Sep 13, 2023
@denesb denesb reopened this Sep 13, 2023
@denesb
Copy link
Contributor

denesb commented Sep 13, 2023

I added Fixes to the revert, let promotion close this issue after merge.

@denesb
Copy link
Contributor

denesb commented Sep 13, 2023

No vulnerable releases, removing backport candidate label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/raft symptom/ci stability Issues that failed in ScyllaDB CI - tests and framework triage/master Looking for assignee
Projects
None yet
Development

No branches or pull requests

4 participants