Polymake.jl
Polymake.jl copied to clipboard
oscar-system
Can't locate object method "code" via package "-1"
e.g. https://oscarci.mathematik.uni-kl.de/job/oscar/8703/artifact/logs/build-8703/c-automorphisms.ipynb.log
@benlorenz ?
What is the issue with the cache? We usually just keep it and remove the wrappers when Pkg.build() is run, there are only a few configurations stored there. I don't see anything related to polymake_user in the log.
I've seen this error from time to time (when e.g. changing julia version?), and the standard (?) solution is to wipe ~/.julia/polymake_user... I have no idea what is the root cause though
The line
Can't locate object method "code" via package "-1" (perhaps you forgot to load "-1"?) at /var/jenkins_home/workspace/oscar/local/share/polymake/perllib/Polymake/Core/BigObjectType.pm line 1021.
indicates that polymake was unable to compute some of the requested properties for the object. But the error handling is wrong somewhere so the original error got lost ...
Any way to reproduce this?
Some of these errors seem to result from multiple Polymake instances on the CI server running code concurrently with a shared ~/.polymake directory, leading to race conditions. I've isolated them properly and for now they seem to be working, though it is too early to tell if any of them have fully gone away. We'll see if any of these errors will have reoccurred tomorrow.
After running it on a couple of CI instances overnight, it seems to happen even when race conditions cannot occur, i.e. while running tests in a strictly sequential fashion with no competing jobs. The only way I've found so far to make the error messages go away has been to isolate each test in its on POLYMAKE_USER_DIR, and I'm not certain that this even fixes the issue rather than making it much less likely.
The errors occur when testing against the master branches of all the relevant Oscar packages, which may also be a contributing factor.
Both errors still occur, i.e. both the C++ compilation error and trying to load a "-1" package.
I will try and turn this into a standalone test case that one can debug outside the CI environment.