1973541 - tier-3 cleanup: promote fuzzing-python to tier-2, or make it try server only

Status: RESOLVED FIXED

(Core :: Fuzzing, task)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

I noticed fuzzing-python tasks run on esr-140, release, beta, central, autoland, and try. I am not sure anybody looks at these results. Also it seems that simple-fuzzing runs on autoland. All of these are tier-3.

Tier-3 is not designed for long term use, so we need to:

• promote to tier-2 (will be sheriffed, but no backout- should be green)
• remove from release/integration trees

In addition of this is on try only as tier-3, I would like to move it behind the --full flag, otherwise it should only be scheduled when desired files are changed, etc.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

:decoder, can you determine next steps here? I am targetting tier-3 cleanup by July 18th unless there are circumstances to otherwise delay this.

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

checking in as this has been a couple of weeks- I know summer holidays are a frequent thing.

Comment 3

[Jesse Schwartzentruber (:truber)]

This should be tier-2.

re: --full, this only affects try pushes? We can't really path filter the grizzly test, as it's a full-browser launch test to make sure nothing breaks our fuzzing automation harness. The js and fuzzing_interfaces tests could be path filtered.

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

tier-2 is great. there are 3 perma failures on central:
https://treeherder.mozilla.org/jobs?repo=mozilla-central&tier=3&searchStr=fuzzing&revision=1e02bb4c2af2efa34f8335befa373d2b39383b02

also changes would have to happen to remove this from running when we have artifact builds (this is primarily a try server thing).

--full only affects try pushes, if this is tier-2, I don't see a reason to make this behind --full, although it runs on so many try pushes now probably unintentionally that having it behind --full would reduce a bunch of unnecessary tasks.

Comment 5

[Jesse Schwartzentruber (:truber)]

(In reply to Joel Maher ( :jmaher ) (UTC -8) from comment #4)

also changes would have to happen to remove this from running when we have artifact builds (this is primarily a try server thing).

Is this something I add in the yml, or something that changes in taskgraph?

Comment 6

[Joel Maher ( :jmaher ) (UTC -8)]

we have a transform here:
https://searchfox.org/mozilla-central/source/taskcluster/gecko_taskgraph/target_tasks.py#303

and you can see an example of using supports-artifact-builds:
https://searchfox.org/mozilla-central/source/taskcluster/kinds/test/compiled.yml#33

that should just be added the the .yml config and it should work :)

in addition, I would recommend adding it to:
https://searchfox.org/mozilla-central/source/taskcluster/gecko_taskgraph/target_tasks.py#42

things there are hidden behind --all-tasks and --full. Autoland can catch regressions, I guess if you have found a lot of regressions with it overall (since it is tier-3, try has been ignored), then I wouldn't put the tasks in uncommon_try_tasks. If you find <4 regressions/year, then I would hide it.

Comment 7

[Jesse Schwartzentruber (:truber)]

Attachment: Bug 1973541 - Move fuzzing smoke tests to tier-2 r?#taskgraph-reviewers!

Comment 8

[Joel Maher ( :jmaher ) (UTC -8)]

what is the status here? we continue to run perma fail jobs on all the pushes. Can we turn these off until they are fixed?

Comment 9

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: Bug 1973541 - Disable win/macosx fuzzing due to perma failing, upgrade linux to use 24.04 docker. r=truber

Comment 10

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/5c5ade009e7c
https://hg.mozilla.org/integration/autoland/rev/1fc662320e32
Disable win/macosx fuzzing due to perma failing, upgrade linux to use 24.04 docker. r=truber

Comment 11

[pstanciu]

https://hg.mozilla.org/mozilla-central/rev/1fc662320e32