Skip to content

Conversation

JDevlieghere
Copy link

We weren't setting the listener back to the unhijacked one in this
case, so that a continue after the stop fails. It thinks the process
is still running. Also add tests for this behavior.

Differential Revision: https://reviews.llvm.org/D112747

(cherry picked from commit e655769)

We weren't setting the listener back to the unhijacked one in this
case, so that a continue after the stop fails.  It thinks the process
is still running.  Also add tests for this behavior.

Differential Revision: https://reviews.llvm.org/D112747

(cherry picked from commit e655769)
@JDevlieghere
Copy link
Author

@swift-ci please test

Copy link

@jimingham jimingham left a comment

Choose a reason for hiding this comment

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

This looks correct, we we missing a place where we needed to restore the process events, and that leads to a stall where we can no longer continue. The patch is right. Also, this went through review when submitted to llvm.org and has been in place for months now. We don't have any local differences that would require changes.

@JDevlieghere
Copy link
Author

Unrelated failure

@swift-ci please test macos

@JDevlieghere
Copy link
Author

17:04:13   Swift(macosx-x86_64) :: Distributed/Runtime/distributed_actor_func_calls_remoteCall_takeThrowReturn.swift

@JDevlieghere
Copy link
Author

@swift-ci please test macos

@JDevlieghere JDevlieghere merged commit 1893335 into stable/20211026 Jan 30, 2022
@JDevlieghere JDevlieghere deleted the 🍒/austria/e655769c4a7b5a17b17eace3bd160b3b015b75ed branch January 30, 2022 19:55
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