IGNOREME: just trying to figure out why autotester win32 is mangling pathnames#10567
IGNOREME: just trying to figure out why autotester win32 is mangling pathnames#10567marler8997 wants to merge 1 commit intodlang:masterfrom
Conversation
|
Thanks for your pull request and interest in making D better, @marler8997! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please see CONTRIBUTING.md for more information. If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment. Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub fetch digger
dub run digger -- build "master + dmd#10567" |
021679f to
025f635
Compare
025f635 to
47eb9f1
Compare
|
What the heck is going on! How is it passing now??? |
It's back to failure. I guess it depends on the build machine, passing for "win-farm-1", but failing for "power". The difference in the log is that HOST_DMD is initially not set in the passing version. |
|
Not sure how HOST_DMD would affect the git clone command. Might be a different version of cygwin causing the issue? |
I'm not sure either. Is the error message actually from
Possible. I've long given up on cygwin, in part due to this brittle conversion of path names, |
Yes:
Git:
Probably. Is |
It looks like this failure occurs on some autotester Win_32 hosts but not on others. Consistently fails on the "power" host but succeeds on the "win-farm-1" host.
The failure occurs when running git to clone the dlang tools repo. It fails with a message indicating that it combined the current directory with the absolute path passed as the destination path for the repo, i.e.
@braddr confirms these machines are using git directly (there's no in-between script that could be mangling the arguments). It seems the most likely culprit is cygwin. I've emailed @braddr to ask whether these machines are using different versions of cygwin.
Ping @MoonlightSentinel