Closed Bug 1785993 Opened 5 months ago Closed 5 months ago

Consider dropping the non-fission puppeteer job

Categories

(Remote Protocol :: CDP, task, P1)

task
Points:
1

Tracking

(firefox106 fixed)

RESOLVED FIXED
106 Branch
Tracking Status
firefox106 --- fixed

People

(Reporter: Sasha, Assigned: whimboo)

Details

(Whiteboard: [webdriver:m4])

Attachments

(1 file)

Since the support for non-fission builds should stop at some point, we can consider also dropping a puppeteer non-fission job. This job also cases usually more issues.

To add my 2c quickly, we do no longer request Fission to be disabled for CDP for quite some time (bug 1601245).

As such I wonder how important non Fission tests actually are for Puppeteer. We should discuss if they really give a value to us seeing the costs and not being able to differentiate our expectation test data between both test types.

When discussing this topic we agreed on in our team that those non-Fission tests aren't valuable for us.

Joel do you have any objections in getting this test configuration removed?

Flags: needinfo?(jmaher)

non fission tests only run for the purpose of supporting geckoview until that is fission by default- so if the value of puppeteer is null for geckoview this is a no brainer. If there is a high value in keeping this around to test code for geckoview we should keep it around for another 6 months or so.

Flags: needinfo?(jmaher)

Our Puppeteer support is desktop only. As such it's not valuable at all to continue running these tests in non-Fission mode. I'm going to remove this test configuration.

Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Priority: -- → P1
Points: --- → 1
Whiteboard: [webdriver:m4]
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5a91b0fa371a
[puppeteer] Drop puppeteer test job for non-Fission. r=jmaher
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 106 Branch
You need to log in before you can comment on or make changes to this bug.