From 3f92ac3de94fb14019e809cb385ebcab3e34647e Mon Sep 17 00:00:00 2001 From: Holger Levsen Date: Sun, 6 Mar 2016 00:57:59 +0100 Subject: reproducible armhf: fix typo --- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README b/README index 3f20e9d4..b8963ea4 100644 --- a/README +++ b/README @@ -138,7 +138,7 @@ Installation tests inside chroot environments. * Currently, three suites are tested on 'amd64' and 'armhf' architectures: 'testing', 'unstable' and 'experimental'. The tests are done using 'pbuilder' using link:https://wiki.debian.org/ReproducibleBuilds/ExperimentalToolchain[our toolchain] through concurrent builder jobs, 32 for 'amd64' and 42 for 'armhf', which are each constantly testing packages and saving the results of these tests. ** These builds on remote nodes run on very different hardware: for 'amd64' we are now using four virtual machines, profitbricks-build(1+2+5+6)-amd64, which have 18 or 17 cores and 48gb ram each and are sponsored by link:https://jenkins.debian.net/userContent/thanks.html[Profitbricks]. -** To test 'armhf' we are using 16 small boards donated by vagrant@d.o: eleven quad cores (cbxi4a and cbxi4b) with 4gb ram, nine quad cores (wbq0, cbxi4pro0, ff2a, ff2b odxu4, odxu4b, odxu4c, opi2a and opi2b) with 2gb ram, two quad-cores (rpi2b and rpi2c) with 1gb ram and three dual cores (bpi0, hb0 and wbd0) with 1gb ram, each. We would love to have more or more powerful ARM hardware in the future, if you can help, please talk to us! +** To test 'armhf' we are using 16 small boards donated by vagrant@d.o: two quad cores (cbxi4a and cbxi4b) with 4gb ram, nine quad cores (wbq0, cbxi4pro0, ff2a, ff2b odxu4, odxu4b, odxu4c, opi2a and opi2b) with 2gb ram, two quad-cores (rpi2b and rpi2c) with 1gb ram and three dual cores (bpi0, hb0 and wbd0) with 1gb ram, each. We would love to have more or more powerful ARM hardware in the future, if you can help, please talk to us! * Packages to be build are scheduled in the SQLite database via a scheduler job, which runs every hour and if the queue is below a certain threshold schedules four types of packages: ** new untested packages (either uploaded to 'unstable' or 'experimental' or migrated to 'testing'), -- cgit v1.2.3-70-g09d2