In the main directory there's a symlink soloptxmr.py, that points to src/prod.py. The script calls a few Python modules, ultimately to call the opti executable in the build/default-static-release/bin/ directory by default.
Even though calling the individual components that constitute the src/prod.py goes fine, the script hangs the GitHub CI machines. See the workaround in util/ci.sh:
python3 src/tests.py
# Now test unpickling:
python3 src/tests.py
./ci-default -o "VERBOSE_FUNCTIONS=OFF" # <-- it might be helpful to set it to ON
echo "Testing the entire production chain:"
if [ "$(uname)" == "Linux" ]; then
python3 src/prod.py
else
# TODO: Mac OSX suffers from an endless loop (?) in prod.py
#python3 src/prod.py
cd build/default-static-release/bin/
./opti
fi
A good approach would be to run the script in Python's debug mode and pause the execution to see where it hung.
It can be done either by a Mac owner or by somebody (like me) through renting an OSX terminal from a service like https://www.vpsserver.com .
In the main directory there's a symlink
soloptxmr.py, that points tosrc/prod.py. The script calls a few Python modules, ultimately to call theoptiexecutable in thebuild/default-static-release/bin/directory by default.Even though calling the individual components that constitute the
src/prod.pygoes fine, the script hangs the GitHub CI machines. See the workaround inutil/ci.sh:A good approach would be to run the script in Python's debug mode and pause the execution to see where it hung.
It can be done either by a Mac owner or by somebody (like me) through renting an OSX terminal from a service like https://www.vpsserver.com .