Currently, all test paths scheduled for the chunk are passed to mozharness using environment variables.
They are structured like so:
```
{
'web-platform-tests': [
'test',
'test-2'
]
}
```
This is problematic for two reasons:
1. it is unwieldy as the test paths grow.
2. environment variables have a finite character limit and this is rather quickly reached for windows platforms.
Addressing this issue with some sort of an artifact generated by the decision task that can be downloaded then read by the chunks would result in significantly better chunk balance as it would unlock ability to specific individual tests to be run.
Bug 1641592 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently, all test paths scheduled for the chunk are passed to mozharness using environment variables.
They are structured like so:
```
"MOZHARNESS_TEST_PATHS": {
'web-platform-tests': [
'test',
'test-2'
]
}
```
This is problematic for two reasons:
1. it is unwieldy as the test paths grow.
2. environment variables have a finite character limit and this is rather quickly reached for windows platforms.
Addressing this issue with some sort of an artifact generated by the decision task that can be downloaded then read by the chunks would result in significantly better chunk balance as it would unlock ability to specific individual tests to be run.