-
Notifications
You must be signed in to change notification settings - Fork 592
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 (TimeoutError
) in TopicDeleteCloudStorageTest.topic_delete_unavailable_test
#15479
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
added
auto-triaged
used to know which issues have been opened from a CI job
ci-failure
labels
Dec 13, 2023
michael-redpanda
changed the title
CI Failure (key symptom) in
CI Failure (Dec 14, 2023
TopicDeleteCloudStorageTest.topic_delete_unavailable_test
TimeoutError
) in TopicDeleteCloudStorageTest.topic_delete_unavailable_test
abhijat
added
the
sev/medium
Bugs that do not meet criteria for high or critical, but are more severe than low.
label
Jan 2, 2024
The partition removal gets stuck somewhere when stopping the archiver, during
As storage is removed only after the preceding steps finish, the segments are not removed and there is a timeout. |
7 tasks
2 similar comments
8 tasks
7 tasks
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.
https://buildkite.com/redpanda/redpanda/builds/42333
https://buildkite.com/redpanda/redpanda/builds/42565
https://buildkite.com/redpanda/redpanda/builds/42656
JIRA Link: CORE-1636
The text was updated successfully, but these errors were encountered: