Create mach try preset
Categories
(Remote Protocol :: Agent, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: ato, Unassigned)
Details
Attachments
(1 file)
1.05 KB,
patch
|
Details | Diff | Splinter Review |
Regardless what is the conclusion to https://phabricator.services.mozilla.com/D32028/,
we will want a try preset that can run all the relevant remote
debugger tests for us.
At the moment, I think we want it to include:
- remote/test/browser/ (mochitest browser-chrome)
- remote/test/unit/ (xpcshell)
Reporter | ||
Comment 1•5 years ago
|
||
Can you explain what we need to do here? Can the preset be scoped
to running files under specific directories?
Comment 2•5 years ago
|
||
Here's an example of an in-tree preset (note if the mochitest-remote
patch lands, this becomes obsolete). Also I needed to duplicate paths
and test_paths
because of bug 1556445 (the workaround is simple enough I wouldn't bother making it block this).
With this, you'd run mach try --preset remote
. Though, this preset is pretty basic.. you almost don't even need it. Without a preset, you could just run:
# select tasks interactively
$ ./mach try fuzzy remote
# select tasks from cli
$ ./mach try fuzzy remote -q "linux xpcshell"
Reporter | ||
Comment 3•5 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #2)
Though, this preset is pretty basic.. you almost don't even need
it. Without a preset, you could just
I see your point. All the tests we care about for the moment are
under remote/, and fuzzy is able to figure our the tests from giving
the path already.
We can always re-open this bug if the situation changes and there
are tests outside of remote/ that become relevant to us.
Reporter | ||
Updated•5 years ago
|
Description
•