Summary:

• We pushed 1,018 code changes to our mercurial-based repos. Over the month, this translates into:
• 11,279 build/unittest jobs, or ~15.7 jobs per hour.
• 5,837 talos jobs, or ~8 talos jobs per hour.
• TryServer now does linux-arm and WinMo builds, which creates extra load per push.
• The mozilla-1.9.1 branch has a few bursts of activity, but you can see attention moving to mozilla-central, as post-3.5 work starts to open up.
• Aki just pointed out that we’re not yet tracking mobile-browser branch or the l10n repacks. Also, in July we are spinning up new places branch, electrolysis branch, mozilla-1.9.2 branch, so expect to see them in next month’s report.

Details:

As each of these pushes triggers multiple different types of builds/unittest jobs, the math is:

• mozilla-central: 12 jobs per push (L/M/W opt, L/M/W leaktest, L/M/W unittest, linux64 opt, linux-arm, WinMo)
• mozilla-1.9.1: 12 jobs per push (L/M/W opt, L/M/W leaktest, L/M/W unittest, linux64 opt, linux-arm, WinMo)
• tracemonkey: 7 jobs per push (L/M/W opt, L/M/W unittest, linux64 opt)
• try: 11 jobs per push (L/M/W opt, L/M/W leaktest, L/M/W unittest, linux-arm, WinMo)
• theoretical total: (515 x 12) + (130 x 12) + (141 x 7) + (232 x 11) = 11,279 jobs per month = 15.7 jobs per hour.

Now that we have pooled all the talos slaves, we can count triggered talos jobs for every opt build as follows:

• mozilla-central: 6 jobs per push (ubuntu, osx10.4, osx10.5, WinVista, WinXP, linux-arm)
• mozilla-1.9.1: 5 jobs per push (ubuntu, osx10.4, osx10.5, WinVista, WinXP)
• tracemonkey: 5 jobs per push (ubuntu, osx10.4, osx10.5, WinVista, WinXP)
• try: 5 jobs per push (ubuntu, osx1.4, osx10.5, WinVista, WinXP)
• theoretical total: (515 x 6) + (130 x 5) + (141 x 5) + (232 x 6) = 5837 jobs per month = 8 jobs per hour.