1869449 - ./mach try fuzzy --chemspill-prio fails to run gecko decision task: Exception: Invalid v1 `try_task_config.json`. expected bool for dictionary value @ data['chemspill-prio']

Status: RESOLVED FIXED

(Developer Infrastructure :: Try, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

./mach try fuzzy --chemspill-prio fails to run the decision task successfully with

Exception: Invalid v1 `try_task_config.json`.
expected bool for dictionary value @ data['chemspill-prio']

Some Android 7.0 web platform tests had been chosen in the fuzzy selector.

Comment 1

[Julien Cristau [:jcristau]]

$ ./mach file-info bugzilla-component tools/tryselect/task_config.py 
Developer Infrastructure :: Try
  tools/tryselect/task_config.py

Moving back :)

Comment 2

[Marco Castelluccio [:marco]]

Bug 1496768 is presumably the cause of this.

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1496768

:ahal, since you are the author of the regressor, bug 1496768, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Comment 4

[Andrew Halberstadt [:ahal]]

Sorry haven't had a chance to look.. will leave the needinfo and take a look in the new year.

Comment 5

[Andrew Halberstadt [:ahal]]

Attachment: Bug 1869449 - [tryselect] Fix 'chemspill-prio' try task configuration, r?#releng-reviewers!

Comment 6

[Andrew Halberstadt [:ahal]]

Note that try is down, but I verified the generated try_task_config.json locally and this should fix the issue.

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f2dbae7b3f71
[tryselect] Fix 'chemspill-prio' try task configuration, r=releng-reviewers,bhearsum

Comment 8

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/f2dbae7b3f71

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.