[Scons-users] Possible 2.5.1 regression on Windows? (was: Unreliable build problem)
wblevins001 at gmail.com
Wed May 3 21:09:03 EDT 2017
I think you mean:
On Wed, May 3, 2017 at 6:32 PM, Bill Deegan <bill at baddogconsulting.com> wrote:
> Likely it's the same issue as this:
> On Wed, May 3, 2017 at 3:14 PM, Arvid Rosén <arvid at softube.com> wrote:
>> I have problems with that too. Typically running 16 threads. I had to
>> rewrite all actions that generated source files (like header files with
>> version information), because they never worked reliably on Windows. Mac has
>> always been fine. I ended up using static header files with defines passed
>> on the command line instead. Somewhat ugly but it works.
>> I always thought this was rather related to some Windows related scanning
>> or anti-virus service, but I might give it a try with 2.3.6 and see if that
>> solves it.
>> Get Outlook for iOS
>> From: Bill Deegan <bill at baddogconsulting.com>
>> Sent: onsdag, maj 3, 2017 8:25 em
>> Subject: Re: [Scons-users] Possible 2.5.1 regression on Windows? (was:
>> Unreliable build problem)
>> To: SCons users mailing list <scons-users at scons.org>
>> That's useful to know 2.3.6 isn't showing this.
>> We've had a few reports of others running into it.
>> Are you using CacheDirs?
>> On Wed, May 3, 2017 at 10:42 AM, Hill, Steve (FP COM)
>> <Steve.Hill at cobham.com> wrote:
>>> Hi all,
>>> While looking at the unreliable build problem (which I will return to), I
>>> upgraded to 2.5.1 (from 2.3.6). Unfortunately, this seems to have introduced
>>> an issue which is preventing me from rolling the new version out the
>>> development community: I am seeing the file handle inheritance problem again
>>> that _scons_file and _scons_open were added to work around.
>>> We typically use between 8 and 12 build threads (depending on the
>>> physical machine that we are building on) and, when building with 2.5.1, we
>>> quite frequently see the build fail with some sort of access denied issue.
>>> The build system automatically runs handle.exe in this case and I can see
>>> that the other (unrelated) build threads have an open handle on the file at
>>> this time. Reverting to 2.3.6 results in the issue going away.
>>> I've confirmed that _scons_open and _scons_file are both in place for the
>>> built-in file() and open() and I've monkey patched os.open to assert that it
>>> is always called with the os.O_NOINHERIT flag. Does anyone know what other
>>> functions could be causing this that I can check?
>>> Scons-users mailing list
>>> Scons-users at scons.org
>> Scons-users mailing list
>> Scons-users at scons.org
> Scons-users mailing list
> Scons-users at scons.org
More information about the Scons-users