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

Issue 834473 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

[Findit] Completion of build-aheads is not being persisted in the datastore.

Project Member Reported by robert...@chromium.org, Apr 18 2018

Issue description

Project Member

Comment 1 by bugdroid1@chromium.org, Apr 18 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/c83edda6822ce3663678a57ecfb2125f29882708

commit c83edda6822ce3663678a57ecfb2125f29882708
Author: Roberto Carrillo <robertocn@google.com>
Date: Wed Apr 18 22:53:29 2018

[Findit] Make MarkComplete persist the build ahead try job record.

As soon as MarkComplete is called, we should persist the state of the
try job so that any failure in the handler does not make it lose this
knowledge.

R=chanli,lijeffrey,stgao

Bug:  834473 
Change-Id: I0407eb1a6c5221400c22ccb2561169f808bda803
Reviewed-on: https://chromium-review.googlesource.com/1018000
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Commit-Queue: Roberto Carrillo <robertocn@chromium.org>

[modify] https://crrev.com/c83edda6822ce3663678a57ecfb2125f29882708/appengine/findit/model/test/build_ahead_try_job_test.py
[modify] https://crrev.com/c83edda6822ce3663678a57ecfb2125f29882708/appengine/findit/model/build_ahead_try_job.py

Status: Fixed (was: Started)

Sign in to add a comment