Bugzilla

I think I'd like to go a step further here and just *always* remove chunk numbers from `mach try auto` / other selectors. Especially given that we are soon going to be landing "manifest scheduling" on autoland, which means the chunks that developers see in treeherder *will not* be the same as the chunks that they get locally. This would be a step in the direction of abstracting the concept of "chunks" away from developers.

So in this new chunkless world, selecting:
```
./mach try fuzzy -q "test-linux64/opt-mochitest-plain-e10s"
```

would run all Linux 64 opt mochitest-plain tests with e10s, no matter how many chunks there are. If a subset of mochitests are desired, then developers can specify a test path:
```
./mach try fuzzy -q "test-linux64/opt-mochitest-plain-e10s" dom/indexedDB
```
This way the default mental model is that I'm selecting "paths" not "chunks".

Note, we could potentially implement a flag to continue to expose chunks if that's desired for some advanced use cases. Though, if such use cases exist, I think we should try to see if there are alternative solutions (e.g using presets) to solve them first.

I think I'd like to go a step further here and just *always* remove chunk numbers from `mach try fuzzy` / other selectors. Especially given that we are soon going to be landing "manifest scheduling" on autoland, which means the chunks that developers see in treeherder *will not* be the same as the chunks that they get locally. This would be a step in the direction of abstracting the concept of "chunks" away from developers.

So in this new chunkless world, selecting:
```
./mach try fuzzy -q "test-linux64/opt-mochitest-plain-e10s"
```

would run all Linux 64 opt mochitest-plain tests with e10s, no matter how many chunks there are. If a subset of mochitests are desired, then developers can specify a test path:
```
./mach try fuzzy -q "test-linux64/opt-mochitest-plain-e10s" dom/indexedDB
```
This way the default mental model is that I'm selecting "paths" not "chunks".

Note, we could potentially implement a flag to continue to expose chunks if that's desired for some advanced use cases. Though, if such use cases exist, I think we should try to see if there are alternative solutions (e.g using presets) to solve them first.