Project

General

Profile

Bug #3061

OsmoTRX ARM chroot build jobs failing due to proot bug

Added by pespin almost 2 years ago. Updated 10 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
03/13/2018
Due date:
% Done:

0%

Spec Reference:

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 issues

Related to OsmoTRX - Bug #3766: Sporadic jenkins failureClosed01/24/2019

Related to OsmoTRX - Feature #4301: set up raspi4 build slave for jenkinsIn Progress12/03/2019

History

#1 Updated by msuraev 11 months ago

  • Related to Bug #3766: Sporadic jenkins failure added

#2 Updated by laforge 11 days ago

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?

#3 Updated by pespin 10 days ago

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)

#4 Updated by laforge 10 days ago

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?

#5 Updated by pespin 10 days ago

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?

#6 Updated by laforge 9 days ago

  • Related to Feature #4301: set up raspi4 build slave for jenkins added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)