Skip to content

Conversation

@DanBlackwell
Copy link

We have seen another failure of TestTsanSwiftAccessRace.py, indicating that we recieved the stop reason eStopReasonSignal rather than the expected eStopReasonInstrumentation. This alone has not been enough to diagnose the root cause of the failure.

This PR adds in verbose logging, as well as capturing the value of the signal, in the hope of diagnosing the issue fully in the next occurrence.

rdar://153220781

@DanBlackwell
Copy link
Author

Note: it will be easier to review the first commit prior to running the formatter (which has changed many lines untouched by the first commit)

@charles-zablit
Copy link

Note that we don't squash commits on the swiftlang fork. You probably want to squash before merging.

We have seen another failure of TestTsanSwiftAccessRace.py, indicating that we recieved the stop reason eStopReasonSignal rather than the expected eStopReasonInstrumentation. This alone has not been enough to diagnose the root cause of the failure.

This PR adds in verbose logging, as well as capturing the value of the signal, in the hope of diagnosing the issue fully in the next occurrence.
@DanBlackwell DanBlackwell force-pushed the improved-logging-lldb-testTsanSwiftAccessRace branch from c7864f5 to 173d564 Compare September 9, 2025 13:30
@DanBlackwell DanBlackwell merged commit 0a3a8ce into swiftlang:stable/21.x Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants