win juju client still broken with unknown

Bug #1335328 reported by Curtis Hovey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Dave Cheney

Bug Description

The change increment juju to 1.19.5 (will be 1.21-alpha1) merged 3 commits after" Merge pull request #186 from davecheney/fix-os-version", but this panic was seen in master. This looks like the same error shown in bug 1334493.

Moved C:\Users\Administrator\ci\gogo\src\github.com\juju\juju\scripts\win-installer\output\juju-setup-1.19.5.exe to C:\Users\Administrator\ci

Installed Juju
Command '('\\Progra~2\\Juju\\juju.exe', 'version')' returned non-zero exit status 2
<class 'subprocess.CalledProcessError'>
panic: invalid series "unknown"

goroutine 1 [running]:
runtime.panic(0xa97be0, 0x12700570)
 C:/Users/ADMINI~1/AppData/Local/Temp/2/makerelease106211947/go/src/pkg/runtime/panic.c:266 +0xa6
github.com/juju/juju/juju/paths.MustSucceed(0xb693c8, 0x0, 0x26c740, 0x12700570, 0x26c740, ...)
 C:/Users/Administrator/ci/gogo/src/github.com/juju/juju/juju/paths/paths.go:76 +0x48
github.com/juju/juju/agent.init()
 C:/Users/Administrator/ci/gogo/src/github.com/juju/juju/agent/agent.go:35 +0x123
github.com/juju/juju/environs.init()
 C:/Users/Administrator/ci/gogo/src/github.com/juju/juju/environs/utils.go:22 +0x93
github.com/juju/juju/environs/tools.init()
 C:/Users/Administrator/ci/gogo/src/github.com/juju/juju/environs/tools/validation.go:74 +0x52
github.com/juju/juju/environs/sync.init()
 C:/Users/Administrator/ci/gogo/src/github.com/juju/juju/environs/sync/sync.go:354 +0x4d
main.init()
 C:/Users/Administrator/ci/gogo/src/github.com/juju/juju/cmd/juju/user_info.go:124 +0x52

goroutine 3 [syscall]:
os/signal.loop()
 C:/Users/ADMINI~1/AppData/Local/Temp/2/makerelease106211947/go/src/pkg/os/signal/signal_unix.go:21 +0x20
created by os/signal.init��1
 C:/Users/ADMINI~1/AppData/Local/Temp/2/makerelease106211947/go/src/pkg/os/signal/signal_unix.go:27 +0x33
+ '[' 3 -ne 0 ']'
+ exit 1
Build step 'Execute shell' marked build as failure

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

The bug has mutated again. Juju cannot be compiled on windows. We can see "undefined: Handle". We can also see the steps the script performed to clean the workspace before calling go build.

# github.com/juju/utils/symlink
..\..\..\utils\symlink\zsymlink_windows_386.go:28: undefined: Handle

Building and installing Juju 1.21-alpha1 from juju-core_1.21-alpha1.tar.gz
Removed C:\Users\Administrator\ci\juju-core_1.20.1.tar.gz
Removed C:\Users\Administrator\ci\juju-setup-1.20.1.exe
Removed C:\Users\Administrator\ci\gogo
Uninstalled Juju with \Progra~2\Juju\unins000.exe
Extracted the Juju source.
Moved C:\Users\Administrator\ci\tmp\juju-core_1.21-alpha1 to C:\Users\Administrator\ci\gogo

Command '('\\go\\bin\\go.exe', 'build')' returned non-zero exit status 2
<class 'subprocess.CalledProcessError'>
+ '[' 3 -ne 0 ']'
+ exit 1

Revision history for this message
Dave Cheney (dave-cheney) wrote :

I have a windows environment, i'll try to get juju checked out and running tomorrow.

Changed in juju-core:
assignee: nobody → Dave Cheney (dave-cheney)
Revision history for this message
Dave Cheney (dave-cheney) wrote :
Changed in juju-core:
status: Triaged → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
importance: Critical → High
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → 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.