876571 - Fix setting of MINIDUMP_SAVE_PATH

Status: RESOLVED DUPLICATE of bug 761586

(Release Engineering :: General, defect)

Description

[Phil Ringnalda (:philor)]

Bug 544062 set the env var MINIDUMP_SAVE_PATH to basedir/minidumps. On sane platforms, that sets it to something like "ENV: MINIDUMP_SAVE_PATH is now /builds/slave/talos-slave/test/build/../minidumps" and life is good. On Windows, that sets "ENV: MINIDUMP_SAVE_PATH is now c:\talos-slave\test\build/../minidumps" and when you send your friendly neighborhood relenger to fetch you the file from your log saying "INFO -  Saved dump as c:\talos-slave\test\build/../minidumps\4f2f3df0-f7e3-47d3-aa47-b3b246143963.dmp" he will tell you "philor: C:\talos-slave\test\minidumps is a 200K file" because the net result of that pile of mismatched slashes is a file named minidumps preventing the creation of a directory named minidumps even if we managed to have a path which would be a path rather than a... whatever that is.

I suspect that means that we've ruined minidumps as a possible directory, and along with getting the slashes right, we need to switch to putting them somewhere else.

Comment 1

[(not currently active) Ted Mielczarek]

I think you're probably just seeing bug 761586, which I only just fixed recently and hasn't made it from github to m-c yet. That change should make things work even in the face of the existing "file-as-directory" bustage.