Closed
Bug 1502483
Opened 6 years ago
Closed 6 years ago
raptor-test should test for presence of Git and emit an error message if it's not found
Categories
(Testing :: Raptor, defect)
Tracking
(firefox65 fixed)
RESOLVED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox65 | --- | fixed |
People
(Reporter: mconley, Assigned: Bebe)
References
Details
Attachments
(1 file)
STR: 1) Install mozilla-build on 2018 Quantum Reference device 2) Run ./mach bootstrap to set up the infrastructure for a Firefox Desktop artifact build 3) Run ./mach build to build an artifact build 4) Run ./mach raptor-test --test raptor-tp6 to run the raptor-tp6 suite ER: Should run the raptor-tp6 suite AR: Here's what I got in the console: $ ./mach raptor-test --test raptor-tp6 Updating external benchmarks from https://github.com/mozilla/perf-automation [Error 2] The system cannot find the file specified
Reporter | ||
Comment 1•6 years ago
|
||
Gijs, apparently you got some Raptor tests running on the 2018 device... any insight here?
Flags: needinfo?(gijskruitbosch+bugs)
Comment 2•6 years ago
|
||
Hey Mike, probably a silly question but is git available in your path in the terminal you're running Raptor from?
Flags: needinfo?(mconley)
Reporter | ||
Comment 3•6 years ago
|
||
(In reply to Robert Wood [:rwood] from comment #2) > Hey Mike, probably a silly question but is git available in your path in the > terminal you're running Raptor from? Not a silly question at all - no it is not. I guess we don't distribute it with mozilla-build? Should I install it?
Flags: needinfo?(mconley) → needinfo?(rwood)
Comment 4•6 years ago
|
||
Ah, yes Raptor uses git to checkout a specific rev of the benchmark source (to a local .mozbuild/performance-tests repo), so yep you'll need to install it and have it in the path. Thanks for filing this bug - we need to have raptor test for Git and dump out a message indicating it cannot run if Git is not available.
Flags: needinfo?(rwood)
Reporter | ||
Comment 5•6 years ago
|
||
Gotcha, thanks!
Summary: Can't run raptor-tp6 on 2018 Quantum Reference device → raptor-test should test for presence of Git and emit an error message if it's not found
Reporter | ||
Updated•6 years ago
|
Flags: needinfo?(gijskruitbosch+bugs)
Comment 6•6 years ago
|
||
:bebe, would you have a chance to pick this one up? Should be a fairly quick one.
Flags: needinfo?(bebe)
Comment 8•6 years ago
|
||
(In reply to Mike Conley (:mconley) (:⚙️) from comment #1) > Gijs, apparently you got some Raptor tests running on the 2018 device... any > insight here? Yes, in fact I filed a dupe when I ran into it...
Comment 9•6 years ago
|
||
(In reply to :Gijs (he/him) from comment #8) > (In reply to Mike Conley (:mconley) (:⚙️) from comment #1) > > Gijs, apparently you got some Raptor tests running on the 2018 device... any > > insight here? > > Yes, in fact I filed a dupe when I ran into it... Ah, thanks :Gijs, I see yours was filed against Testing=>General and not Testing=>Raptor so I didn't see it (sorry).
Assignee | ||
Comment 10•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → bebe
Flags: needinfo?(bebe)
Comment 11•6 years ago
|
||
(In reply to Florin Strugariu [:Bebe] from comment #10) > Created attachment 9020747 [details] > Bug 1502483 raptor-test should test for presence of Git and emit an error > message if it's not found r? rwood Thanks :Bebe, please provide a try link with Raptor jobs on each platform, thanks!
Flags: needinfo?(bebe)
Comment 12•6 years ago
|
||
Pushing to try on :Bebe's behalf as he doesn't have perms yet
Flags: needinfo?(bebe)
Comment 13•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=72383dd197a9590650823066b27d0bca026a958a
Comment 14•6 years ago
|
||
Landed: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=b424df899a126d25503c3c818ad6931d785cf3bf
Comment 15•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b424df899a12
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in
before you can comment on or make changes to this bug.
Description
•