github.com/juju/juju/worker/uniter/runner/jujuc_test unexpected signal during runtime execution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As seen in issue: http://
Somewhere within "github.
The start of the error message:
goroutine 18 [chan receive]:
gopkg.in/
c:/users/
gopkg.in/
c:/users/
gopkg.in/
c:/users/
gopkg.in/
c:/users/
gopkg.in/
c:/users/
github.
tags: | added: ci unit-test windows |
tags: | added: intermittent-failure regression |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
- Unittest fails on windows due to unexpected signal + github.com/juju/juju/worker/uniter/runner/jujuc_test unexpected signal + during runtime execution |
description: | updated |
It's a pity that the link with the full stack is no longer available.
I cannot reproduce this locally and I have stress-tested both worker/ uniter/ runner/ jujuc tests as well as worker/ metrics/ spool ones.
I do recall that there were some changes in metrics area fairly recently, at least, since this report was filed. Maybe that work fixed this issue as well?..
Either way, there is not enough information here to proceed. I'll mark as Fix Released. If we'd see a re-occurrence, we'd need full new logs and a new report.