GetBuildersStatus failed in CommitQueueCompletion
Reported by
jrbarnette@chromium.org,
Apr 14 2017
|
||
Issue description
This build failed:
https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/14252
The build presumably tried to self-destruct because of this failure in
the lakitu paladin:
https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-paladin/builds/6135
Instead, it failed with this output:
07:55:32: INFO: Running cidb query on pid 20732, repr(query) starts with u'SELECT id, build_stage_id, outer_failure_id, exception_type, exception_message, exception_category
07:55:32: INFO: Creating BuilderStatus for builder x86-mario-paladin
@@@STEP_FAILURE@@@
07:55:32: ERROR: Traceback (most recent call last):
File "/b/cbuild/internal_master/chromite/cbuildbot/stages/generic_stages.py", line 628, in Run
self.PerformStage()
File "/b/cbuild/internal_master/chromite/cbuildbot/stages/completion_stages.py", line 919, in PerformStage
super(CommitQueueCompletionStage, self).PerformStage()
File "/b/cbuild/internal_master/chromite/cbuildbot/stages/completion_stages.py", line 293, in PerformStage
statuses = self._FetchSlaveStatuses()
File "/b/cbuild/internal_master/chromite/cbuildbot/stages/completion_stages.py", line 211, in _FetchSlaveStatuses
manager, build_id, db, builder_names, timeout))
File "/b/cbuild/internal_master/chromite/cbuildbot/stages/completion_stages.py", line 915, in _GetSlaveBuildStatus
timeout=timeout)
File "/b/cbuild/internal_master/chromite/cbuildbot/manifest_version.py", line 640, in GetBuildersStatus
builder_status.message.BuildFailureMessageToStr(),
AttributeError: 'NoneType' object has no attribute 'BuildFailureMessageToStr'
In case it's relevant, here's the link to the x86-mario-paladin run:
https://uberchromegw.corp.google.com/i/chromeos/builders/x86-mario-paladin/builds/13208
,
Apr 18 2017
It's affected by CL:462429 patch_number:6. I noticed that and, then I -1 the CL and restarted master-paladin/builds/14253 |
||
►
Sign in to add a comment |
||
Comment 1 by jrbarnette@chromium.org
, Apr 14 2017This CQ run also failed with an identical symptom: https://uberchromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/14253 In this second failure, all of the slave paladins completed successfully.