Compile failing with 'compile confirm no-op' on Linux and Android |
||
Issue descriptionBuilders failed on: - Android: https://build.chromium.org/p/chromium/builders/Android - Google Chrome Linux x64: https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux%20x64 - Cronet bots on the Android waterfall: https://build.chromium.org/p/chromium.android/console Log output has something along the lines of ninja explain: restat of output md5sum_bin_host older than most recent input obj/tools/android/md5sum/md5sum_bin_host.inputdeps.stamp (0 vs 1499220544) ninja explain: md5sum_bin_host is dirty ninja explain: obj/tools/android/md5sum/md5sum_bin_host.stamp is dirty ninja explain: restat of output host_forwarder older than most recent input obj/tools/android/forwarder2/host_forwarder.inputdeps.stamp (0 vs 1499220544) ninja explain: host_forwarder is dirty ninja explain: restat of output host_forwarder_unittests older than most recent input obj/tools/android/forwarder2/host_forwarder_unittests.inputdeps.stamp (0 vs 1499220544) ninja explain: host_forwarder_unittests is dirty These failures didn't start at a consistent time, and are seemingly a bit flaky. Nothing in the recent log looks particularly suspicious. Tagging as an infra issue for the troopers to help investigate, since I can't see anything obvious I can do as Sheriff.
,
Jul 5 2017
The failures seem to have cleared up as of about R484189. The failures seem to have cleared up after that point. Still no indication of what could have caused this.
,
Jul 5 2017
At this stage, I'm pretty sure everything is fixed. I don't know what we can do to stop this happening again, so I'm just going to close this bug.
,
Jul 5 2017
We turned on the "confirm no-op" check in https://chromium-review.googlesource.com/c/558756/ and reverted it in https://chromium-review.googlesource.com/c/559244/.
,
Jul 6 2017
That explains it, thanks! |
||
►
Sign in to add a comment |
||
Comment 1 by tsergeant@chromium.org
, Jul 5 2017