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

Do not override an existed thread in the testing framework #511

Merged
merged 1 commit into from
Feb 5, 2022

Conversation

ono-max
Copy link
Collaborator

@ono-max ono-max commented Feb 1, 2022

A thread for storing debuggee's output is defined https://github.com/ruby/debug/blob/master/test/support/utils.rb#L333 as a reader_thread in remote_info. However, it's overridden in https://github.com/ruby/debug/pull/511/files#diff-a1bc4fb86b4a4e8cc3d94199a4d2b9152c2c8da2261be54d0529942f64a8105dL155. This PR fixes it.

@ono-max ono-max force-pushed the patch-30 branch 2 times, most recently from 05267fb to 6c991fd Compare February 1, 2022 13:16
@ono-max ono-max changed the title Do not override a thread for storing debuggee's output when a thread for receiving DAP requests is created Do not override a existed thread in the testing framework Feb 1, 2022
@ono-max ono-max changed the title Do not override a existed thread in the testing framework Do not override an existed thread in the testing framework Feb 1, 2022
@st0012
Copy link
Member

st0012 commented Feb 1, 2022

Is this a cause of random CI failures?

@ono-max
Copy link
Collaborator Author

ono-max commented Feb 1, 2022

Hopefully.
I can't have confidence in that, though.

@ko1 ko1 merged commit aa7d94c into ruby:master Feb 5, 2022
@ono-max ono-max deleted the patch-30 branch February 13, 2022 13:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants