New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 795992 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

cyan-paladin often fails with exception

Project Member Reported by levarum@chromium.org, Dec 19 2017

Issue description

Chrome Version: n/a

What steps will reproduce the problem?
Look at https://uberchromegw.corp.google.com/i/chromeos/builders/cyan-paladin?numbuilds=100

What is the expected result?
No 'exception' failures

What happens instead?
There are a lot for 'exception' failures



Please use labels and text to provide additional information.

The stack trace looks like:

Traceback (most recent call last):
  File "/home/chrome-bot/buildbot/build/third_party/twisted_10_2/twisted/internet/defer.py", line 290, in addCallbacks
    self._runCallbacks()
  File "/home/chrome-bot/buildbot/build/third_party/twisted_10_2/twisted/internet/defer.py", line 547, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/home/chrome-bot/buildbot/build/third_party/twisted_10_2/twisted/internet/defer.py", line 365, in callback
    self._startRunCallbacks(result)
  File "/home/chrome-bot/buildbot/build/third_party/twisted_10_2/twisted/internet/defer.py", line 459, in _startRunCallbacks
    self._runCallbacks()
--- <exception caught here> ---
  File "/home/chrome-bot/buildbot/build/third_party/twisted_10_2/twisted/internet/defer.py", line 547, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "/home/chrome-bot/buildbot/build/scripts/master/chromium_step.py", line 1596, in onCommandFinished
    self.scriptComplete(command_result)
  File "/home/chrome-bot/buildbot/build/scripts/master/chromium_step.py", line 1586, in scriptComplete
    self.script_observer.handleReturnCode(cmd.rc)
  File "/home/chrome-bot/buildbot/build/scripts/master/chromium_step.py", line 1481, in handleReturnCode
    reason='return code was %d.' % return_code)
  File "/home/chrome-bot/buildbot/build/scripts/master/chromium_step.py", line 809, in finishCursor
    self.finishStep(self.cursor, status=status, reason=reason)
  File "/home/chrome-bot/buildbot/build/scripts/master/chromium_step.py", line 796, in finishStep
    section['log'].addHeader(msg)
  File "/home/chrome-bot/buildbot/build/third_party/buildbot_8_4p1/buildbot/status/logfile.py", line 462, in addHeader
    self.addEntry(HEADER, text)
  File "/home/chrome-bot/buildbot/build/third_party/buildbot_8_4p1/buildbot/status/logfile.py", line 414, in addEntry
    assert not self.finished
exceptions.AssertionError: 
 
This seems to be common among many builders, e.g. caroline, kevin, etc.  But there seems to be no common exception pattern?  Given that this is CQ, it could also be that the in-flight change is bad, too.

If there is something bothering in particular, we should also loop the sheriffs in.  But I don't see an action item here (except for maybe understand how they failed)?
For cyan all 10 recent exceptions ended up with the stack trace above. That doesn't look like a bad CL.

We just need a trooper to look into this, but seems like there is no trooper coverage this week...
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>CI
Status: Archived (was: Untriaged)

Sign in to add a comment