Author koobs
Recipients Claudiu.Popa, koobs, vajrasky, vstinner
Date 2016-08-25.10:02:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1472119329.99.0.264880816429.issue27838@psf.upfronthosting.co.za>
In-reply-to
Content
This appears to have spontaneously resolved itself after build #957 after many failures. For reference, other builders on the same host were failing as well:

AMD64 FreeBSD CURRENT Debug 3.5 (#567, #568)
AMD64 FreeBSD CURRENT Non-Debug 3.5 (#8, #9)

And possibly others (Didn't listed any that hadn't failed in the last 5 builds)

According to my (non-expert) reading of the code, the test skips (or is supposed to skip) unless group count of uid is > 1.

The group membership of the buildbot user this worker runs as is only 'buildbot' and on that basis wouldn't a skip expected?

Open questions are:

1) Why/how did it suddenly *start* failing. (I cant see any relevant commits at or around the time)
2) Why/how did it suddenly stop failing (I made no worker/buildbot changes

Nosy vajrasky (original unit test creator) and Claudiu (who reviewed), who might be able to shine a light on what might be going on
History
Date User Action Args
2016-08-25 10:02:10koobssetrecipients: + koobs, vstinner, Claudiu.Popa, vajrasky
2016-08-25 10:02:09koobssetmessageid: <1472119329.99.0.264880816429.issue27838@psf.upfronthosting.co.za>
2016-08-25 10:02:09koobslinkissue27838 messages
2016-08-25 10:02:09koobscreate