New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 663926 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

x86-alex-paladin graphics_GLMark2.bvt-cq test failure

Project Member Reported by nxia@chromium.org, Nov 9 2016

Issue description


https://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex-paladin/builds/26069/steps/HWTest%20%5Bbvt-cq%5D/logs/stdio


11/09 10:39:19.647 DEBUG|        retry_util:0123| Encountered unexpected exception <class 'autotest_lib.client.common_lib.error.NoEligibleHostException'>(NoEligibleHostException: No hosts within board:x86-alex satisfy hw_video_acc_h264, cros-version:x86-alex-paladin/R56-8974.0.0-rc4, pool:cq, board:x86-alex.
Traceback (most recent call last):
  File "/usr/local/autotest/frontend/afe/json_rpc/serviceHandler.py", line 114, in dispatchRequest
    results['result'] = self.invokeServiceEndpoint(meth, args)
  File "/usr/local/autotest/frontend/afe/json_rpc/serviceHandler.py", line 154, in invokeServiceEndpoint
    return meth(*args)
  File "/usr/local/autotest/frontend/afe/rpc_handler.py", line 270, in new_fn
    return f(*args, **keyword_args)
  File "/usr/local/autotest/frontend/afe/rpc_utils.py", line 1347, in replacement
    return func(**kwargs)
  File "/usr/local/autotest/frontend/afe/rpc_interface.py", line 1033, in create_job
    **rpc_utils.get_create_job_common_args(locals()))
  File "/usr/local/autotest/frontend/afe/rpc_utils.py", line 1019, in create_job_common
    atomic_group=atomic_group)
  File "/usr/local/autotest/frontend/afe/rpc_utils.py", line 621, in create_new_job
    check_job_metahost_dependencies(metahost_objects, dependencies)
  File "/usr/local/autotest/frontend/afe/rpc_utils.py", line 362, in check_job_metahost_dependencies
    % (metahost.name, ', '.join(job_dependencies)))
NoEligibleHostException: No hosts within board:x86-alex satisfy hw_video_acc_h264, cros-version:x86-alex-paladin/R56-8974.0.0-rc4, pool:cq, board:x86-alex.
), not retrying.
11/09 10:39:19.647 DEBUG|             suite:0831| video_ChromeHWDecodeUsed.h264 not applicable for this board/pool. Emitting TEST_NA.


xixuan@, can you take a quick look the NoEligibleHostException here? Is it caused by the lab or the test?
 

Comment 1 by nxia@chromium.org, Nov 9 2016

Cc: amstan@chromium.org jcliang@chromium.org vbendeb@chromium.org
Cc: posciak@chromium.org
Pawel, do you know anything about this failure?
Status: Available (was: Untriaged)
I think the errors in #1 in not the real cause of failure. All the video tests were safely ignored. The bvt-cq failed because graphics_GLMark2 was aborted:

"""
  Suite job                                 [ PASSED ]
  video_ChromeHWDecodeUsed.h264             [  INFO  ]
  video_ChromeHWDecodeUsed.h264               TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.vp9.mse          [  INFO  ]
  video_ChromeHWDecodeUsed.vp9.mse            TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.vp8.arc          [  INFO  ]
  video_ChromeHWDecodeUsed.vp8.arc            TEST_NA: Skipping:  test not supported on this board.
  video_ChromeRTCHWDecodeUsed               [  INFO  ]
  video_ChromeRTCHWDecodeUsed                 TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.vp8.mse          [  INFO  ]
  video_ChromeHWDecodeUsed.vp8.mse            TEST_NA: Skipping:  test not supported on this board.
  video_ChromeRTCHWEncodeUsed.arc           [  INFO  ]
  video_ChromeRTCHWEncodeUsed.arc             TEST_NA: Skipping:  test not supported on this board.
  telemetry_LoginTest.arc                   [  INFO  ]
  telemetry_LoginTest.arc                     TEST_NA: Skipping:  test not supported on this board.
  video_VideoSanity.h264.arc                [  INFO  ]
  video_VideoSanity.h264.arc                  TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.vp8              [  INFO  ]
  video_ChromeHWDecodeUsed.vp8                TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.vp9              [  INFO  ]
  video_ChromeHWDecodeUsed.vp9                TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.vp9.arc          [  INFO  ]
  video_ChromeHWDecodeUsed.vp9.arc            TEST_NA: Skipping:  test not supported on this board.
  video_ChromeCameraMJpegHWDecodeUsed       [  INFO  ]
  video_ChromeCameraMJpegHWDecodeUsed         TEST_NA: Skipping:  test not supported on this board.
  video_ChromeCameraMJpegHWDecodeUsed.arc   [  INFO  ]
  video_ChromeCameraMJpegHWDecodeUsed.arc     TEST_NA: Skipping:  test not supported on this board.
  video_VideoSanity.vp8.arc                 [  INFO  ]
  video_VideoSanity.vp8.arc                   TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.h264.arc         [  INFO  ]
  video_ChromeHWDecodeUsed.h264.arc           TEST_NA: Skipping:  test not supported on this board.
  graphics_Idle.arc                         [  INFO  ]
  graphics_Idle.arc                           TEST_NA: Skipping:  test not supported on this board.
  video_ChromeRTCHWEncodeUsed               [  INFO  ]
  video_ChromeRTCHWEncodeUsed                 TEST_NA: Skipping:  test not supported on this board.
  video_ChromeHWDecodeUsed.h264.mse         [  INFO  ]
  video_ChromeHWDecodeUsed.h264.mse           TEST_NA: Skipping:  test not supported on this board.
  video_ChromeRTCHWDecodeUsed.arc           [  INFO  ]
  video_ChromeRTCHWDecodeUsed.arc             TEST_NA: Skipping:  test not supported on this board.
  video_VideoSanity.vp9.arc                 [  INFO  ]
  video_VideoSanity.vp9.arc                   TEST_NA: Skipping:  test not supported on this board.
  desktopui_ExitOnSupervisedUserCrash.arc   [  INFO  ]
  desktopui_ExitOnSupervisedUserCrash.arc     TEST_NA: Skipping:  test not supported on this board.
  graphics_GLMark2.bvt-cq                   [ FAILED ]
  graphics_GLMark2.bvt-cq                     ABORT: Timed out, did not run.
"""

Interestingly, it seems that the graphics_GLMark2.bvt-cq test actually passed on the chromeos2-row6-rack6-host1:

https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/84834984-chromeos-test/chromeos2-row6-rack6-host1/

I see a database error when the master autoserv was writing the keyval:

"""
11/09 11:04:22.051 ERROR|                db:0169| 11:04:22 11/09/16: An operational error occured during a database operation: (2006, 'MySQL server has gone away')
11/09 11:05:00.368 INFO |        server_job:0153| START	----	x86-alex-paladin/R56-8974.0.0-rc4/bvt-cq/graphics_GLMark2.bvt-cq	timestamp=1478718300	localtime=Nov 09 11:05:00	
11/09 11:05:00.369 INFO |        server_job:0153| 	ABORT	----	x86-alex-paladin/R56-8974.0.0-rc4/bvt-cq/graphics_GLMark2.bvt-cq	timestamp=1478718300	localtime=Nov 09 11:05:00	
11/09 11:05:00.370 INFO |        server_job:0153| END ABORT	----	x86-alex-paladin/R56-8974.0.0-rc4/bvt-cq/graphics_GLMark2.bvt-cq	timestamp=1478718300	localtime=Nov 09 11:05:00	
"""

Is this a infra issue?
The log in the first comment is not a test failure, but an indication that the test is not running on this board as expected (TEST_NA).

We decide whether to run a video test based on the labels applied to the board. Alex doesn't have h264 acceleration, so it doesn't have the "hw_video_acc_h264" label and we don't run the test, which results in TEST_NA.

The failure for graphics_GLMark2.bvt-cq seems to be a different issue from the above.

Comment 5 by nxia@chromium.org, Nov 10 2016

xixuan@, can you follow comment#3 and see if it's an infra issue. Why was the test aborted.

Comment 6 by nxia@chromium.org, Nov 11 2016

Cc: -xixuan@chromium.org
Owner: xixuan@chromium.org
Assigning this to xixuan for more investigation. Feel free to pass this bug to the right owner with your findings.
Status: WontFix (was: Available)
Feels to me that test graphics_GLMark2 is completed, but aborted during parsing. Mark it as won't fix since this issue is observed not frequently. 

When deputy found this issue more often, this will become a fix-it issue.
Labels: OS-Chrome
Please also see  issue 678009 .

Sign in to add a comment