New issue
Advanced search Search tips

Issue 812129 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Autotest, issue with dbus module in server test

Project Member Reported by wirebrand@chromium.org, Feb 14 2018

Issue description

When I run a server test in the test lab the test fails since the dbus module is missing. The test works fine when I run it from my workstation.

The problem is that the Python 'dbus' package isn't available inside the SSP container.

Link on Stainless to test that fails: https://stainless.corp.google.com/search?exclude_retried=true&first_date=2018-02-07&master_builder_name=&builder_name_number=&shard=&exclude_acts=true&builder_name=&master_builder_name_number=&owner=&retry=&exclude_cts=true&exclude_non_production=true&hostname=&board=%5Eguado%24&test=%5Eenterprise_CFM_AtrusUpdaterStress%24&exclude_not_run=false&build=%5ER66%5C-10390%5C.0%5C.0%24&status=FAIL&status=ERROR&status=ABORT&reason=&waterfall=&suite=&last_date=2018-02-13&exclude_non_release=true&exclude_au=true&model=&view=list

Link to log file with trace info: https://storage.cloud.google.com/chromeos-autotest-results/175828297-chromeos-test/chromeos1-row5-rack1-host1/debug/autoserv.INFO?_ga=2.224035480.-2025005535.1518170479

What steps will reproduce the problem?
Run the autotest on Chrome OS test rack.

What is the expected result?
Test should start runnig without issue.

What happens instead?
Test fails when trying to import python dbus module.

 
Cc: kerl@google.com dtosic@google.com
Discussion on chromeos-infra-dicuss for context: https://groups.google.com/a/google.com/forum/#!topic/chromeos-infra-discuss/5Sw1H4MqYig
Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
Status: Available (was: Untriaged)
Labels: -Pri-2 Hotlist-Deputy Pri-1
Some more jetstream tests are also blocked by this now: g/chromeos-infra-discuss/undc7AunNmE

> deputy.
BTW, we've managed to break our Wifi tests with this. We already had plenty of client-side tests that use the client/cros/networking/shill_proxy module (which uses the dbus module), and we accidentally broke all our Wifi *server* tests by starting to use this module.

We'll fix that up ourselves, but the inconsistency in lack of dbus module on the container is a real problem.

It also looks like the Bluetooth team just managed to break themselves too:  bug 906872 .
Cc: ayatane@chromium.org
Labels: -Hotlist-Deputy
Owner: akes...@chromium.org
Status: Assigned (was: Available)
Isn't really a deputy issue (outage or routine task)

Needs an owner.
Cc: shijinabraham@google.com

Sign in to add a comment