1175635 - Why no tests in a particular try run?

Status: RESOLVED DUPLICATE of bug 1175701

(Release Engineering :: General, defect)

Description

[Milan Sreckovic [:milan] (needinfo for best results)]

Here's this run, with try: -b d -p win32,win64 -u all -t none
https://treeherder.mozilla.org/#/jobs?repo=try&revision=75d5caabad7c

and here is this run, same request try: -b d -p win32,win64 -u all -t none
https://treeherder.mozilla.org/#/jobs?repo=try&revision=eacce28c98b6

The first one did XP, 7 and 8 x64 debug builds and a bunch of tests.  The second one XP and 8 x64 debug builds, and no tests.

Yet another one: https://treeherder.mozilla.org/#/jobs?repo=try&revision=0fb1d17692e7 also with the same try string did XP and 8 x64 debug builds, and 8 x64 tests.

What gives?  Why no tests on two out of three of these?

Comment 1

[Phil Ringnalda (:philor)]

14:29:19     INFO - ##### Running sendchange step.
14:29:19     INFO - #####
14:29:19     INFO - Running pre-action listener: influxdb_recording_pre_action
14:29:19     INFO - Running main action method: sendchange
14:29:19     INFO - 'enable_talos_sendchange' is false; skipping
14:29:19     INFO - Running command: ['c:\\mozilla-build\\python27\\python.exe', 'c:\\mozilla-build\\buildbotve\\scripts\\buildbot', 'sendchange', '--master', 'buildbot-master81.build.mozilla.org:9301', '--username', 'sendchange-unittest', '--branch', 'try-win32-debug-unittest', '-r', u'eacce28c98b6e2be79f5f36e3487d52db0b23f13', '--username', u'[e-mail]', '--comments', 'try: -b d -p win32,win64 -u all -t none', '--property', 'buildid:20150616132629', '--property', 'pgo_build:False', '--property', 'builduid:328ab5a737234a1a9909135c1f903c62', u'https://queue.taskcluster.net/v1/task/B4nnGoSiTe-6FAF6kveL2A/artifacts/public/build/firefox-41.0a1.en-US.win32.zip', u'https://queue.taskcluster.net/v1/task/B4nnGoSiTe-6FAF6kveL2A/artifacts/public/build/test_packages.json']
14:29:19     INFO - Copy/paste: c:\mozilla-build\python27\python.exe c:\mozilla-build\buildbotve\scripts\buildbot sendchange --master buildbot-master81.build.mozilla.org:9301 --username sendchange-unittest --branch try-win32-debug-unittest -r eacce28c98b6e2be79f5f36e3487d52db0b23f13 --username [e-mail] --comments "try: -b d -p win32,win64 -u all -t none" --property buildid:20150616132629 --property pgo_build:False --property builduid:328ab5a737234a1a9909135c1f903c62 https://queue.taskcluster.net/v1/task/B4nnGoSiTe-6FAF6kveL2A/artifacts/public/build/firefox-41.0a1.en-US.win32.zip https://queue.taskcluster.net/v1/task/B4nnGoSiTe-6FAF6kveL2A/artifacts/public/build/test_packages.json
14:29:19     INFO -  c:\mozilla-build\python27\python.exe: can't open file 'c:\mozilla-build\buildbotve\scripts\buildbot': [Errno 2] No such file or directory
14:29:19    ERROR - Return code: 2
14:29:19     INFO - The sendchange failed but we don't want to turn the build orange: 2

Comment 2

[Milan Sreckovic [:milan] (needinfo for best results)]

When these happen, do I need a new try run, or do I just restart the build step?  Or something else?

Comment 3

[Phil Ringnalda (:philor)]

That depends on why it actually failed, which I don't know.

I'm a little suspicious about how both of the slaves that failed have a slavealloc note of "Bug 1164214 Puppet Test Pool", which might well mean that those five slaves fail sendchange every single time, and nobody has said anything about it. In that case, "just retrigger the build, and hope you don't get one of those five a second time."