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

Issue metadata

Status: Assigned
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Sign in to add a comment

Issue 812425: quipper build seems to be failing unittests occasionally

Reported by, Feb 14 2018 Project Member

Issue description

Filed by on behalf of

An example failed build:

Failing tests:
quipper-0.0.1-r2369: [----------] Global test environment tear-down
quipper-0.0.1-r2369: [==========] 147 tests from 16 test cases ran. (83498 ms total)
quipper-0.0.1-r2369: [  PASSED  ] 145 tests.
quipper-0.0.1-r2369: [  FAILED  ] 2 tests, listed below:
quipper-0.0.1-r2369: [  FAILED  ] PerfParserTest.ReadsBuildidsInMountNamespace_TriesRootFsRejectsInode
quipper-0.0.1-r2369: [  FAILED  ] PerfParserTest.ReadsBuildidsInMountNamespace_DifferentDevOrIno

Comment 1 by, Feb 14 2018


Comment 2 by, Feb 14 2018

Labels: -Pri-2 Pri-1

Comment 3 by, Feb 14 2018

This CL:

claims quipper comes from github, stored in google storage at gs location: gs://chromeos-localmirror/distfiles/quipper-<GIT SHA1>.tar.gz

Comment 4 by, Feb 14 2018

Comment 5 by, Feb 15 2018

lakshmana@ making you the owner since you probably have the most expertise to help narrow down this one.

Comment 6 by, Feb 15 2018

Labels: -Pri-1 Pri-2
Per lakshmana@'s request, reducing the priority of this bug since it didn't show up in subsequent build.

Comment 7 by, Feb 15 2018

if it's a flaky unittest, i think Pri-1 might not be that inaccurate ... we have enough flakes in our CQ/release as it is :/.

if we don't have a handle on the fix, we could disable it until we do.

Comment 8 by, Feb 21 2018

Status: Assigned (was: Available)
It just happened again:

Comment 9 by, Feb 21 2018

Labels: -Pri-2 Pri-1 Type-Bug
That took out quite a few CLs:
Build lakitu-gpu-paladin failed with not ignorable failures, will not submit changes: CL:*573959 CL:*573965 CL:448976 CL:852560 CL:889412 CL:889413 CL:905384 CL:905577 CL:919504 CL:923404 CL:923405 CL:923416 CL:924113 CL:924303 CL:924506 CL:924763 CL:924764 CL:927444 CL:927606 CL:928846

Setting back to Pri-1

Comment 10 by, Feb 24 2018

RE 7 yes we can disable the test instead, if it is flaky and no handle on a fix.

Comment 11 by, Feb 24 2018 if someone wants to approve it

Comment 12 by, Feb 26 2018

Project Member
The following revision refers to this bug:

commit ec0dacbb614ad7db80ffea4820d6a9aef13fbb65
Author: Mike Frysinger <>
Date: Mon Feb 26 22:10:05 2018

quipper: disable flaky tests

Disable these until someone can figure out how to make them not flaky.

TEST=precq passes

Change-Id: I0f9e68adf2c7dbad81928bc4738d881b1c85665c
Commit-Ready: Mike Frysinger <>
Tested-by: Mike Frysinger <>
Reviewed-by: Aviv Keshet <>
Reviewed-by: Don Garrett <>


Comment 13 by, Feb 26 2018

Labels: -Pri-1 OS-Chrome Pri-2

Comment 14 by, Sep 28

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Comment 15 by, Nov 5


Comment 16 by, Nov 7

Yes, I was the owner.

Sign in to add a comment