Multiple unit test failure: "libgtk-3.so.0: cannot open shared object file: No such file or directory" |
|||||||||||
Issue descriptionBuild failures: https://uberchromegw.corp.google.com/i/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29%2832%29/builds/42427 https://uberchromegw.corp.google.com/i/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29%2832%29/builds/42426 https://uberchromegw.corp.google.com/i/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29%2832%29/builds/42423 (and more...) The stack trace is quite simple: Stack Trace: ******************************************************************************** No crash dump found. ******************************************************************************** Standard output: ******************************************************************************** ../../out/Debug/chrome: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory ******************************************************************************** This seems to be a linking error, potentially caused by BUILD file changes.
,
Jul 11 2017
Ken: are you also seeing this in gpu tests?
,
Jul 11 2017
nednguyen@ kbr@ Can you help me to find the right owner for this issue?
,
Jul 11 2017
Seeing a lot like this https://build.chromium.org/p/chromium.linux/builders/Linux%20Tests%20%28dbg%29%281%29%2832%29/builds/42429 https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.linux%2FLinux_Tests__dbg__1__32_%2F42429%2F%2B%2Frecipes%2Fsteps%2Ftelemetry_unittests%2F0%2Fstdout ../../out/Debug/chrome: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory Should that be on this bot?
,
Jul 11 2017
,
Jul 11 2017
mark@ If this is a specific bot's trouble, does it have to be handled by Infra team?
,
Jul 11 2017
I believe that libgtk-3.so.0 should be provided by the OS, and it appears to be missing here, which sounds like a bot problem to me. That’s why I raised this to Infra-Troopers.
,
Jul 11 2017
,
Jul 11 2017
,
Jul 11 2017
Hmm, not seeing this on these waterfalls: https://build.chromium.org/p/chromium.gpu/console https://build.chromium.org/p/chromium.gpu.fyi/console Were a bunch of new GCE instances just added to the Swarming pool which are misconfigured?
,
Jul 11 2017
We pushed a new OS image last night, and it looks like that image doesn't contain the files. Not sure why yet, but at least part of the reason seems to be that the version of install-build-deps we were running is *really* old :(. We've reverted the image, and are working to repair the existing machines.
,
Jul 11 2017
Remove "Speed>Telemetry" since this is not a Telemetry issue.
,
Jul 11 2017
Can we get libgtk-3.so.0 added (back) to the Trusty image? Could we have caught this when we canaried the new image on chromium-swarm-dev, or is it too specific to test for? Lowering to P1 as the image has been reverted, but keep in mind that it takes up to 24 hours for all VMs to be converted.
,
Jul 12 2017
This looks to be fixed now. Builds have been completing happily for quite some time, and we've modified the swarming bots to auto-quarantine themselves if the library is missing. Thanks particularly to vadimsh@ and maruel@ for repairing the machines. Postmortem to follow ...
,
Jul 12 2017
@smut - the problem is that the pinned version of install-build-deps we're using to create the image is much too old (as per comment #11). We should definitely figure out what we need to do to catch problems like this on the canaries.
,
Jul 12 2017
,
Jul 12 2017
|
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by hongchan@chromium.org
, Jul 11 2017