github.com/juju/juju/worker/uniter/runner/jujuc_test unexpected signal during runtime execution

Bug #1617883 reported by Christopher Lee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Unassigned

Bug Description

As seen in issue: http://reports.vapour.ws/releases/issue/584f0008749a56699848310e

Somewhere within "github.com/juju/juju/worker/metrics/spool" an unexpected signal causes the test to panic and thus fail.

The start of the error message:
goroutine 18 [chan receive]:
gopkg.in/check%2ev1.(*suiteRunner).runTest(0xc08249d700, 0xc08210df10, 0x0)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/gopkg.in/check.v1/check.go:810 +0x5e
gopkg.in/check%2ev1.(*suiteRunner).run(0xc08249d700, 0xc08248ef20)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/gopkg.in/check.v1/check.go:615 +0x2a7
gopkg.in/check%2ev1.Run(0xcf26a0, 0xc08248ef20, 0xc08241c280, 0xc0824dc000)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/gopkg.in/check.v1/run.go:92 +0x4a
gopkg.in/check%2ev1.RunAll(0xc08241c280, 0x0)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/gopkg.in/check.v1/run.go:84 +0xcf
gopkg.in/check%2ev1.TestingT(0xc0824dc240)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/gopkg.in/check.v1/run.go:72 +0x1e5
github.com/juju/juju/worker/uniter/runner/jujuc_test.TestPackage(0xc0824dc240)

tags: added: ci unit-test windows
Curtis Hovey (sinzui)
tags: added: intermittent-failure regression
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
Curtis Hovey (sinzui)
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
Revision history for this message
Anastasia (anastasia-macmood) wrote :

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.

Changed in juju:
status: Triaged → 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.