[Qa-jenkins-scm] [jenkins.debian.net] 01/01: reproducible debian: explain we're testing i386 now too

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit 541dced67b58c1f1ecaaaa35dd8b36f59a493bf8
Author: Holger Levsen <holger at layer-acht.org>
Date:   Sat Mar 26 22:17:28 2016 -0400

    reproducible debian: explain we're testing i386 now too
---
 README      | 4 ++--
 THANKS.head | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/README b/README
index ebc2336..3613101 100644
--- a/README
+++ b/README
@@ -135,9 +135,9 @@ Installation tests inside chroot environments.
 
 * The (current) purpose of https://tests.reproducible-builds.org is to show the prospects of reproducible builds for Debian - and six other projects currently. This is research, showing what could (and should) be done... check https://wiki.debian.org/ReproducibleBuilds for the real status of the project for Debian!
 
-* 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 50 for 'armhf', which are each constantly testing packages and saving the results of these tests.
+* Currently, three suites are tested on 'amd64', 'i386' 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, 16 for 'amd64' and 'i386' each, and 50 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].
+** These builds on remote nodes run on very different hardware: for 'amd64' and 'i386' we are using two virtual machines each, profitbricks-build(1+5)-amd64 and profitbricks-build(2+6)-i386, 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 18 small boards donated by vagrant at d.o:
 *** three quad-cores (cbxi4a, cbxi4b and ff4a) with 4gb ram, 
 *** three octo-cores (odxu4, odxu4b and odxu4c) with 2gb ram, 
diff --git a/THANKS.head b/THANKS.head
index c52a51a..1438cdd 100644
--- a/THANKS.head
+++ b/THANKS.head
@@ -5,11 +5,11 @@
  * Since October 2012 jenkins.debian.net has been running on (virtualized) hardware sponsored by link:https://www.profitbricks.co.uk[Profitbricks] - Thanks a lot! Currently we are using:
  ** 23 cores and 64 GB memory for jenkins.debian.net
  ** 18 cores and 48 GB memory for profitbricks-build1-amd64.debian.net
- ** 18 cores and 48 GB memory for profitbricks-build2-amd64.debian.net
+ ** 18 cores and 48 GB memory for profitbricks-build2-i386.debian.net
  ** 8 cores and 16 GB memory for profitbricks-build3-amd64.debian.net
  ** 4 cores and 8 GB memory for profitbricks-build4-amd64.debian.net
  ** 17 cores and 48 GB memory for profitbricks-build5-amd64.debian.net
- ** 17 cores and 48 GB memory for profitbricks-build6-amd64.debian.net
+ ** 17 cores and 48 GB memory for profitbricks-build6-i386.debian.net
  ** 3 cores and 6 GB memory for freebsd-jenkins.debian.net (also running on Profitbricks virtual hardware)
  * link:https://qa.debian.org/developer.php?login=vagrant%40debian.org[Vagrant] provides and hosts 18 'armhf' systems:
  ** three quad-cores with 4 GB RAM each,

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git