amd64 mismatch in i386 tests

Bug #1372961 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Andrew Wilkins

Bug Description

Build: #1863 Revision: gitbranch:master:github.com/juju/juju 76946149 Version: 1.21-alpha2

Failed tests
run-unit-tests-precise-i386 build #740 http://juju-ci.vapour.ws:8080/job/run-unit-tests-precise-i386/740/console

We see arch mismatch errors like this:
    c.Check(*hc.Arch, gc.Equals, "amd64")
... obtained string = "i386"
... expected string = "amd64"

The errors are consistent for all retried of the test for 1863. The errors also appear in all the tries for revision build 1861. The last successful run of the i386 unit tests was for
Revision build: 1860 gitbranch:master:github.com/juju/juju daee1985
The first failure is
Revision build: 1861 gitbranch:master:github.com/juju/juju 24e04838

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: none → 1.21-alpha2
Revision history for this message
Curtis Hovey (sinzui) wrote :

As the succeeding and failing commits are back-to-back in the log, this issue was likely caused by
    Merge pull request #804 from axw/tools-metadata-no-provider-storage

Andrew Wilkins (axwalk)
Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Andrew Wilkins (axwalk)
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.

Other bug subscribers

Remote bug watches

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