MainSuite.TestFirstRun2xFrom1x fails on windows
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Nate Finch |
Bug Description
As seen in
http://
main_test.go:227:
c.Check(
Welcome to Juju %s. If you meant to use Juju 1.25.0 you can continue using it
with the command juju-1 e.g. 'juju-1 switch'.
See https:/
`[1:], jujuversion.
... obtained string = ""
... expected string = "" +
... " Welcome to Juju 2.0-beta7. If you meant to use Juju 1.25.0 you can continue using it\n" +
... " with the command juju-1 e.g. 'juju-1 switch'.\n" +
... " See https:/
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 2.0-beta7 |
tags: | added: blocker ci regression test-failure unit-tests windows |
Changed in juju-core: | |
status: | Fix Committed → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → In Progress |
assignee: | Reed O'Brien (reedobrien) → Nate Finch (natefinch) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta7 → none |
milestone: | none → 2.0-beta7 |
AFAICT this warning was created to alert people that unknowingly got an update to juju2 on xenial. See https:/ /bugs.launchpad .net/juju- core/+bug/ 1564622
Because we install on windows by building from source or using and installer, it seems that we can skip this warning on Windows.
Alternatively, we'll need to use the appropriate juju command based on the host os as I assume the command on Windows is probably juju.exe. Unsure if it would even be different between juju 1.x and juju 2.x.
Going with a skip on windows. For now.