Open Bug 1323008 Opened 8 years ago Updated 2 years ago

when the gecko decision tasks runs- log the SETA data as an artifact


(Testing :: General, defect, P3)



(Not tracked)


(Reporter: jmaher, Unassigned)



in trying to understand which jobs are run and for what reason, it would be nice to inspect the logs of the decision task and when doing that we see a job is optimized away, inspect the SETA data.

One option is to document the data coming from SETA, another option is to change the messages in the gecko decision task.
Blocks: 1311814
Blocks: 1325404
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.