runlevel tool used in FAFT not installed in cros_sdk

[Marc Jones]

I'm hitting an error in FAFT. The firmware_InvalidUSB test is trying to set a runlevel in my cros_sdk and the tools isn't installed. Does anyone know what package that might be in or how it should be installed?

A side question. Why would the test be trying to set a runlevel?

Regards,

Marc

[Yusuf Mohsinally]

Hi Marc,

Could you zip up the test logs directory and send it over?

Thanks,

Yusuf

[Mike Loptien]

I have seen the same issues.  I attached a log file for you from Clapper.

Thanks,

Mike

[Dave Parker]

Looking in 

https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/common_lib/hosts/base_classes.py

It looks like the test framework is checking that the host machine about to drive the test process isn't about to shut down.

The 'runlevel' check is in an exception block so this shouldn't be fatal.

-Dave

[Yusuf Mohsinally]

This seems harmless. It's probably this:

https://cs.corp.google.com/#chromeos_public/src/third_party/autotest/files/client/common_lib/hosts/base_classes.py&q=p:chromeos_%5Binternal%7Cpublic%5D%20runlevel&l=147

It's trying to detect the current runlevel, and it doesn't matter if it fails.

I have created a bug to track this issue since it seems to be autotest related:

https://code.google.com/p/chromium/issues/detail?id=359180

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.