Repository navigation
Go builds erroring #1727
Description
Part of the automated scripts for preparing Go programs is erroring.
$ gvm use go1.1
Now using version go1.1
$ export GOPATH=$HOME/gopath:$GOPATH
$ mkdir -p $HOME/gopath/src/github.com/CasualSuperman
$ cp -r $TRAVIS_BUILD_DIR $HOME/gopath/src/github.com/CasualSuperman/Diorite
cp: cannot stat `$HOME/build/CasualSuperman/Diorite': No such file or directory
Which is odd because the same commands were run and worked perfectly in previous builds. Perhaps $TRAVIS_BUILD_DIR has been improperly set? It looks like $HOME wasn't expanded.
Activity
roidrage commentedon Dec 9, 2013
It does indeed look like that. I found the offending commit: travis-ci/travis-build@ff00dad
jmarshall commentedon Dec 9, 2013
Also appears to be the cause of these build failures (in C, so build failures are not limited to Go), in which
is supposed to enable later test scripts to run a
bgzipexecutable in the tabix subdirectory, butdavecgh commentedon Dec 9, 2013
I can confirm this as well. I've tried multiple Go projects which previously worked and they are all failing with this same error.
roidrage commentedon Dec 9, 2013
Thanks guys, we have found the error, and we're working on a fix.
Trying to fix
hack(travis): temporarily fix travis
roidrage commentedon Dec 10, 2013
Fix for this is currently rolling out.
davecgh commentedon Dec 10, 2013
This is still failing for me -- https://travis-ci.org/conformal/btcchain. Does it need a completely new build instead of just hitting the restart build button?
roidrage commentedon Dec 10, 2013
@davecgh I'm sorry, I'm not sure the error you're seeing is related to this issue.
I'm no go export, but it looks like there are compilation issues with a dependent library?
davecgh commentedon Dec 10, 2013
@roidrage: Thanks for your response. I should've posted the error in particular rather than just the link. It is:
I'm seeing the same error with more than one project. I've not had any issues previously.
roidrage commentedon Dec 10, 2013
@davecgh it may be that you're seeing an old version of the build logs: https://s3.amazonaws.com/archive.travis-ci.org/jobs/15161198/log.txt
davecgh commentedon Dec 10, 2013
@roidrage: Thanks. The jobs web page is indeed showing an old version of the build logs. Accessing them with the raw link shows the correct ones. It does appear to be another issue.
Return to using $TRAVIS_BUILD_DIR (for flexibility)