Issue metadata
Sign in to add a comment
|
compile failure on chromium/Win x64 |
||||||||||||||||||||
Issue descriptioncompile failure on chromium/Win x64 Builders failed on: - Win x64: https://build.chromium.org/p/chromium/builders/Win%20x64 Log Snippet: 22699/50303] ACTION //net/http:transport_security_state_unittest_data(//build/toolchain/win:x64) FAILED: gen/net/http/transport_security_state_static_unittest2.h C:/b/depot_tools/python276_bin/python.exe ../../build/gn_run_binary.py transport_security_state_generator.exe ../../net/http/transport_security_state_static_unittest2.json ../../net/http/transport_security_state_static_unittest.pins ../../net/http/transport_security_state_static_unittest.template gen/net/http/transport_security_state_static_unittest2.h [22701/50303] ACTION //net/http:transport_security_state_unittest_data(//build/toolchain/win:x64) FAILED: gen/net/http/transport_security_state_static_unittest1.h C:/b/depot_tools/python276_bin/python.exe ../../build/gn_run_binary.py transport_security_state_generator.exe ../../net/http/transport_security_state_static_unittest1.json ../../net/http/transport_security_state_static_unittest.pins ../../net/http/transport_security_state_static_unittest.template gen/net/http/transport_security_state_static_unittest1.h [22706/50303] ACTION //net/http:transport_security_state_unittest_data(//build/toolchain/win:x64) FAILED: gen/net/http/transport_security_state_static_unittest3.h C:/b/depot_tools/python276_bin/python.exe ../../build/gn_run_binary.py transport_security_state_generator.exe ../../net/http/transport_security_state_static_unittest3.json ../../net/http/transport_security_state_static_unittest.pins ../../net/http/transport_security_state_static_unittest.template gen/net/http/transport_security_state_static_unittest3.h Reverting r464391 as the likely culprit.
,
Apr 13 2017
,
Apr 13 2017
rch@, I reverted your CL as a likely culprit for the compilation error. Do you mind taking another look at this?
,
Apr 13 2017
Given that my CL landed via the CQ and passed win 64 bots, this is super surprising. In addition, I didn't change anything related to net/http/transport_security_state_static_unittest2.h How confident are you that my CL was the culprit?
,
Apr 13 2017
It is possible that the CQ bots had a pre-existing generated version of gen/net/http/transport_security_state_static_unittest*.h and thus this wasn't caught by them. Given that your CL was the only one touching files in //net/ in the hours before the error and the build passed after reverting your CL I am quite confident that your CL was indeed the culprit. However, please feel free to reassign this bug if you think another CL is responsible.
,
Apr 13 2017
If the CQ bots have a pre-existing generated version of gen/net/http/transport_security_state_static_unittest*.h and my CL is actually the culprit (in a win 64 specific fashion) do you have a suggestion for how to repro this? I don't really want to land again and just cross my fingers, but I'm not sure what the alternative is. :(
,
Apr 13 2017
Looking at the Win 64 bot, my CL was first built by: https://build.chromium.org/p/chromium/builders/Win%20x64/builds/10396 This build succeeded. The bot failed on the next build: https://build.chromium.org/p/chromium/builders/Win%20x64/builds/10397 My CL was not on the blamelist for that build The next build after that was: https://build.chromium.org/p/chromium/builders/Win%20x64/builds/10398 Which was successful again and did NOT include the revert of my CL. The revert was first built by: https://build.chromium.org/p/chromium/builders/Win%20x64/builds/10399 So if my CL is at fault, it means we have some sort of non-determinism in the build :(
,
Apr 13 2017
Ok, I re-landed and the build looks stable so I'm going to close this bug. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by bugdroid1@chromium.org
, Apr 13 2017