You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't exactly have a minimal reproducer right now, but when tests improperly terminate (e.g. call sys.exit(1)) we find that the replacing worker will try to access registered_collections while it is not in it. For example when running with pytest -n 2 --dist loadgroup we see the following:
attempted to index with <WorkerController gw2>
attempted to index with <WorkerController gw3>
These are the replacement workers for the crashed workers gw0 and gw1. These lines were printed by the following debug statement I added in loadscope.py:
# Ask the node to execute the workloadtry:
worker_collection=self.registered_collections[node]
except:
print("attempted to index with", node)
raise
Turning off --dist loadgroup fixes the issue. I've reproduced with pytest==8.3.5.
The text was updated successfully, but these errors were encountered:
I don't exactly have a minimal reproducer right now, but when tests improperly terminate (e.g. call
sys.exit(1)
) we find that the replacing worker will try to accessregistered_collections
while it is not in it. For example when running withpytest -n 2 --dist loadgroup
we see the following:Note the following lines:
These are the replacement workers for the crashed workers
gw0
andgw1
. These lines were printed by the following debug statement I added inloadscope.py
:Turning off
--dist loadgroup
fixes the issue. I've reproduced withpytest==8.3.5
.The text was updated successfully, but these errors were encountered: