These tests are run across different archs using the same script (the same user etc.). Nothing has changed in how it's run but we're only seeing this failure on Zesty.
I should be able to get the PolicyKit output from the journal in case that is of use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode Status in juju: Triaged Status in juju 2.1 series: Won't Fix Status in dbus package in Ubuntu: New Bug description: As seen at http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e A unit test is exclusively failing on our new zesty machine. the previous issues is not related to the zesty falures machine-0: has workers [agent api-address-updater api-caller api-config-watcher disk-manager log-forwarder log-sender logging-config-updater machine-action-runner machiner migration-fortress migration-inactive-flag migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater state-config-watcher storage-provisioner termination-signal-handler unconverted-api-workers upgrade-check-flag upgrade-check-gate upgrade-steps-flag upgrade-steps-gate upgrader] machine-0: waiting for [unit-agent-deployer] machine-0: unexpected [] machine-0: report: {} machine_test.go:1272: WaitMatch(c, matcher.Check, coretesting.LongWait, s.BackingState.StartSync) engine_test.go:234: c.Fatalf("timed out waiting for workers") ... Error: timed out waiting for workers To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
