This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients eric.araujo, jcea, r.david.murray, skrah, vstinner
Date 2011-05-01.08:39:06
SpamBayes Score 4.9244903e-07
Marked as misclassified No
Message-id <20110501083748.GA17697@sleipnir.bytereef.org>
In-reply-to <1304207348.56.0.739452461877.issue11873@psf.upfronthosting.co.za>
Content
R. David Murray <report@bugs.python.org> wrote:
> The failing test is launching a subprocess to compile python code, waiting
> for the subprocess to exit, and then checking to see if the file was
> created.  So the timing issue would appear to be that the file created by
> the subprocess doesn't appear to exist to the main program even after the
> subprocess has exited.  Stefan, Jesus, do either of you know of anything
> about the file systems used on your buildbots that might give rise to this
> problem?  Is there some sort of file system sync call we need to make to
> make sure different processes have the same view of the file system?

The FreeBSD bot has a UFS filesystem with no soft updates:

$ mount
/dev/ad0s1a on / (ufs, local)

If the main process waits for the subprocess to finish, I can't think of
a reason to do any kind of synchronization.
History
Date User Action Args
2011-05-01 08:39:07skrahsetrecipients: + skrah, jcea, vstinner, eric.araujo, r.david.murray
2011-05-01 08:39:07skrahlinkissue11873 messages
2011-05-01 08:39:06skrahcreate