https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=amd64-generic-paladin&buildBranch=master

From the history of amd64-generic-paladin build results, the first failure happened at this build:

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8930843837090195008

It does not look like there was any CL in that build triggered this failure.

In an old build that passed, I can see both mesa and minigbm are built:

https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8930860251967473808/+/steps/BuildPackages/0/stdout

I am not sure whether this is a real issue.

I just had a fresh checkout.
amd64-generic build_package passed with no issue.


[ebuild  N     ] media-libs/mesa-18.2_pre1-r24::chromiumos to /build/amd64-generic/ USE="classic dri egl gallium gles2 llvm nptl shared-glapi -X -cros_h
ost -debug -drm -gbm -gles1 -pic -selinux -vulkan -wayland -xlib-glx" VIDEO_CARDS="intel llvmpipe nouveau radeon -amdgpu -freedreno -mach64 -mga -r128 -
radeonsi -savage -sis -softpipe -tdfx -via -virgl -vmware" 0 KiB       


[ebuild  N     ] media-libs/minigbm-0.0.1-r244::chromiumos to /build/amd64-generic/ USE="-asan -coverage -cros_host -fuzzer -msan -ubsan" VIDEO_CARDS="i
ntel radeon -amdgpu -exynos -marvell -mediatek -msm -radeonsi -rockchip -tegra -vc4 -virgl" 0 KiB                                                       
[ebuild  N     ] chromeos-base/crosvm-0.0.1-r238::chromiumos to /build/amd64-generic/ USE="crosvm-wl-dmabuf -cros_host -crosvm-gpu -crosvm-plugin -debug
" 273 KiB 


emerge-amd64-generic -p --cols --quiet --root /var/empty -e virtual/target-os

listed 


 N     media-libs/mesa 18.2_pre1-r24 to /var/empty/ 
 N     media-libs/minigbm 0.0.1-r244 to /var/empty/ 

So it looks great.


In contrast, in the CQ build failure log, we have

B      media-libs/mesa[gbm] ("media-libs/mesa[gbm]" is blocking media-libs/minigbm-0.0.1-r244)


So the problem is why CQ build wanted mesa[gbm]:

 media-libs/mesa[gbm] required by (media-libs/virglrenderer-0.7.0_p20180919-r2:0/0::chromiumos, ebuild scheduled for merge to '/var/empty/')


And I checked in my chroot:

(cr) ((ac3eeb2...)) cychiang@cychiang-z840 ~/trunk/src/scripts $ equery-amd64-generic d virglrenderer
 * These packages depend on virglrenderer:
chromeos-base/crosvm-0.0.1-r238 (crosvm-gpu ? media-libs/virglrenderer)

[ebuild  N     ] chromeos-base/crosvm-0.0.1-r238::chromiumos to /build/amd64-generic/ USE="crosvm-wl-dmabuf -cros_host -crosvm-gpu -crosvm-plugin -debug
" 273 KiB 

So in my chroot, crosvm-gpu was not used.

Need to check why it was used in the buildbot.

+zachr

I could not find where the crosvm-gpu is set to that build.

Searching on the crbug, I saw this one might be related:

https://bugs.chromium.org/p/chromium/issues/detail?id=837073#c21

https://cros-goldeneye.corp.google.com/chromeos/legoland/builderHistory?buildConfig=amd64-generic-paladin&buildBranch=master
Looking at the history, I found that the issue happened on swarm-cros-459 for last 11 builds.
The latest build at swarm-cros-450 does not have this issue.
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8930722874630067104

So it might be something wrong with swarm-cros-459.

I clicked "Shutdown gracefully" on swarm-cros-459 status page:
https://chrome-swarming.appspot.com/bot?id=swarm-cros-459&sort_stats=total%3Adesc

Not sure if I need to do anything to bring it back.