Builds failing on travis

Question

Builds failing on travis

felipeochoa opened this issue 6 years ago · comments

I think something changed in the travis environment, because make -f emacs-travis.mk install_emacs now fails with the following error:

Warning: Your system has a gap between BSS and the
heap (2525848 bytes). This usually means that exec-shield
or something similar is in effect. The dump may
fail because of this. See the section about
exec-shield in etc/PROBLEMS for more information.

make[2]: *** [bootstrap-emacs] Segmentation fault (core dumped)
make[1]: *** [src] Error 2
make: *** [install_emacs] Error 2
The command "make -f emacs-travis.mk install_emacs" failed and exited with 2 during .

Here are a couple of failed builds:

Greg Hendershott · Answer 1 · Mon Jan 15 2018 03:57:39 GMT+0800 (China Standard Time)

I'm seeing the same thing.

A Travis CI "CRON" build from about a month ago succeeded.
But suddenly yesterday a CRON build of the exact same commit failed.

fmdkdd · Answer 2 · Mon Jan 15 2018 04:57:56 GMT+0800 (China Standard Time)

Indeed, I'm seeing failures as well after emptying the cache on our Travis builds. Compiling Emacs from source now fails. In fact, I'm getting a core dump trying to compile (24.5) on my machine as well, so it might not be an issue with Travis:

/bin/sh: line 7:  8304 Segmentation fault      (core dumped) ./temacs --batch --load loadup bootstrap

And the emacs-travis script hasn't changed since the succeeded builds, so I don't think it's the issue either.

Edit: 25.3 compiles fine on my machine. Not on Travis.

Greg Hendershott · Answer 3 · Mon Jan 15 2018 11:18:57 GMT+0800 (China Standard Time)

Although I don't really know anything about building Emacs, I want to help somehow.

I know how to read blog posts and how to push buttons to see what happens. 😄 In that spirit:

I noticed this Travis blog post in December: New Trusty images are now live!. OK that sounds suspicious.
I tried its recipe to downgrade to the previous image and things seem to work again. Yay.
The Travis blog post asks for people to report issues.
- I don't see this on their list of known issues.
- Should you raise it here? (Although I'm happy to, it would probably carry more weight if you do?)

fmdkdd · Answer 4 · Mon Jan 15 2018 19:07:53 GMT+0800 (China Standard Time)

Looks like this is it! It seems to work fine with the previous Trusty image. I'll add the workaround to the README until the issue is resolved.

Should you raise it here?

Done. Thank you for finding a workaround 👍

Felipe · Answer 5 · Mon Jan 15 2018 21:34:07 GMT+0800 (China Standard Time)

@greghendershott Thanks a ton Greg! The change worked for me: https://travis-ci.org/felipeochoa/rjsx-mode/builds/329049924.

@fmdkdd From my POV, this issue is resolved, and it seems like it's more a travis issue. Feel free to close if you like!

fmdkdd · Answer 6 · Mon Jan 15 2018 21:47:49 GMT+0800 (China Standard Time)

@felipeochoa Thanks for reporting. I'll keep this open until the upstream issue is fixed. I'm not sure if the workaround can work in the long run (i.e., if Travis drops the previous image completely).

Greg Hendershott · Answer 7 · Tue Jan 16 2018 00:19:01 GMT+0800 (China Standard Time)

Yes. Also: Needing to use sudo: required to get the older image, means using a different infrastructure.

fmdkdd · Answer 8 · Fri Jan 19 2018 00:51:15 GMT+0800 (China Standard Time)

Update: the issue seems to be with container-based builds specifically, and not the update from December. See travis-ci/travis-ci#9061 (and this comment specifically).

That means sudo: required is necessary for building Emacs, but we can at least use the current image.

An alternative would be to grab binaries instead of building from source. See EVM and https://github.com/npostavs/emacs-travis/releases.