graphics_Gbm autotest appears to be flakey |
|||
Issue descriptionLatest failure was on x86-alex paladin: https://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex-paladin/builds/26507 https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/94542941-chromeos-test/chromeos4-row4-rack2-host3/debug/ autoserv.DEBUG: 01/05 12:28:47.647 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: START graphics_Gbm graphics_Gbm timestamp=1483648126 localtime=Jan 05 12:28:46 01/05 12:28:47.647 INFO | server_job:0153| START graphics_Gbm graphics_Gbm timestamp=1483648126 localtime=Jan 05 12:28:46 01/05 12:28:55.353 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: FAIL graphics_Gbm graphics_Gbm timestamp=1483648134 localtime=Jan 05 12:28:54 Failed: Gbm test failed (CHECK failed in check_bo() gbmtest.c:133 01/05 12:28:55.354 INFO | server_job:0153| FAIL graphics_Gbm graphics_Gbm timestamp=1483648134 localtime=Jan 05 12:28:54 Failed: Gbm test failed (CHECK failed in check_bo() gbmtest.c:133 01/05 12:28:55.355 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: CHECK failed in test_import_vgem() gbmtest.c:504 01/05 12:28:55.355 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: CHECK failed in check_bo() gbmtest.c:133 01/05 12:28:55.355 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: CHECK failed in test_import_dmabuf() gbmtest.c:539 01/05 12:28:55.356 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: CHECK failed in check_bo() gbmtest.c:133 01/05 12:28:55.356 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: CHECK failed in test_import_planar() gbmtest.c:589 01/05 12:28:55.356 DEBUG| site_autotest:0194| AUTOTEST_STATUS:: [ FAILED ] graphics_Gbm test failed Searching this database for graphics_Gbm shows lots more failures. I didn't see any CL that could obviously cause this failure. Thank you Stephane!
,
Jan 5 2017
Are you sure? What about these: ☆ 654157 ---- ---- 1 ---- ---- Untriaged ---- [bvt-cq] graphics_Gbm Failure on kevin-release/R56-8873.0.0 autofiled Chrome Oct 8 ☆ 647268 ---- ---- 1 ---- ---- ---- ---- [bvt-cq] graphics_Gbm Failure on kevin-release/R54-8743.29.0 autofiled Chrome Nov 23 ☆ 641985 ---- ---- 1 ---- ---- ---- ---- [bvt-cq] graphics_Gbm Failure on kevin-release/R54-8743.3.0 autofiled Chrome Oct 9 ☆ 641818 ---- ---- 1 ---- ---- ---- ---- [bvt-cq] graphics_Gbm Failure on kevin-release/R55-8750.0.0 autofiled Chrome Sep 8 ☆ 641354 ---- ---- 1 ---- ---- Untriaged ---- [bvt-cq] graphics_Gbm Failure on samus-release/R54-8743.0.0 autofiled Chrome Aug 26 ☆ 641344 ---- ---- 1 ---- ---- ---- ---- [bvt-cq] graphics_Gbm Failure on auron_yuna-release/R54-8743.0.0 autofiled Chrome Oct 4 ☆ 626586 ---- ---- 1 ---- ---- Untriaged ---- [bvt-cq] graphics_Gbm Failure on stumpy-release/R53-8530.7.0 autofiled Chrome Jul 8 ☆ 625396 ---- ---- 1 ---- ---- Untriaged ---- [bvt-cq] graphics_Gbm Failure on ultima-release/R52-8350.49.0 autofiled Chrome Jul 2 ☆ 621293 ---- ---- 1 ---- ---- Untriaged ---- [bvt-cq] graphics_Gbm Failure on ninja-release/R52-8350.34.0 autofiled Chrome Jun 2016
,
Jan 5 2017
Yes it's a good test which catches bugs. What else am I supposed to say?
,
Jan 5 2017
(also less than a dozen failures in 6 months)
,
Jan 5 2017
Sorry Stephane! I figured the paladins would have caught those bugs. Thanks.
,
Jan 5 2017
Oh... I was confused by the <board>-release suffix... those were all CQ runs :/ Also some of them were infrastructure problems. :/ :/
,
Jan 5 2017
@6: not all, the original report on alex is a real failure catching a bad CL. |
|||
►
Sign in to add a comment |
|||
Comment 1 by marc...@chromium.org
, Jan 5 2017