Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quick explanation of what the
GC tests for RemoteChannels
test does:RemoteChannel
srr
andfstore
on worker 1 and worker 2 respectively from the master process. At this point only the master process knows aboutrr
andfstore
.put!(fstore, rr)
, i.e. we remotecall worker 2 and putrr
(which is owned worker 1 but is currently only known about by the master) intofstore
.rr
.Step 3 should succeed despite us never previously explicitly communicating with worker 1, because
serialize(::ClusterSerializer, ::RemoteChannel)
will send a message to the owner of theRemoteChannel
to inform them of its existence (seesend_add_client()
). This happens asynchronously in step 2, and on rare occasions worker 1 would not process that message before step 3, causing the test to fail.Now we give the check 10s to succeed.
Should fix failures seen in CI: https://github.com/JuliaParallel/DistributedNext.jl/actions/runs/11880658178/job/33104808773
I was able to reproduce the failure roughly every 30 test executions. Checked this fix by running the tests locally 100 times.