cunumeric: Error "Current configuration results in zero workers" while running test suite
Hello, I hope you are well. When I attempt to run in the root of the repo:
legate test.py
I receive an error regarding my current configuration:
[0 - 7f7efdb2e000] 0.000046 {4}{threads}: reservation ('Python-1 proc 1d00000000000006') cannot be satisfied
[0 - 7f7df9c89000] 0.511264 {6}{python}: python exception occurred within task:
Traceback (most recent call last):
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legion_top.py", line 477, in legion_python_main
run_path(args[start], run_name='__main__')
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legion_top.py", line 298, in run_path
exec(code, module.__dict__, module.__dict__)
File "test.py", line 47, in <module>
plan = TestPlan(config, system)
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legate/tester/test_plan.py", line 47, in __init__
self._stages = [
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legate/tester/test_plan.py", line 48, in <listcomp>
STAGES[feature](config, system) for feature in config.features
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legate/tester/stages/_linux/cpu.py", line 54, in __init__
self._init(config, system)
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legate/tester/stages/test_stage.py", line 280, in _init
self.spec = self.compute_spec(config, system)
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legate/tester/stages/_linux/cpu.py", line 75, in compute_spec
workers = adjust_workers(len(cpus) // procs, config.requested_workers)
File "/home/walter/anaconda3/envs/simulations/lib/python3.1/site-packages/legate/tester/stages/util.py", line 97, in adjust_workers
raise RuntimeError("Current configuration results in zero workers")
RuntimeError: Current configuration results in zero workers
legion_python: /opt/conda/conda-bld/legate-core_1675127265170/work/build/_deps/legion-src/runtime/realm/python/python_module.cc:996: virtual void Realm::LocalPythonProcessor::execute_task(Realm::Processor::TaskFuncID, const Realm::ByteArrayRef&): Assertion `0' failed.
Signal 6 received by node 0, process 895982 (thread 7f7df9c89000) - obtaining backtrace
Signal 6 received by process 895982 (thread 7f7df9c89000) at: stack trace: 15 frames
[0] = /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f7efdc89520]
[1] = /lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c) [0x7f7efdcdda7c]
[2] = /lib/x86_64-linux-gnu/libc.so.6(raise+0x16) [0x7f7efdc89476]
[3] = /lib/x86_64-linux-gnu/libc.so.6(abort+0xd3) [0x7f7efdc6f7f3]
[4] = /lib/x86_64-linux-gnu/libc.so.6(+0x2871b) [0x7f7efdc6f71b]
[5] = /lib/x86_64-linux-gnu/libc.so.6(+0x39e96) [0x7f7efdc80e96]
[6] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x52805c) [0x7f7efe57805c]
[7] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x4cc6d1) [0x7f7efe51c6d1]
[8] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x4cc746) [0x7f7efe51c746]
[9] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x52b449) [0x7f7efe57b449]
[10] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x4cf34a) [0x7f7efe51f34a]
[11] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x52a494) [0x7f7efe57a494]
[12] = /home/walter/anaconda3/envs/simulations/bin/../lib/librealm.so.1(+0x4d4a6f) [0x7f7efe524a6f]
[13] = /lib/x86_64-linux-gnu/libc.so.6(+0x94b43) [0x7f7efdcdbb43]
[14] = /lib/x86_64-linux-gnu/libc.so.6(+0x126a00) [0x7f7efdd6da00]
Would anyone know how I should call
legate test.py
with proper options or configurations? Thank you!
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 16 (14 by maintainers)
@magnatelee I’ll start with a PR to change the default and make and make and issue about the pinning. Currently we have
--cpu-pin=partial
to mean “pin on platforms where pinning is possible” but maybe be can expand that to mean “pin to the extent possible (regardless of platform)” Broadening that existing meaning would be a smaller change than adding another “mode” entirely.