Closed Bug 1563224 Opened 5 years ago Closed 5 years ago

Raptor jobs for Fission current fail with "no such option: --setpref"

Categories

(Testing :: Raptor, defect, P2)

69 Branch
defect

Tracking

(Fission Milestone:M5)

RESOLVED DUPLICATE of bug 1585593
Fission Milestone M5

People

(Reporter: whimboo, Unassigned)

References

Details

As it can be seen on this try push the Raptor job currently fails for Fission:

[taskcluster 2019-07-03T13:46:04.365Z] Executing command 0: /usr/local/bin/python2 -u 'mozharness/scripts/raptor_script.py' --cfg 'mozharness/configs/raptor/mac_config.py' --test=raptor-youtube-playback '--setpref="fission.autostart=true"' --download-symbols ondemand --test=raptor-youtube-playback '--setpref="fission.autostart=true"'
Usage: raptor_script.py [options]
raptor_script.py: error: no such option: --setpref

Reason is that the raptor mozharness script doesn't have a --setpref option.

Priority: -- → P2
Flags: needinfo?(ahal)

Looks like a regression from bug 1555792. Though since fission isn't running anywhere that causes backouts, it isn't Byron's fault.

Flags: needinfo?(ahal)
Regressed by: 1555792

Bug 1555792 has not landed yet, and those try pushes do not have my patches in them. I tripped over this bug while working on bug 1555792, but I worked around it by not setting my prefs on raptor jobs.

No longer regressed by: 1555792

Also see bug 1555792 where this has been done for a couple other test jobs.

See Also: → 1555792

So... I was completely flying by the seat of my pants on that bug, for what it is worth. Please don't assume I really knew what I was doing...

Actually the mozharness addition will only be half of the job. The other half will be to bake in the preference setting support in the Raptor harness itself. Something like...

https://searchfox.org/mozilla-central/rev/4436573fa3d5c4311822090e188504c10c916c6f/testing/raptor/raptor/cmdline.py
https://searchfox.org/mozilla-central/rev/4436573fa3d5c4311822090e188504c10c916c6f/testing/raptor/raptor/raptor.py#938

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Fission Milestone: --- → ?

M5 so engineers can run Raptor-Fis sooner.

Blocks: 1594631
Fission Milestone: ? → M5

When i created the patch for raptor to enable fission: https://bugzilla.mozilla.org/show_bug.cgi?id=1585593
I added the --setpref to command line to be able to use --setpref=fission.autostart=true
https://hg.mozilla.org/mozilla-central/rev/8aa294ef7cc2#l2.18
I think we can close this ticket as fixed.

See Also: → 1585593

Looks like it's more a duplicate of bug 1585593.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.