-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
llvm sources keep breaking #156
Comments
I just discovered that my issues seem to be entirely due to llvm.org taking extremely long to connect (30+ seconds), such that
@travis-ci: Could you please not redirect this output to Original question still applies: how do we get a recent version of clang on Travis VMs if llvm.org continues to time out? |
I ran into this problem last night as well. Thank you for doing some investigating and getting the conversation started, @jfirebaugh! I'm wondering if there's a flag that can be passed to Given that having sources be up-to-date is necessary for many builds, I'd say that failing to fetch sources should fail the build. What do you think? Should build-failure-on-source-fetch-failure be a default and/or an optional flag? |
llvm.org is down again today, breaking builds. Still looking for a solution here if anyone has one. |
I believe Travis mirrors/caches some APT stuff already (see here). Would it be unduly difficult to get llvm.org's APT source somehow included in that? |
@dirk -- APT caching "is available only for private repositories." |
Someone deleted the entire http://llvm.org/apt/ subdirectory today, again breaking all Travis builds that use the whitelisted packages. |
It looks like llvm.org is no longer going to host packages: http://lists.llvm.org/pipermail/llvm-dev/2016-May/100303.html |
Is there any alternative apt source for llvm/clang or building from source is the only solution? |
Until there is no better solution, I found an llvm-backport ppa created by Alexander Drozdov to download clang 3.7 for trusty. Here is our modified .travis.yml if you are interested. |
what about mirroring useful repos by travis itself? |
This is now a fixed issue I think |
TLDR: Does anyone have a working build on Travis CI using clang >= 3.5?
As far as I can tell, the whitelisted llvm sources stopped working a couple days ago, when llvm released a new version.
I know this may be out of Travis's control, but bear with me: I'd like to use this ticket reach out to other folks and brainstorm solutions. I'm CC'ing some people who have opened or commented on related tickets because they may be facing similar issues right now: @JesseTG, @ldionne, @gnzlbg, @bkentel, @prudhomm.
@gnzlbg summed this up well in travis-ci/apt-package-safelist#561 (comment):
A release just happened, and just as predicted, all of our builds broke. We were using clang 3.5; I haven't been able to get an upgrade to 3.6 working. I posted to the llvm-dev mailing list asking what's up:
So far no response.
Anyone know what's up here?
The text was updated successfully, but these errors were encountered: