quipper build seems to be failing unittests occasionally |
||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of snanda@google.com An example failed build: https://luci-milo.appspot.com/buildbot/chromeos/coral-paladin/2542 Failing tests: quipper-0.0.1-r2369: [0;32m[----------] [mGlobal test environment tear-down quipper-0.0.1-r2369: [0;32m[==========] [m147 tests from 16 test cases ran. (83498 ms total) quipper-0.0.1-r2369: [0;32m[ PASSED ] [m145 tests. quipper-0.0.1-r2369: [0;31m[ FAILED ] [m2 tests, listed below: quipper-0.0.1-r2369: [0;31m[ FAILED ] [mPerfParserTest.ReadsBuildidsInMountNamespace_TriesRootFsRejectsInode quipper-0.0.1-r2369: [0;31m[ FAILED ] [mPerfParserTest.ReadsBuildidsInMountNamespace_DifferentDevOrIno
,
Feb 14 2018
,
Feb 14 2018
This CL: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/683315 claims quipper comes from github, stored in google storage at gs location: gs://chromeos-localmirror/distfiles/quipper-<GIT SHA1>.tar.gz
,
Feb 14 2018
https://luci-milo.appspot.com/buildbot/chromeos/sentry-paladin/2308 another fail that is exactly the same
,
Feb 15 2018
lakshmana@ making you the owner since you probably have the most expertise to help narrow down this one.
,
Feb 15 2018
Per lakshmana@'s request, reducing the priority of this bug since it didn't show up in subsequent build.
,
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.
,
Feb 21 2018
It just happened again: https://luci-milo.appspot.com/buildbot/chromeos/lakitu-gpu-paladin/2827
,
Feb 21 2018
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
,
Feb 24 2018
RE 7 yes we can disable the test instead, if it is flaky and no handle on a fix.
,
Feb 24 2018
https://chromium-review.googlesource.com/936227 if someone wants to approve it
,
Feb 26 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/ec0dacbb614ad7db80ffea4820d6a9aef13fbb65 commit ec0dacbb614ad7db80ffea4820d6a9aef13fbb65 Author: Mike Frysinger <vapier@chromium.org> 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. BUG=chromium:812425 TEST=precq passes Change-Id: I0f9e68adf2c7dbad81928bc4738d881b1c85665c Reviewed-on: https://chromium-review.googlesource.com/936227 Commit-Ready: Mike Frysinger <vapier@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Don Garrett <dgarrett@chromium.org> [modify] https://crrev.com/ec0dacbb614ad7db80ffea4820d6a9aef13fbb65/chromeos-base/quipper/quipper-9999.ebuild [add] https://crrev.com/ec0dacbb614ad7db80ffea4820d6a9aef13fbb65/chromeos-base/quipper/files/quipper-disable-flaky-tests.patch
,
Feb 26 2018
,
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.
,
Nov 5
,
Nov 7
Yes, I was the owner. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by snanda@chromium.org
, Feb 14 2018