Open IainNZ opened 9 years ago
Part of the message looks the same as https://github.com/JuliaOpt/Ipopt.jl/issues/41, as if configure didn't run under Ipopt's ThirdParty/Blas/build
. Can we figure out which package was first responsible for installing Ipopt and/or CoinOptServices and find its full log? There's some persistence problem with a patch file.
AmplNLWriter I think: http://pkg.julialang.org/?pkg=AmplNLWriter&ver=release
(alphabetical)
Is the VM supposed to be clean before starting?
Yep, its clean
With the exception, of course, anything set up by the provisioning script
If that's the case, then what's up with this?
INFO: Computing test dependencies for AmplNLWriter...
INFO: Installing BinDeps v0.3.12
INFO: Installing Cbc v0.1.6
INFO: Installing Clp v0.0.9
INFO: Installing CoinOptServices v0.0.5
INFO: Installing FactCheck v0.2.8
INFO: Installing Ipopt v0.1.15
INFO: Installing LightXML v0.1.11
INFO: Installing SHA v0.0.4
INFO: Installing URIParser v0.0.5
INFO: Building Cbc
INFO: Building Ipopt
INFO: Attempting to Create directory /home/vagrant/.julia/v0.3/Ipopt/deps/downloads
INFO: Directory /home/vagrant/.julia/v0.3/Ipopt/deps/downloads already created
INFO: Downloading file http://www.coin-or.org/download/source/Ipopt/Ipopt-3.12.1.tgz
INFO: Done downloading file http://www.coin-or.org/download/source/Ipopt/Ipopt-3.12.1.tgz
INFO: Attempting to Create directory /home/vagrant/.julia/v0.3/Ipopt/deps/src
INFO: Directory /home/vagrant/.julia/v0.3/Ipopt/deps/src already created
INFO: Attempting to Create directory /home/vagrant/.julia/v0.3/Ipopt/deps
INFO: Directory /home/vagrant/.julia/v0.3/Ipopt/deps already created
INFO: Attempting to Create directory /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1
INFO: Directory /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1 already created
INFO: Changing Directory to /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1
INFO: Changing Directory to /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1/ThirdParty/Blas
INFO: Attempting to Create directory build
INFO: Directory build already created
INFO: Changing Directory to /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1/ThirdParty/Blas
INFO: Changing Directory to /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1
INFO: Changing Directory to /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1/ThirdParty/Blas/build
INFO: Changing Directory to /home/vagrant/.julia/v0.3/Ipopt/deps/src/Ipopt-3.12.1/ThirdParty/Blas/build
make: *** No rule to make target `install'. Stop.
================================[ ERROR: Ipopt ]================================
Also note that AbstractDomains starts by uninstalling Cbc and Ipopt and a few other things. Wha?
On nightly AmplNLWriter is getting terminated, probably due to a timeout.
Maybe things aren't getting cleaned like they should be?
Huh. I have a hunch, I did terminate the VMs the night before last in a weird way (i.e. killall
). I'm wondering if somehow Vagrant started from there, running the provisioning script but not on a fresh virtual HDD. I'll go in there and really clear it out.
OK everything is clean now. Could leave this open until tomorrow, or just close it - up to you.
If I could login to julia.mit.edu right now, I would double-check whether re-running Pkg.build
when partial sources are already present can be made any more robust. I'll leave this open as a to-do, but I'm not sure whether I can do much here.
Seems fine today
AmplNLWriter is still failing due to a timeout though
PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their tests (if available) on both the stable version of Julia (0.3) and the nightly build of the unstable version (0.4). The results of this script are used to generate a package listing enhanced with testing results.
On Julia 0.3
Tests pass.
Tests fail.
This issue was filed because your testing status became worse. No additional issues will be filed if your package remains in this state, and no issue will be filed if it improves. If you'd like to opt-out of these status-change messages, reply to this message saying you'd like to and @IainNZ will add an exception. If you'd like to discuss PackageEvaluator.jl please file an issue at the repository. For example, your package may be untestable on the test machine due to a dependency - an exception can be added.
Test log: