ppc64el unit test timeout

Bug #1434555 reported by Curtis Hovey
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Ian Booth
1.23
Fix Released
High
Ian Booth

Bug Description

Both master and 1.23 fail because a timeout in agent/machine_test and/or agent/upgrade_test.

The bug blocks the release of 1.23.0 because Ubuntu will not accept a regression on the tests. Engineers can fix the test or skip it if the deem the issue is a broken compiler.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Attached is the most recent log.

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.23-beta2 → 1.24-alpha1
Revision history for this message
Ian Booth (wallyworld) wrote :

Looks like there's still issues with the machine agent completing upgrades when run on ppc64.

There's already a skip for this test on I386. Maybe we also need to add a skip for PPC64

TestUpgradeStepsStateServer

github_com_juju_juju_cmd_jujud_agent.Stop.pN49_github_com_juju_juju_cmd_jujud_agent.MachineAgent
 /home/ubuntu/juju-core_1.23-beta2/src/github.com/juju/juju/cmd/jujud/agent/machine.go:320
agent.$nested187
 /home/ubuntu/juju-core_1.23-beta2/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:835
gopkg_in_check_v1.stopNow.pN19_gopkg_in_check_v1.C
 /home/ubuntu/juju-core_1.23-beta2/src/gopkg.in/check.v1/check.go:97
gopkg_in_check_v1.Assert.pN19_gopkg_in_check_v1.C
 /home/ubuntu/juju-core_1.23-beta2/src/gopkg.in/check.v1/helpers.go:174
agent.waitForUpgradeToFinish
 /home/ubuntu/juju-core_1.23-beta2/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:855
github_com_juju_juju_cmd_jujud_agent.assertUpgradeSteps.pN49_github_com_juju_juju_cmd_jujud_agent.UpgradeSuite
 /home/ubuntu/juju-core_1.23-beta2/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:778
github_com_juju_juju_cmd_jujud_agent.TestUpgradeStepsStateServer.pN49_github_com_juju_juju_cmd_jujud_agent.UpgradeSuite
 /home/ubuntu/juju-core_1.23-beta2/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:451
gopkg_in_check_v1.Call.N28_gopkg_in_check_v1.methodType
 /home/ubuntu/juju-core_1.23-beta2/src/gopkg.in/check.v1/check.go:49
check.$nested2
 /home/ubuntu/juju-core_1.23-beta2/src/gopkg.in/check.v1/check.go:761
check.$nested0
 /home/ubuntu/juju-core_1.23-beta2/src/gopkg.in/check.v1/check.go:655
created by gopkg_in_check_v1.forkCall.pN29_gopkg_in_check_v1.suiteRunner
 /home/ubuntu/juju-core_1.23-beta2/src/gopkg.in/check.v1/check.go:652

Ian Booth (wallyworld)
Changed in juju-core:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
John George (jog)
tags: added: unit-tests
Revision history for this message
Martin Packman (gz) wrote :

So, one skip has landed for this already on trunk, but we're still getting failures such as:

<http://reports.vapour.ws/releases/2536/job/run-unit-tests-trusty-ppc64el/attempt/2782>

goroutine 14818 [chan receive]:
launchpad.net_tomb.Wait.pN23_launchpad.net_tomb.Tomb
 /home/ubuntu/juju-core_1.24-alpha1/src/launchpad.net/tomb/tomb.go:110
github.com_juju_juju_cmd_jujud_agent.Stop.pN49_github.com_juju_juju_cmd_jujud_agent.MachineAgent
 /home/ubuntu/juju-core_1.24-alpha1/src/github.com/juju/juju/cmd/jujud/agent/machine.go:322
agent.$nested193
 /home/ubuntu/juju-core_1.24-alpha1/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:837
gopkg.in_check.v1.stopNow.pN19_gopkg.in_check.v1.C
 /home/ubuntu/juju-core_1.24-alpha1/src/gopkg.in/check.v1/check.go:97
gopkg.in_check.v1.Assert.pN19_gopkg.in_check.v1.C
 /home/ubuntu/juju-core_1.24-alpha1/src/gopkg.in/check.v1/helpers.go:174
agent.waitForUpgradeToFinish
 /home/ubuntu/juju-core_1.24-alpha1/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:857
github.com_juju_juju_cmd_jujud_agent.assertUpgradeSteps.pN49_github.com_juju_juju_cmd_jujud_agent.UpgradeSuite
 /home/ubuntu/juju-core_1.24-alpha1/src/github.com/juju/juju/cmd/jujud/agent/upgrade_test.go:780
github.com_juju_juju_cmd_jujud_agent.TestUpgradeStepsHostMachine.pN49_github.com_juju_juju_cmd_jujud_agent.UpgradeSuite
...

Only skipped TestUpgradeStepsStateServer but apparently TestUpgradeStepsHostMachine is also unhappy now?

Martin Packman (gz)
Changed in juju-core:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.