h-vetinari commented on PR #13991: URL: https://github.com/apache/arrow/pull/13991#issuecomment-1238337000
> @h-vetinari I regular see Conda segmentation faults on some conda builds, such as this one: https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=33677&view=logs&j=cf796865-97b7-5cd1-be8e-6e00ce4fd8cf&t=88ee2fb8-46fd-5c68-fde3-1c8d31ba2a5f > > ``` > /usr/local/miniconda/etc/profile.d/conda.sh: line 9: 18881 Segmentation fault: 11 "$CONDA_EXE" $_CE_M $_CE_CONDA "$@" > ``` > > Is this a known issue? I've seen the `1 leaked semaphore` stuff occasionally failing builds recently: ``` /usr/local/miniconda/etc/profile.d/conda.sh: line 9: 18881 Segmentation fault: 11 "$CONDA_EXE" $_CE_M $_CE_CONDA "$@" /usr/local/miniconda/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 1 leaked semaphore objects to clean up at shutdown ``` Not sure if related. In any case I opened https://github.com/conda-forge/conda-forge.github.io/issues/1823 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
