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

Issue 806196 link

Starred by 1 user

Issue metadata

Status: Fixed
Closed: Jan 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 0
Type: Bug

Sign in to add a comment

Pre-CQ Uprev stage fails on cros_mark_as_stable

Project Member Reported by, Jan 26 2018

Issue description

In pre-CQ, Uprev stage fails on running cros_mark_as_stable. It's complaining third_party/libapps/nassh/manifest.json is missing.

Example pre-CQ run:

Example failure log:

00:32:19: ERROR: Package crosh-extension failed: return code: 2; command: /b/c/cbuild/repository/src/third_party/chromiumos-overlay/chromeos-base/crosh-extension/files/ /b/c/cbuild/repository/src/third_party/libapps
gawk: fatal: cannot open file `/b/c/cbuild/repository/src/third_party/libapps/nassh/manifest.json' for reading (No such file or directory)
cmd=['/b/c/cbuild/repository/src/third_party/chromiumos-overlay/chromeos-base/crosh-extension/files/', '/b/c/cbuild/repository/src/third_party/libapps']
00:32:19: ERROR: 
return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_mark_as_stable --all '--boards=' '--overlays=...', '--drop_file=/b/c/cbuild/repository/src/scripts/cbuildbot_package.list', 'commit'], cwd=/b/c/cbuild/repository
00:32:19: ERROR: /b/c/cbuild/repository/chromite/bin/cros_mark_as_stable failed (code=1)

I guess this change is the culprit:


Comment 1 by, Jan 26 2018


Comment 2 by, Jan 26 2018

Owner: ----
Status: Available (was: Assigned)
Labels: -Pri-1 Pri-0
Status: Assigned (was: Available)
The CL renames manifest.json, not good.

Revert is here:
Just find the same root cause of last build and thanks for filing the issue and creating revert CL.
Implemented the recommended forward fix in the revert cl:
Project Member

Comment 7 by, Jan 26 2018

The following revision refers to this bug:

commit 907862fd7223303706dc48a4c6ed484d8de365d0
Author: C Shapiro <>
Date: Fri Jan 26 15:29:12 2018

Fix build failure caused by rename

This is an attempt to forward fix the issue by fixing
the filename to the renamed file.

BUG= chromium:806196 
TEST=cros tryjob -g 887976 reef-pre-cq

Change-Id: I22c39abe1f28d384a28d6b048f215a2c7db43313
Reviewed-by: Benjamin Gordon <>
Tested-by: C Shapiro <>


Comment 8 by, Jan 26 2018

Status: Fixed (was: Assigned)
Charles's CL fixed things

Sign in to add a comment