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

Issue 711585 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

cbuildbot always fails unless using --do-not-use-buildbucket

Project Member Reported by norvez@chromium.org, Apr 14 2017

Issue description


See for example:
https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10496
https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10497

Those were launched with something like:
$ cbuildbot --remote --profile=aosp -g *354727 amd64-generic-cheets-release

Note that this is a draft CL, but that's not the issue, that bot failed too, and it was just ToT:
https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10487


Passing --do-not-use-buildbucket  works around the issue:
https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/release/10499
 
Cc: nxia@chromium.org
Interesting. This looks like some kind of CIDB integrity issue.

@@@STEP_FAILURE@@@
20:28:17: ERROR: <class 'sqlalchemy.exc.IntegrityError'>: (IntegrityError) (1062, "Duplicate entry '8982374072949266512' for key 'buildbucket_id_index'") 'INSERT INTO `buildTable` (master_build_id, buildbot_generation, builder_name, waterfall, build_number, build_config, bot_hostname, start_time, important, buildbucket_id) VALUES (%s, %s, %s, %s, %s, %s, %s, CURRENT_TIMESTAMP, %s, %s)' (None, 1, 'release', 'chromiumos.tryserver', 10496, u'amd64-generic-cheets-release', 'build46-m2.golo.chromium.org', False, '8982374072949266512')
Traceback (most recent call last):
  File "/b/cbuild/repository/chromite/lib/failures_lib.py", line 190, in wrapped_functor
    return functor(*args, **kwargs)
  File "/b/cbuild/repository/chromite/cbuildbot/stages/report_stages.py", line 258, in PerformStage
    raise e
IntegrityError: (IntegrityError) (1062, "Duplicate entry '8982374072949266512' for key 'buildbucket_id_index'") 'INSERT INTO `buildTable` (master_build_id, buildbot_generation, builder_name, waterfall, build_number, build_config, bot_hostname, start_time, important, buildbucket_id) VALUES (%s, %s, %s, %s, %s, %s, %s, CURRENT_TIMESTAMP, %s, %s)' (None, 1, 'release', 'chromiumos.tryserver', 10496, u'amd64-generic-cheets-release', 'build46-m2.golo.chromium.org', False, '8982374072949266512')


I don't understand why your tryjob would be different from any other kind.
I'm wondering if this was a transient issue unrelated to buildbucket. Re-running a tryjob now, just to see.
Status: WontFix (was: Unconfirmed)
I don't think this is buildbucket related. My tryjob just passed, even though it was launched that way.

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/release/builds/10534

Comment 4 by norvez@chromium.org, Apr 15 2017

An overnight tryjob worked for me too. Agreed, looks like a transient issue.

Sign in to add a comment