search

JuliaCI / PackageEvaluator.jl

A tool to evaluate the quality of Julia packages.
http://pkg.julialang.org
MIT License
35 stars 32 forks source link

Consistent VM failures #200

Open ararslan opened 6 years ago

ararslan commented 6 years ago

This has been keeping PackageEvaluator from updating things since early March. One of the VMs (usually thirdPZ06 it seems) fairly consistently fails to provision. The message emitted by Vagrant from the run on 26 March is:

An action 'provision' was attempted on the machine 'thirdPZ06', but another process is already executing an action on the machine. Vagrant locks each machine for access by only one process at a time. Please wait until the other Vagrant process finishes modifying this machine, then try again.

If you believe this message is in error, please check the process listing for any "ruby" or "vagrant" processes and kill them. Then try again.

The machine provisioned on the 28 March run, but instead emitted similar errors regarding up and destroy rather than provision. This appears not to have been fatal, however, as the file containing the results of the 0.6 tests for packages P-Z does exist. This particular run actually failed because thirdGO07 claimed not to have Nullables installed, so JSON failed to load, which means that no 0.7GO.json file was created, thereby crashing the part of the process that tries to read all of the results .json files.

Interestingly, the cronjob.jl file hits a SIGTERM somewhere along the line when dealing with thirdPZ06. The full log for 28 March is here: https://gist.github.com/ararslan/d3b585855c950d092616c97d5be5f167.

I'm currently running vagrant box update, hopefully that makes a difference in the next run (30 March). In the meantime, any insight into this would be much appreciated.