compare_build_artifacts failing on chromium.win/Windows deterministic |
||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of keishi@google.com compare_build_artifacts failing on chromium.win/Windows deterministic Builders failed on: - Windows deterministic: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Windows%20deterministic
,
Nov 26
This is still failing quite a bit https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Windows%20deterministic/10842 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Windows%20deterministic/10844 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Windows%20deterministic/10846 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Windows%20deterministic/10855 But not always https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Windows%20deterministic/10857 Looking at the stdout its not obvious to me what the difference is between the succeeding and failing runs. Both logs call out a number of binary differences and both mention a few "error:" lines for some troubled gn targets.
,
Nov 26
Figured out how to read the log. Thakis - do you know the right owner for these (or advice on where to go from here)? Unexpected diffs: 2 Unexpected files with diffs: nacl_irt_x86_32.nexe nacl_irt_x86_32.nexe.debug
,
Nov 26
Is it still failing? https://chromium-review.googlesource.com/c/1351089 was supposed to fix this, and all (well, currently 2) builds that have that are green as far as I can tell. I'm not sure what triggered the problem, but I had marked the two new files as expected nondeterministic targets, so the bot should green up.
,
Nov 26
Last three builds have been green, so should be fixed now. thakis@, should we leave this bug open for a proper fix? Or is the nondeterminism expected?
,
Nov 27
It's not expected, but this isn't the right bug to track it. Let's call this one done. |
||||
►
Sign in to add a comment |
||||
Comment 1 by keishi@chromium.org
, Nov 26