Bug #3061
open
OsmoTRX ARM chroot build jobs failing due to proot bug
Added by pespin about 6 years ago.
Updated over 4 years ago.
Description
Since we moved to new jenkins nodes, proot doesn't seem to be working properly, and it fails always with "terminated with signal 31". It doesn't seem to be related to the ARM rootfs, as the issue still appears when using proot without it.
There's a bug open upstream to track the issue. I updated it: https://github.com/proot-me/PRoot/issues/134
Meanwhile, let's disable the ARM related axis to avoid failure on all jobs:
--with-neon
--with-neon-vfpv4
Since the change is temporary (hopefully), I'll just manually edit the job through jenkins web UI for now.
- Related to Bug #3766: Sporadic jenkins failure added
is there anything else we can do to work around this? We could e.g. use a Raspi as a jenkins build slave and do the arm builds there? Would that help us?
I can spend time again on it to see if it's fixed in a newer version of PRoot. Having an ARM buildhost may be an interesting idea, but I'm not sure how can we run jenkins job twice for x86 and arm (on a raspberrypi)
On Mon, Dec 02, 2019 at 09:31:28AM +0000, pespin [REDMINE] wrote:
I can spend time again on it to see if it's fixed in a newer version of PRoot.
the bug ticket is still open, I doubt it makes sense.
Having an ARM buildhost may be an interesting idea
I'll buy a Raspi4, it is a quad-core 64bit ARM and contrary to many
other boards can be obtained with 4GB of RAM, which should improve
compilation speeds.
but I'm not sure how can we run jenkins job twice for x86 and arm (on a raspberrypi)
I doubt it would be different to jenkins than e.g. running a job on
debian8 and debian8, or for linux+freebsd as we did in the past?
I'll buy a Raspi4, it is a quad-core 64bit ARM and contrary to many
other boards can be obtained with 4GB of RAM, which should improve
compilation speeds.
Fine with me.
I doubt it would be different to jenkins than e.g. running a job on
debian8 and debian8, or for linux+freebsd as we did in the past?
I guess it's the same, but I don't know how it used to be set up... matrix job?
- Related to Feature #4301: set up raspi4 build slave for jenkins added
Also available in: Atom
PDF
