win juju client still broken with unknown
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/
Moved C:\Users\
Installed Juju
Command '('\\Progra~
<class 'subprocess.
panic: invalid series "unknown"
goroutine 1 [running]:
runtime.
C:/Users/
github.
C:/Users/
github.
C:/Users/
github.
C:/Users/
github.
C:/Users/
github.
C:/Users/
main.init()
C:/Users/
goroutine 3 [syscall]:
os/signal.loop()
C:/Users/
created by os/signal.init��1
C:/Users/
+ '[' 3 -ne 0 ']'
+ exit 1
Build step 'Execute shell' marked build as failure
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
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 Administrator\ ci\juju- core_1. 20.1.tar. gz Administrator\ ci\juju- setup-1. 20.1.exe Administrator\ ci\gogo 2\Juju\ unins000. exe Administrator\ ci\tmp\ juju-core_ 1.21-alpha1 to C:\Users\ Administrator\ ci\gogo
Removed C:\Users\
Removed C:\Users\
Removed C:\Users\
Uninstalled Juju with \Progra~
Extracted the Juju source.
Moved C:\Users\
Command '('\\go\ \bin\\go. exe', 'build')' returned non-zero exit status 2 CalledProcessEr ror'>
<class 'subprocess.
+ '[' 3 -ne 0 ']'
+ exit 1