unexpected signal during runtime execution

Bug #1617883 reported by Christopher Lee on 2016-08-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

As seen in issue:

Somewhere within "" an unexpected signal causes the test to panic and thus fail.

The start of the error message:
goroutine 18 [chan receive]:*suiteRunner).runTest(0xc08249d700, 0xc08210df10, 0x0)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/ +0x5e*suiteRunner).run(0xc08249d700, 0xc08248ef20)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/ +0x2a7, 0xc08248ef20, 0xc08241c280, 0xc0824dc000)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/ +0x4a, 0x0)
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/ +0xcf
 c:/users/admini~1/appdata/local/temp/tmpb3aod9/gogo/src/ +0x1e5

tags: added: ci unit-test windows
Curtis Hovey (sinzui) on 2016-08-29
tags: added: intermittent-failure regression
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
Curtis Hovey (sinzui) on 2016-12-12
summary: - Unittest fails on windows due to unexpected signal
+ unexpected signal
+ during runtime execution
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers