panics in apiserver/root.go
Menno Smits
menno.smits at canonical.com
Mon Jun 23 05:36:11 UTC 2014
Talk about quick turn-around! I'm glad you've (probably) found it.
On 23 June 2014 17:32, John Meinel <john at arbash-meinel.com> wrote:
> I think I figured it out, though I'm not 100% sure. I believe we're
> accessing a go map without a mutex, so you can get concurrent access. I'll
> see if I can create a test case that triggers the race detector and fix it.
>
> John
> =:->
>
>
> On Mon, Jun 23, 2014 at 9:24 AM, John Meinel <john at arbash-meinel.com>
> wrote:
>
>> I have not seen them before, but it certainly is likely to be related,
>> I'll dig into it today.
>>
>> John
>> =:->
>>
>>
>> On Mon, Jun 23, 2014 at 8:21 AM, Menno Smits <menno.smits at canonical.com>
>> wrote:
>>
>>> There's been a few panics during test runs in the API server code
>>> recently that look like this:
>>>
>>> http://juju-ci.vapour.ws:8080/job/github-merge-juju/221/consoleFull
>>> http://juju-ci.vapour.ws:8080/job/github-merge-juju/223/consoleFull
>>>
>>> I've also seen it happen during test runs on my personal machine today
>>> (once out of 10's of runs of the same test suite). Given where the panic is
>>> occurring could it be related to the recent API versioning changes?
>>>
>>> - Menno
>>>
>>> --
>>> Juju-dev mailing list
>>> Juju-dev at lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140623/fb0bccb7/attachment-0001.html>
More information about the Juju-dev
mailing list