"mach raptor-test" fails with "error: The following untracked working tree files would be overwritten by checkout"
Categories
(Testing :: Raptor, defect, P3)
Tracking
(Not tracked)
People
(Reporter: whimboo, Unassigned)
Details
I just tried to run the following command when I got this error:
mach raptor-test --test=raptor-youtube-playback --post-startup-delay=0 --gecko-profile
Updating external benchmarks from https://github.com/mozilla/perf-automation
error: The following untracked working tree files would be overwritten by checkout:
CODE_OF_CONDUCT.md
pagesets/mitmproxy/raptor-tp6/raptor-Apple.html
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-analytics.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-globalfooter.css
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-globalfooter.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-globalnav.css
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-globalnav.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-localnav.css
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/ac-localnav.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/auto-init.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/fonts.css
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/head.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/localeswitcher.css
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/localeswitcher.js
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/main.css
pagesets/mitmproxy/raptor-tp6/raptor-Apple_files/main.js
I didn't change anything in that folder, so I assume some update happened here recently which is causing the update command to fail, and then to bail out from the Raptor test.
Reporter | ||
Comment 1•5 years ago
|
||
Running $ git status
in that local clone shows:
HEAD detached at 2720cdc
Changes not staged for commit:
Which is:
commit 2720cdc790828952964524bb44ce8b4c14670e90 (HEAD, tag: unity-webgl-v3, tag: unity-webgl-v2)
Merge: dd3f5a4 fdc6767
Author: Joel Maher <joel.maher@gmail.com>
Date: Mon Sep 17 15:22:20 2018 -0400
So it's not something which was changed lately.
I was able to get the tests running again after performing a $ git checkout master -f
.
Comment 2•5 years ago
|
||
I'm not seeing this error when I tried the same command (on the latest mozilla-central) but maybe because I had just pulled the latest and did a clobber and new build.
Reporter | ||
Updated•5 years ago
|
Updated•2 years ago
|
Description
•