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.

Sign up for GitHub

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

Jump to bottom

Test "test__201__channel_serial_is_cleared_whenever_a_channel_entered_into_detached_suspended_or_failed_state" fails a lot #1990

Open
maratal opened this issue Oct 8, 2024 · 0 comments
Open

Test "test__201__channel_serial_is_cleared_whenever_a_channel_entered_into_detached_suspended_or_failed_state" fails a lot #1990

maratal opened this issue Oct 8, 2024 · 0 comments
Assignees
@maratal
Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.

Comments

@maratal
Copy link
Collaborator

maratal commented Oct 8, 2024 •
edited by sync-by-unito bot
Loading

Actually it's "test__200__channel_serial_is_updated_whenever_a_protocol_message_with_either_message_presence_or_attached_actions_is_received_in_a_channel" which is above the test in the title. One of it's closures is being called already after test finishes and thus failing currently executing test ("splitDone called more than 3 times").

┆Issue is synchronized with this Jira Task by Unito
@maratal maratal self-assigned this Oct 8, 2024
@maratal maratal added the failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug. label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maratal maratal

Labels
failing-test Where an automated test is failing either locally or in CI. Perhaps flakey, wrong or bug.
Milestone
No milestone
Development

No branches or pull requests
1 participant
@maratal