-s flag
pip install to build the arkouda package... Building wheels for collected packages: arkouda
Building wheel for arkouda (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /home/users/p02405/anaconda3/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/lus/scratch/tmp/pip-req-build-mra5diqu/setup.py'"'"'; __file__='"'"'/lus/scratch/tmp/pip-req-build-mra5diqu/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /lus/scratch/tmp/pip-wheel-2cq41ur_
cwd: /lus/scratch/tmp/pip-req-build-mra5diqu/
Complete output (30 lines):
/home/users/p02405/anaconda3/lib/python3.8/site-packages/setuptools/dist.py:461: UserWarning: Normalizing 'v2021.08.20+35.g6f5616b.dirty' to '2021.8.20+35.g6f5616b.dirty'
warnings.warn(tmpl.format(**locals()))
running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/arkouda
copying arkouda/groupbyclass.py -> build/lib/arkouda
copying arkouda/io_util.py -> build/lib/arkouda
copying arkouda/pdarrayclass.py -> build/lib/arkouda
copying arkouda/timeclass.py -> build/lib/arkouda
copying arkouda/message.py -> build/lib/arkouda
copying arkouda/sorting.py -> build/lib/arkouda
copying arkouda/logger.py -> build/lib/arkouda
copying arkouda/numeric.py -> build/lib/arkouda
copying arkouda/infoclass.py -> build/lib/arkouda
copying arkouda/strings.py -> build/lib/arkouda
copying arkouda/client.py -> build/lib/arkouda
copying arkouda/security.py -> build/lib/arkouda
copying arkouda/pdarrayIO.py -> build/lib/arkouda
copying arkouda/pdarraysetops.py -> build/lib/arkouda
copying arkouda/_version.py -> build/lib/arkouda
copying arkouda/pdarraycreation.py -> build/lib/arkouda
copying arkouda/__init__.py -> build/lib/arkouda
copying arkouda/dtypes.py -> build/lib/arkouda
copying arkouda/categorical.py -> build/lib/arkouda
copying arkouda/join.py -> build/lib/arkouda
UPDATING build/lib/dist/arkouda/_version.py
error: [Errno 2] No such file or directory: 'build/lib/dist/arkouda/_version.py'
----------------------------------------
ERROR: Failed building wheel for arkouda
Are you pip installing from pypi or are you building your own client package to install (https://github.com/Bears-R-Us/arkouda#install-ak).
You shouldn't install from pypi as we have not updated that in quite some time and it will not work with the current server.
hi all - new to this project. i have just been playing with arkouda for the past month or so.
i am having an issue with using a system where 256 threads are available (2 x 64 core processors with hyperthreading) and am only getting 128ish arkouda threads. how is the number of arkouda threads spun up decided for a given system? it seems there is a default value that applies to smaller machines but not this machine i am trying. Is there a max number of threads? Is there a flag to specify how many threads to spin up when starting the server? Thanks!
CHPL_RT_NUM_THREADS_PER_LOCALE, but generally speaking using logical threads will not help performance and may in fact hurt. See https://chapel-lang.org/docs/usingchapel/tasks.html#controlling-the-number-of-threads for more info.
I'm fairly certain the reason for hanging/failure was the server process dying and the client ZMQ socket waiting for reconnection. If that's the case the test will never actually complete and should be considered failed as soon as the server process dies.
However, if you want to try to increase the time out you can install the pytest-timeout plugin and it enables the cmd line arg --timeout=300 where the value is in seconds. An alternative is to try and use pytest marks to set something on a specific test @pytest.mark.timeout(10, "slow", method-"thread") (from the pytest docs)
4 replies
Zoom Invite
Michael Merrill is inviting you to a scheduled Zoom meeting.
Topic: Arkouda Weekly Zoom Meeting Time: recurring meeting Tuesdays @ 1pm ET
Join Zoom Meeting https://us04web.zoom.us/j/77717000423?pwd=TGlmaUN3L2hScFovTy9NRXNnUTE5dz09
Meeting ID: 777 1700 0423 Passcode: kjM3WS
During your first run you should have gotten a message from gasnet recommending a value for GASNET_PHYSMEM_MAX. This is usually ~2/3 of physical memory or a limit set by the HCA. This limits how much memory can be pinned, but not how much physical memory you can allocate (just how much can be pinned / communicated at any given time).
The amount the server reports comes from https://chapel-lang.org/docs/modules/standard/Memory/Diagnostics.html#Diagnostics.locale.physicalMemory, which should just be the physical memory of a system. Can you run free -g on the nodes to verify the OS reports ~750G and not ~512G?