On Donnerstag, 29. Oktober 2020, 15:39:00 CET Kyle Edwards wrote:

Hello all,

I recently added aarch64 and armv7el architectures to my OBS instance. I'm building for Ubuntu 16.04 and Ubuntu 20.04. However, both aarch64 and armv7el seem to be unavailable for Ubuntu 16.04 - they both say "unresolvable." When I look for more details, I see a long list of "nothing provides <package>." Is there not an aarch64 and armv7el build available for Ubuntu 16.04 on OBS?

we have not configured it for arm. And no, I won't add it now when it is almost EOL ;)

In addition, for Ubuntu 20.04, armv7el says "The repository setup is broken, build or publish is not possible." What does this mean? So far the only one of these four builds that I've managed to get working is aarch64 on Ubuntu 20.04.

Side note: is armv7el the right architecture to use? There's a bunch of different arm-32 architectures, and it's not clear how the OBS arches correspond to the arches for other distros.

depends on what about speak here. If it is the scheduler architecture in OBS, you need to use armv7l instead by default.

On 10/29/20 10:49 AM, Adrian Schröter wrote:

we have not configured it for arm. And no, I won't add it now when it is almost EOL ;)

Heh, good point, thanks.

depends on what about speak here. If it is the scheduler architecture in OBS, you need to use armv7l instead by default.

For the scheduler, yes. I just turned off armv7el and turned on armv7l, but /monitor says armv7l is "dead". I have an aarch64 builder, shouldn't that be able to build armv7l?

Kyle

On 10/29/20 11:48 AM, Adrian Schröter wrote:

the worker might be able to (not all are), but you need the armv7l scheduler.

How can I tell if this is the case? The output of /proc/cpuinfo on my aarch64 machine doesn't provide much info, but I am able to run 32-bit ARM executables on it.

So, restart the obsscheduler service again after adding it.

Tried that, didn't work :(

Kyle

On 10/29/20 1:27 PM, Andreas Schwab wrote:

If you can run 32-bit code you are fine. That means the cpu implements the A32 ISA.

Thanks. In that case there must be something else causing armv7l to show as "dead". Any idea how I can begin debugging this?

Kyle

On 10/30/20 2:51 AM, Adrian Schröter wrote:

who is dead? the worker? the scheduler? is the armv7l scheduler really running?

/monitor on the web interface lists armv7l as an architecture, but there's a red exclamation mark on it that says "dead" when you hover over it. The aarch64 builder is online and should be serving armv7l, and the OBS scheduler lists aarch64 as available, but not armv7l.

Kyle

On 11/2/20 2:47 AM, Adrian Schröter wrote:

So restart the schedulers and when that is not helping look in the logfile of the scheduler.

I restarted the entire server and am still not having any success. I looked at the processes running on the server, and it looks like it's actually running a scheduler for armv7el, but not armv7l. How can I get the armv7l scheduler running? I have armv7l enabled in my projects.

Kyle

On 11/3/20 10:52 AM, Adrian Schröter wrote:

via

# osc api -e /configuration

Thanks. armv7l is already listed here, but the scheduler still isn't running even after a reboot.

Kyle

On 11/3/20 10:55 AM, Adrian Schröter wrote:

then look at the log file as I mentioned before.

The log for the armv7l scheduler does not show any activity since October 13th, even though I just rebooted.

On 11/3/20 11:16 AM, Adrian Schröter wrote:

And

obs_admin --show-scheduler-architectures

is listing it and you do not see a bs_sched process running with that arch?

/usr/lib/obs/server/bs_admin --show-scheduler-architectures shows armv7el, not armv7l, even though both are present in /configuration, and armv7l is enabled on my projects.

Kyle

On 11/4/20 1:52 AM, Adrian Schröter wrote:

so for some reason the configuration file for the backend got not updated.

Please check and rewrite /src/obs/configuration.xml

Thanks, this worked. My armv7l build is now running.

Kyle