Bug 1633866 Comment 34 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Andrew Halberstadt [:ahal] from comment #33)
> A couple issues to resolve:
> 1. Why is the mochitest-plain symbol "unknown" ?

This one is easy. The default symbols for mochitest-plain are just numbers and nothing else. When we split chunks, the numbers are appended to the existing symbol here:
https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/transforms/tests.py#1495

But since we only have one chunk we never enter that if statement and we likely assign the symbol an empty string, which treeherder then defaults to "unknown".
(In reply to Andrew Halberstadt [:ahal] from comment #33)
> 1. Why is the mochitest-plain symbol "unknown" ?

This one is easy. The default symbols for mochitest-plain are just numbers and nothing else. When we split chunks, the numbers are appended to the existing symbol here:
https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/transforms/tests.py#1495

But since we only have one chunk we never enter that if statement and we likely assign the symbol an empty string, which treeherder then defaults to "unknown".
(In reply to Andrew Halberstadt [:ahal] from comment #33)
> 1. Why is the mochitest-plain symbol "unknown" ?

This one is easy. The default symbols for mochitest-plain are just numbers and nothing else. When we split chunks, the numbers are appended to the existing symbol here:
https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/transforms/tests.py#1495

But since we only have one chunk we never enter that if statement and we likely assign the symbol an null value, which treeherder then defaults to "unknown".

Back to Bug 1633866 Comment 34