The message doesn't indicate an error; it indicates that the
selected board doesn't provide the hardware support required
for the given test.

The fact that this bug got filed means that the message needs
to get fixed.

Also:  Bugs in the Chrome OS test infrastructure should be
filed against component Infra>Client>ChromeOS.

My recommendation for the new message:
    Test not supported for this board.

Thanks for all the corrections.

But what about the FAILED marking, with timeouts? Both of these paladin runs caused the CQ run to fail.

paladin/R56-8921.0.0-rc1, pool:bvt, board:wolf.
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 1002, 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:wolf satisfy arc, cros-version:wolf-tot-paladin/R56-8921.0.0-rc1, pool:bvt, board:wolf.



---

Are we scheduling ARC++ tests for wolf?

> But what about the FAILED marking, with timeouts?
> Both of these paladin runs caused the CQ run to fail.

Ah yes, that.  That's a failure.  In this case "did not run"
means the test couldn't get scheduled before the entire suite
timed out.  That's worth a new bug.

Preview for the new bug:  There are two common explanations
for this symptom:
 1) The target build was unstable in a way that slowed down
    testing (often because of Chrome crashes).
 2) The test scheduler was (temporarily) overloaded in some
    way.

> Are we scheduling ARC++ tests for wolf?

Yes, we schedule ARC++ tests for all boards, because they're
in the suite.  For boards (like wolf) that don't support ARC++,
the tests don't run, with the various symptoms already noted.

Same thing goes for various other tests (e.g. the cited video
tests).

> That's worth a new bug.

https://bugs.chromium.org/p/chromium/issues/detail?id=658478

I filed  issue 658469  for the Sound System Validation failure, but I don't have much extra info.

And about the $subject, yes, I think I've misinterpreted that before. I've previously at least understood that "TEST_NA" meant we didn't care about the "problem." I didn't realize in this case it was simply a way to skip inapplicable tests.

It also didn't help that there were other failures alongside, so I figured mention them all. If this didn't result in a red build, I wouldn't have worried :)

But if we are looking to change the message, it sounds like comment #2's suggestion would help people like me. As long as that's an accurate message, SGTM.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/c91299910fb82b8b9092a67342d1e2340f5816fe

commit c91299910fb82b8b9092a67342d1e2340f5816fe
Author: Richard Barnette <jrbarnette@chromium.org>
Date: Mon Oct 24 15:38:26 2016

[autotest] Fix message for a test on unsupported hardware.

When a test with a hardware dependency was determined to be
unsupported on a given board, the message said "no DUTs with
expected labels".  That message was nominally accurate, but the
target audience (Sheriffs) didn't know what it meant.  This changes
the message to say simply "test not supported on this board".

BUG= chromium:658473 
TEST=None

Change-Id: I1a9c02b20bb63b193f00b9d81d9db684f36c9887
Reviewed-on: https://chromium-review.googlesource.com/402061
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>

[modify] https://crrev.com/c91299910fb82b8b9092a67342d1e2340f5816fe/server/cros/dynamic_suite/suite.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/c91299910fb82b8b9092a67342d1e2340f5816fe

commit c91299910fb82b8b9092a67342d1e2340f5816fe
Author: Richard Barnette <jrbarnette@chromium.org>
Date: Mon Oct 24 15:38:26 2016

[autotest] Fix message for a test on unsupported hardware.

When a test with a hardware dependency was determined to be
unsupported on a given board, the message said "no DUTs with
expected labels".  That message was nominally accurate, but the
target audience (Sheriffs) didn't know what it meant.  This changes
the message to say simply "test not supported on this board".

BUG= chromium:658473 
TEST=None

Change-Id: I1a9c02b20bb63b193f00b9d81d9db684f36c9887
Reviewed-on: https://chromium-review.googlesource.com/402061
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>

[modify] https://crrev.com/c91299910fb82b8b9092a67342d1e2340f5816fe/server/cros/dynamic_suite/suite.py

We'll need a push to prod before the impact of this change
shows up in suite logs, but the code change is done.