The last green run I can find for this platform/task is here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=sp3%2Cwindows%2C11%2C24h2%2Cshippable&revision=381df99d5fa440f09960e020224cc87918380c4c https://treeherder.mozilla.org/logviewer?job_id=556654267&repo=mozilla-central&task=UzjlA2KQS_uapPoyncbEJw.0&lineNumber=2158 (That log does have some `ConnectionResetError:` issues, but it's apparently still judged to be "good"/green.) And the first bad run is here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=sp3%2Cwindows%2C11%2C24h2%2Cshippable&revision=0b76dd137a61420640d9276c563698c3b3eff72a https://treeherder.mozilla.org/logviewer?job_id=556859461&repo=mozilla-central&task=I3D8T65LT2yBNG8G_4Pssw.0&lineNumber=927 Treating this as a regression, those^ yield this regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=381df99d5fa440f09960e020224cc87918380c4c&tochange=0b76dd137a61420640d9276c563698c3b3eff72a ...but I'm not seeing anything obvious jumping out in there. Comparing the good vs. bad log, the main difference I'm seeing is `~1` vs. `~2` in the file path that we're checking for Chrome. The "good" log has: ``` Google Chrome found in expected location C:\Progra~1\Google\Chrome\Application\chrome.exe ``` whereas the "bad" log has: ``` Cannot find Google Chrome at C:\Progra~2\Google\Chrome\Application\chrome.exe ``` Maybe we there was some change to our Windows environment around then, such that we're checking the wrong Program Files directory now? (I think some systems have both "Program Files" and "Program Files (x86)", and presumably one of those is `~1` and the other is `~2`.) jmaher or ahal, maybe one of you know whether there could have been a config change like that around that point in history? (or have other ideas about what to do or who to poke)
Bug 2028315 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The last green run I can find for this platform/task is here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=sp3%2Cwindows%2C11%2C24h2%2Cshippable&revision=381df99d5fa440f09960e020224cc87918380c4c https://treeherder.mozilla.org/logviewer?job_id=556654267&repo=mozilla-central&task=UzjlA2KQS_uapPoyncbEJw.0&lineNumber=2158 (That log does have some `ConnectionResetError:` issues, but it's apparently still judged to be "good"/green.) And the first bad run is here: https://treeherder.mozilla.org/jobs?repo=mozilla-central&searchStr=sp3%2Cwindows%2C11%2C24h2%2Cshippable&revision=0b76dd137a61420640d9276c563698c3b3eff72a https://treeherder.mozilla.org/logviewer?job_id=556859461&repo=mozilla-central&task=I3D8T65LT2yBNG8G_4Pssw.0&lineNumber=927 Treating this as a regression between those^ pushes, that would mean we'd have this regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=381df99d5fa440f09960e020224cc87918380c4c&tochange=0b76dd137a61420640d9276c563698c3b3eff72a ...but I'm not seeing anything obvious jumping out in there. Comparing the last-good vs. first-bad log, the main difference I'm seeing is `~1` vs. `~2` in the file path that we're checking for Chrome. The "good" log has: ``` Google Chrome found in expected location C:\Progra~1\Google\Chrome\Application\chrome.exe ``` whereas the "bad" log has: ``` Cannot find Google Chrome at C:\Progra~2\Google\Chrome\Application\chrome.exe ``` Maybe we there was some change to our Windows environment around then, such that we're checking the wrong Program Files directory now? (I think some systems have both "Program Files" and "Program Files (x86)", and presumably one of those is `~1` and the other is `~2`.) jmaher or ahal, maybe one of you know whether there could have been a config change like that around that point in history? (or have other ideas about what to do or who to poke)