On 2015-08-01, Holger Levsen wrote:
> 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

But wait, there's more:

Cubox-i4pro, quad-core, 2GB ram, ~50GB SATA SSD
ssh port: 2226
ssh fingerprints: 
- 2048 74:e0:b4:50:04:ce:10:b0:e3:91:d9:fd:42:b2:2b:a3 (RSA)
- 256 62:9d:f3:d0:25:87:22:d3:73:43:5d:4a:98:5a:6c:f8 (ECDSA)

> 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

Hrm. No idea on that one...

> 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....

It is considerably more capable, sure. The individual cores on the
Banana PI might be a little more powerful, but the extra ram and extra
cores on the wandboard-quad and cubox-i4pro surely make up for that.

I don't know what "dbd" is...

For starters, I'm not sure it's worth the extra complication to build on
another host, though that does obviously check for reproducibility
issues that might encode build machine-specific info...

live well,

Attachment: signature.asc
Description: PGP signature

Reproducible-builds mailing list

Reply via email to