DuplicateHandle failed on Cygwin

[joduinn]

...instead it just displayed in the DOS console running buildbot.

For example, the following was not logged anywhere, but was displayed on the dos-window of one of our windows slave machine:

$ c:\buildtools\python24\scripts\buildbot start c:\win32-slave1

13 [main] sh 1128! _pinfo::dup_proc_pipe: DuplicateHandle? failed, pid 1128, hProcess 0x6C8, Win32 error 5

[joduinn]

...but there was no way to know about it by looking in logs, waterfall pages, etc. We had to manually connect to the machine to see this error.

[dustin]

Any idea how to get ahold of that information in the buildslave?

[marcusl]

Is it the buildbot process itself that emits this? If so, we need the buildbot to read it's own filedesc-level stdout/stderr. Hm.

It can also be solved by proper error detection within buildbot. I.e. errors like these should never be silently emitted and forgotten, but caught and reported via logs and everything.

I've never seen it. Is there a way to reproduce this?

[thatch]

It looks like it's coming from cygwin's sh. For explanation of the error, see  http://www.cygwin.com/ml/cygwin/2008-05/msg00424.html

[marcusl]

IIUC, it seems as if it is cygwin related (a fork fail due to rebase not having been run recently enough?

[dustin]

So if I understand, this is a failure in sh, probably due to a failure of whatever's being executed. I'm not sure a Python script is going to be able to handle something so deeply buried in layers of emulation, but it would be nice to at least know what's going on.

What ShellCommand? are you running? Does changing usePTY help at all?

[dustin]

Seems like this is a cygwin problem, rather than bbot.. please reopen if I'm wrong.