Skip to content

Conversation

@cachemeifyoucan
Copy link

Fix a potential issue that can cause new clang scan daemon failed to start when the previous daemon timed out at the same time. It is possible for the timed out daemon still hold pid file when being shutdown, when the new clang daemon is starting up and failed to lock the pid file. To the new clang daemon, this is indistinguishable from losing the race to start a new daemon with another clang invocation, thus the new starting request will be dropped and no daemon will be started.

Fix a potential issue that can cause new clang scan daemon failed to
start when the previous daemon timed out at the same time. It is
possible for the timed out daemon still hold pid file when being
shutdown, when the new clang daemon is starting up and failed to lock
the pid file. To the new clang daemon, this is indistinguishable from
losing the race to start a new daemon with another clang invocation,
thus the new starting request will be dropped and no daemon will be
started.
@cachemeifyoucan
Copy link
Author

@swift-ci please test llvm

Copy link

@hamishknight hamishknight left a comment

Choose a reason for hiding this comment

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

Thanks!

@cachemeifyoucan cachemeifyoucan merged commit 5595098 into swiftlang:next Nov 14, 2025
0 of 2 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