Timeout in github.com/juju/juju/apiserver/service on windows

[Curtis Hovey]

As seen at
    http://reports.vapour.ws/releases/issue/572b992b749a563c48c49f19

The windows unit tests timeout in github.com/juju/juju/apiserver/service. This issue was fixed for about 7 days in bug 1580184, but is now broken again.

[William Reade (fwereade)]

For possible future reference, this bit looks significant:

goroutine 1035 [semacquire, 19 minutes]:
sync.runtime_Semacquire(0xc08231700c)
 C:/Go/src/runtime/sema.go:47 +0x2d
sync.(*WaitGroup).Wait(0xc082317000)
 C:/Go/src/sync/waitgroup.go:127 +0xbb
github.com/juju/juju/apiserver/service_test.(*recordingStorage).Put(0xc082546b40, 0xc0821b4500, 0x46, 0x38457d0, 0xc082024b78, 0x565, 0x0, 0x0)
 c:/users/admini~1/appdata/local/temp/tmpnzxqio/gogo/src/github.com/juju/juju/apiserver/service/service_test.go:2735 +0x5f
github.com/juju/juju/apiserver/service.StoreCharmArchive(0xc082376340, 0xc0825b8d20, 0x384da50, 0xc082393e50, 0x38457d0, 0xc082024b78, 0x565, 0xc0827ea180, 0x40, 0x0, ...)
 c:/users/admini~1/appdata/local/temp/tmpnzxqio/gogo/src/github.com/juju/juju/apiserver/service/charmstore.go:206 +0x1a9

[William Reade (fwereade)]

Yes, I think it is significant: we have 9/10 goroutines waiting for putBarrier; implying that the 1/10 failed before it got far enough to call Storage.Put, and so I'm very much unconvinced it's fundamentally windows-specific.

As discussed with cherylj, will be skipping on windows for now, but I doubt that's the end of the story.

[Cheryl Jennings (cherylj)]

William - can you open a new bug to fix the test, rather than just skipping on windows?

We can use this bug to track skipping this test on windows.

[Michael Foord (mfoord)]

Opened bug 1596960 to track the [potential] underlying issue.

[Michael Foord (mfoord)]

http://reviews.vapour.ws/r/5176/