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

Possible deadlock in concurrent write test #12316

Open
RoloEdits opened this issue Dec 22, 2024 · 0 comments
Open

Possible deadlock in concurrent write test #12316

RoloEdits opened this issue Dec 22, 2024 · 0 comments
Labels
C-bug Category: This is a bug

Comments

@RoloEdits
Copy link
Contributor

RoloEdits commented Dec 22, 2024

Summary

I was rewriting the write command and in the process of testing I noticed that these two tests always seem to timeout. I've never seen it run fully in the times I've been testing locally. I see that it passes in CI, so I wonder if this is spurious behavior and perhaps only triggered on faster hardware?

test test::commands::write::test_buffer_close_concurrent has been running for over 60 seconds
test test::commands::write::test_write_concurrent has been running for over 60 seconds

Reproduction Steps

  1. cargo integration-test

Platform

Windows

Terminal Emulator

wezterm

Installation Method

source

Helix Version

helix 24.7 (d6d93fe)

@RoloEdits RoloEdits added the C-bug Category: This is a bug label Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

No branches or pull requests

1 participant