graphics_drm 'null_platform_test' fails on elm |
||||||
Issue description
10/02 07:10:34.492 DEBUG| graphics_Drm:0142| Running test null_platform_test.
10/02 07:10:34.494 DEBUG| utils:0212| Running 'null_platform_test'
10/02 07:10:34.522 DEBUG| utils:0280| [stderr] libEGL warning: DRI2: failed to open vgem (search paths /usr/lib/dri)
10/02 07:10:34.547 DEBUG| utils:0280| [stderr] ERROR:bs_egl_setup():egl.c:116:failed to create OpenGL ES Context: EGL_BAD_CONFIG
10/02 07:10:34.552 DEBUG| utils:0280| [stderr] ERROR:main():null_platform_test.c:136:failed to setup egl context
10/02 07:10:34.553 ERROR| graphics_Drm:0092| Failed: null_platform_test (exit=1)
10/02 07:10:34.560 DEBUG| graphics_Drm:0093| Command <null_platform_test> failed, rc=1, Command returned non-zero exit status
* Command:
null_platform_test
Exit status: 1
Duration: 0.0476360321045
stderr:
libEGL warning: DRI2: failed to open vgem (search paths /usr/lib/dri)
ERROR:bs_egl_setup():egl.c:116:failed to create OpenGL ES Context: EGL_BAD_CONFIG
ERROR:main():null_platform_test.c:136:failed to setup egl context
1
,
Oct 2 2017
+gurchetansingh to see if the recent change to egl.c has impact on the failure. The erro log is at https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/146430301-chromeos-test/chromeos2-row7-rack10-host1/graphics_Drm/debug/?pli=1
,
Oct 2 2017
No, the recent changes to egl.c are unrelated. This CL: https://chromium-review.googlesource.com/c/chromiumos/platform/drm-tests/+/682062 may fix the the issue.
,
Oct 2 2017
I guess this bug refers to the following master-paladin failure: https://chromegw.corp.google.com/i/chromeos/builders/master-paladin/builds/16465 This failure is almost certainly related to the img-mesa update patches: https://chromium-review.googlesource.com/#/c/chromiumos/overlays/chromiumos-overlay/+/673145/ https://chromium-review.googlesource.com/#/c/chromiumos/overlays/chromiumos-overlay/+/678677/ Due to the CQ failure, these 2 patches were rejected from landing. Assigning over to drinkcat to help IMG with further investigation.
,
Oct 2 2017
whoops, our paths crossed. Looks like gurchetan has a better idea.
,
Oct 2 2017
Perhaps there was a CQ-DEPEND=CL:682062 missing from 678677 and 673145?
,
Oct 2 2017
Maybe it is caused by the 2 patches in comment #4. The latest build seems to succede now.
,
Oct 2 2017
The CQ did its job here. CL:673145 now has CQ-DEPEND=CL:682062 in place. Let's close this issue if the CLs now land successfully.
,
Oct 2 2017
Right. For some reason I thought the drm-tests CL had already landed. Thanks for fixing this.
,
Oct 3 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by pho...@chromium.org
, Oct 2 2017