Re: [Reproducible-builds] ARM build machines
Hi, so on https://jenkins.debian.net/view/reproducible/ you can now see 12 armhf related jobs, so there is a setup_pbuilder_testing, setup_schroot_testing_debbindiff and a maintenance job for each of the four armhf build hosts. IOW: remote job scheduling now works \o/ What's missing now to make use of them: - dpkg 1.18.1.0~reproducible5 ftbfs in clean sid chroot, this needs to be fixed - the scheduler needs to be taught how to schedule armhf - the build script needs to be taught to deal with remote hosts Stay tuned. cheers, Holger P.S.: yes, in future those amd64 specific jobs should also be renamed to reflect that. signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] ARM build machines
Hi, On Montag, 3. August 2015, Vagrant Cascadian wrote: Oops. Accidentally dropped it on one of the debian.net updates. Re-added just now, got the ack that it was added, now just need to wait for DNS propagation... thanks! (as you may notice, they're all CNAMEs with a consistant pattern, so you could try accessing them directly in a pinch...) yes, I knew the IP, but prefered to get this fixed instead of working around it :) cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] ARM build machines
On 2015-08-03, Holger Levsen wrote: On Samstag, 1. August 2015, Vagrant Cascadian wrote: wbq0-armhf-rb.debian.net: $ host wbq0-armhf-rb.debian.net Host wbq0-armhf-rb.debian.net not found: 3(NXDOMAIN) Oops. Accidentally dropped it on one of the debian.net updates. Re-added just now, got the ack that it was added, now just need to wait for DNS propagation... (as you may notice, they're all CNAMEs with a consistant pattern, so you could try accessing them directly in a pinch...) 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: [Reproducible-builds] ARM build machines
Hi Vagrant, On Samstag, 1. August 2015, Vagrant Cascadian wrote: wbq0-armhf-rb.debian.net: $ host wbq0-armhf-rb.debian.net Host wbq0-armhf-rb.debian.net not found: 3(NXDOMAIN) The others resolve just fine. cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] ARM build machines
Hi, https://reproducible.debian.net/index_repositories.html now shows missing armhf binaries too, so we can see which binNMUs we need to do... Next thing to do: fix dpkg as described in http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150727/002569.html You might also be interested in https://jenkins.debian.net/userContent/todo.html#_reproducible_debian_armhf cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] ARM build machines
Hi Vagrant, On Samstag, 1. August 2015, Vagrant Cascadian wrote: Added new machine... wbq0-armhf-rb.debian.net: Wandboard Quad, quad-core, 2GB ram, ~50GB SATA SSD [...] Holger, I've added access for you with the same key, so tear it up! cool, thanks, done :) btw, on my first git clone this happened: holger@wbq0:~$ git clone git://git.debian.org/git/qa/jenkins.debian.net.git Cloning into 'jenkins.debian.net'... fatal: unable to connect to git.debian.org: git.debian.org[0: moszumanska.debian.org:9418]: Name or service not known A second run that cloned successfully! Do you agree this machine is at least double as powerful as the hb0 and rpi0? [13:04] h01ger | mapreri: re: remote building: i think we should start simple, and only do the 2nd build on another host, scp the results to the first host and run dbd there [13:05] h01ger | i'm not 100% how to do this with the three armhf builds, but lets start this way for amd64 because then we could maybe run 2 builds on wbq0 and do the 2nd builds on rpi0 and hb0 cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] ARM build machines
On 2015-07-27, Vagrant Cascadian wrote: The current specs: bpi0-armhf-rb.debian.net: Banana PI, dual-core, 1GB ram, ~20GB mSATA. ssh port: ssh fingerprints: 2048 8f:0a:d0:77:a8:59:c0:bb:d0:76:de:14:13:5b:a6:56 (RSA) 256 af:b4:13:04:21:30:46:b3:e8:79:ff:7d:99:20:86:f0 (ECDSA) hb0-armhf-rb.debian.net: HummingBoard i2ex, dual-core, 1GB ram, ~20GB mSATA. ssh port: 2224 ssh fingerprints: - 2048 04:af:b4:e8:f0:13:13:66:25:7b:e3:d6:ee:b3:0d:0a (RSA) - 256 2f:1b:3a:fb:55:cf:27:3f:f6:de:e4:3d:e1:4c:59:c8 (ECDSA) Added new machine... wbq0-armhf-rb.debian.net: Wandboard Quad, quad-core, 2GB ram, ~50GB SATA SSD ssh port: 2225 ssh fingerprints: - 2048 ca:04:3e:d6:92:7c:32:20:1e:2f:d7:41:df:29:19:15 (RSA) - 256 4f:57:be:2e:aa:a4:7d:b2:6d:18:8a:d3:35:5e:df:a6 (ECDSA) Holger, I've added access for you with the same key, so tear it up! 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: [Reproducible-builds] ARM build machines
On 2015-07-28, Holger Levsen wrote: do you need to be cc:ed? I am subscribed to the list as of a few weeks ago. On Montag, 27. Juli 2015, Vagrant Cascadian wrote: So I set about trying to patch u-boot and test reproducibility myself, only to discover that the reproducible toolchain didn't include arm packages... yes, we either need to make sure to manually build there in future too, or setup some autobuilders... Would it be feasible to use the same machines for that? I've currently got two up and running, but it sounds like there's more work to do on the backend to integrate with jenkins and other infrastructure... yes, we need to make some changes to our infrastructure as well: - add scheduling for armhf - have jenkins jobs to prepare pbuilder chroots for armhf on these machines - add support for building on remote machines - integrate the armhf build results into the web ui Regarding scheduling, I think we'll need a *lot* more nodes to get real archive coverage, or maybe selectively schedule packages for builds that are known or suspected to have architecture-specific divergence (e.g. builds different packages on different architectures). how is the network connectivity? I assume we want to use a proxy, though I have no idea whether one for both machines or one on each machine (though with 20gb diskspace there is not really space for a proxy...) Network isn't amazingly fast, but there's a squid-deb-proxy on the local network for package caching with ~40GB for the cache, and it could be expanded if needed. Let me know if you need access to these machines to configure them. yes, we need access. Preferedly root/sudo, else user ssh access (account name holger for me please) and we need a jenkins users with a quite liberal sudoers.d... Will give you access and free reign to set up as you wish. :) 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: [Reproducible-builds] ARM build machines
Hi Vagrant, On Dienstag, 28. Juli 2015, Vagrant Cascadian wrote: I am subscribed to the list as of a few weeks ago. ok cool! yes, we either need to make sure to manually build there in future too, or setup some autobuilders... Would it be feasible to use the same machines for that? yes, totally. yes, we need to make some changes to our infrastructure as well: - add scheduling for armhf - have jenkins jobs to prepare pbuilder chroots for armhf on these machines - add support for building on remote machines - integrate the armhf build results into the web ui Regarding scheduling, I think we'll need a *lot* more nodes to get real archive coverage, or maybe selectively schedule packages for builds that are known or suspected to have architecture-specific divergence (e.g. builds different packages on different architectures). /me nods, though I'm not too worried about this: a.) we should start with unstable only b.) some delay (in armhf) is acceptable as long as amd64 is build soon after uploads (and we can schedule interesting armhf packages manually too) c.) I'm sure we can add more nodes easily. I also have idling arm hw Network isn't amazingly fast, but there's a squid-deb-proxy on the local network for package caching with ~40GB for the cache, and it could be expanded if needed. that's totally cool! You'll need to tell the name of that proxy eventually :-) yes, we need access. Preferedly root/sudo, else user ssh access (account name holger for me please) and we need a jenkins users with a quite liberal sudoers.d... Will give you access and free reign to set up as you wish. :) cool, thanks! cheers, Holger signature.asc Description: This is a digitally signed message part. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
