Skip to content

Deflake test that relies on unreliable instrumentation #8875

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

Merged
merged 1 commit into from
Jun 13, 2024

Conversation

adrian-prantl
Copy link

rdar://103598293

@adrian-prantl
Copy link
Author

@swift-ci test

Copy link

@JDevlieghere JDevlieghere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with ignorable nit.

# Unfortunatley the runtime itself isn't 100% reliable in reporting TSAN errors.
process = None
stop_reason = lldb.eStopReasonInvalid
for retry in range(5):

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: make this a constant RETRY_COUNT or something.

process = None
stop_reason = lldb.eStopReasonInvalid
for retry in range(5):
process = target.LaunchSimple(None, None, self.get_process_working_directory())

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand how not being reliable in reporting TSAN errors would cause target.LaunchSimple to fail to produce a process. I would have expected the process to run to completion and then you have a process in eStateExited. What's actually happening here?

@adrian-prantl adrian-prantl merged commit 6694ebd into swiftlang:swift/release/6.0 Jun 13, 2024
3 checks passed
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.

3 participants