Re: Old and New armhf/arm64 nodes (Firefly-rk3399, Jetson-tx1, Odroid-C2, Raspberry PI2)

2017-06-03 Thread Holger Levsen
On Sat, Jun 03, 2017 at 03:23:35PM -0700, Vagrant Cascadian wrote:
> Hrm. Several hours later, jtx1a and ff64a still appear to be idle,
> according to munin. *sigh*
 
thanks for checking…! (I also wondered why 14 jobs where shown as down
in the performance page but was busy doing some last minute changes for
Stretch…)

the ssh host key is wrong/unknown (because I made a mistake when setting
it up, basically did ssh $host instead of ssh -p $port $host…) and then
I didnt notice because aborting the maintenance+setup jobs didnt work
as it should, by properly changing the job result "to aborted", instead
they were shown as successful…

I've now changed the jenknis_master_wrapper to actually exit with error
in such cases, nowadays that we are not constantly running jenkins
build jobs anymore, the mail flood from this should be handable - and useful.

> We'll get them working eventually. :)

surely!


(havent yet fixed the ssh keys, as I'm still on the properly aborting/exiting
fix first… on it.)

-- 
cheers,
Holger


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Old and New armhf/arm64 nodes (Firefly-rk3399, Jetson-tx1, Odroid-C2, Raspberry PI2)

2017-06-03 Thread Vagrant Cascadian
On 2017-06-03, Holger Levsen wrote:
> On Sat, Jun 03, 2017 at 09:27:38AM -0700, Vagrant Cascadian wrote:
>> On a related note, I haven't noticed any builds on ff64a or jtx1a... did
>> all their partner machines happen to be marked as disabled?
>
> there was a problem with the (new) build service with commented out "jobs"
> which I fixed today, thus those builds should pour in now…

Hrm. Several hours later, jtx1a and ff64a still appear to be idle,
according to munin. *sigh*

We'll get them working eventually. :)


live well,
  vagrant


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Old and New armhf/arm64 nodes (Firefly-rk3399, Jetson-tx1, Odroid-C2, Raspberry PI2)

2017-06-03 Thread Holger Levsen
On Sat, Jun 03, 2017 at 09:27:38AM -0700, Vagrant Cascadian wrote:
> > what's your plan for this machine now? I've currently disabled it's build 
> > jobs.
> Keep troubleshooting it... push the issue upstream and/or put it on the
> back burner... haven't found anything really informative yet.

ok, cool, thanks!
 
> linux 4.11 works with haveged, but not with USB or eMMC (where the
> rootfs is). Kernel 4.12-rc2/rc3 work fine with rootfs, but down't work
> with haveged... I've been running the same kernel on a different machine
> (p64c) without obvious problems, so it is either specific to odroid-c2,
> or maybe to that particular board.

ic

> > also https://tests.reproducible-builds.org/debian/index_performance.html now
> > nicely shows how many build jobs are down due to remote build node problems…
> That's nice, thanks!
 
:) glad you find it useful!

> On a related note, I haven't noticed any builds on ff64a or jtx1a... did
> all their partner machines happen to be marked as disabled?

there was a problem with the (new) build service with commented out "jobs"
which I fixed today, thus those builds should pour in now…


-- 
cheers,
Holger


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Old and New armhf/arm64 nodes (Firefly-rk3399, Jetson-tx1, Odroid-C2, Raspberry PI2)

2017-06-03 Thread Vagrant Cascadian
On 2017-06-03, Holger Levsen wrote:
> On Fri, Jun 02, 2017 at 08:46:14AM -0700, Vagrant Cascadian wrote:
>> > <  h01ger> | odc2a is faster than jtx1a (also io wise, but both are 
>> > rather fine…)
>> > <  h01ger> | odc2a takes ages to generate the gpg key for the jenkins 
>> > user, somehow haveged fails to start…
>> Will experiment with combinations of stretch, kernel versions, etc. and
>> see if it behaves the same.
>  
> what's your plan for this machine now? I've currently disabled it's build 
> jobs.

Keep troubleshooting it... push the issue upstream and/or put it on the
back burner... haven't found anything really informative yet.

linux 4.11 works with haveged, but not with USB or eMMC (where the
rootfs is). Kernel 4.12-rc2/rc3 work fine with rootfs, but down't work
with haveged... I've been running the same kernel on a different machine
(p64c) without obvious problems, so it is either specific to odroid-c2,
or maybe to that particular board.


> also https://tests.reproducible-builds.org/debian/index_performance.html now
> nicely shows how many build jobs are down due to remote build node problems…

That's nice, thanks!


On a related note, I haven't noticed any builds on ff64a or jtx1a... did
all their partner machines happen to be marked as disabled?


live well,
  vagrant


signature.asc
Description: PGP signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Re: Old and New armhf/arm64 nodes (Firefly-rk3399, Jetson-tx1, Odroid-C2, Raspberry PI2)

2017-06-03 Thread Holger Levsen
On Fri, Jun 02, 2017 at 08:46:14AM -0700, Vagrant Cascadian wrote:
> > <  h01ger> | ff64a seems quite slow
> Yes, disk i/o seems likely, although shouldn't be hugely worse than any
> of the other systems...  

I'm not so sure of this but let's see what stats we'll have in a week or so…

> Waiting on native sata hardware to become
> available... so it's currently using a usb-sata adapter. Hopefully that
> will resolve the issue.

*nods*

> > <  h01ger> | odc2a is faster than jtx1a (also io wise, but both are 
> > rather fine…)
> > <  h01ger> | odc2a takes ages to generate the gpg key for the jenkins 
> > user, somehow haveged fails to start…
> Will experiment with combinations of stretch, kernel versions, etc. and
> see if it behaves the same.
 
what's your plan for this machine now? I've currently disabled it's build jobs.

also https://tests.reproducible-builds.org/debian/index_performance.html now
nicely shows how many build jobs are down due to remote build node problems…


-- 
cheers,
Holger


signature.asc
Description: Digital signature
___
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds