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

Issue 767716 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2018
Cc:
kmshelton@chromium.org
█ venkatar...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Job status showing as "Queued" while the actual test is running at cautotest, not able to see the logs while test is running.

Project Member Reported by modia@chromium.org, Sep 22 2017 
Ex:

steps to re-produce: 
(1) setup the device at Cassandra stresslab

chromeos1-row1-rack1-host3
chromeos1-row1-rack1-host3-servo

(2) kick off the test at cautotest with create job option

(3) test should kick off and show the status as "running"

What is inspected:

test is able to kick off but showing the status as "queued".  Attaching screen shot for reference.

Confirmed by inspecting the DUT - test is running on DUT, but status is showing as "queued"
status_queued.png
826 KB View Download
missing_Debuglogs.png
663 KB View Download

Comment 1 by modia@chromium.org, Sep 22 2017 

Here, for reference i kicked off the firmware_consecutive boot test with create job option.
firmware_consecutive.png
843 KB View Download

Comment 2 by ayatane@chromium.org, May 17 2018

Status: WontFix (was: Untriaged)
This is because the DUT is sharded.  The real status is on the shard and synced back to the master after the test completes.
►

Sign in to add a comment