Closed Bug 1637679 Opened 5 years ago Closed 5 years ago

Migrate arewefastyet.com from mozilla-central to autoland

Categories

(Testing :: Raptor, task, P2)

Version 3
task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sparky, Assigned: alexandru.capalneanu)

References

Details

We recently had an idea for moving the dashboards from using mozilla-central data to autoland data so that we can disable tests that we run on mozilla-central which only exist for dashboards atm and aren't sheriffed. I think we should also be clear that this would only be done for tests that currently run on both branches and not the tests that are only running on mozilla-central (like our cron tests). We get the same data from both and perf regressions generally make it into mozilla-central unless they are backed out for some other reasons.

There are two questions we need to look into here:

  1. Do the savings of disabling perftests on mozilla-central outweigh the cost to disabling them and switching the dashboards?
  2. Given that autoland has more granularity, would the dashboards be able to handle the added data and still provide the same performance?

:jmaher, what do you think about question (1), do you think you would be able to provide some potential savings estimates? We think this could be a potential CI costs savings but maybe it won't be as impactful as we suspect.

Answering (2) will depend on the answers to (1).

Flags: needinfo?(jmaher)

I think this is a great idea and we would automatically get alerts matched up.

As for #2, let me ask :ekyle.

Flags: needinfo?(jmaher) → needinfo?(klahnakoski)

Given that autoland has more granularity, would the dashboards be able to handle the added data and still provide the same performance?

The health graphics dashboard may be fine. It can be tested easy by making a PR with all "mozilla-central" replaced with "autoland", and reviewing the preview. HERE IS THE PREVIEW

We can see there are a number of tests not run on autoland.

Flags: needinfo?(klahnakoski)

:ekyle, that's expected since we don't run everything on both branches. This would only be for tests that currently run on both autoland and m-c.

For these tests, do you think we could start moving the dashboards to use autoland?

Flags: needinfo?(klahnakoski)

:sparky yes, go ahead and turn off mozilla-central tests. Please add your changes as an issue to https://github.com/mozilla-frontend-infra/firefox-health-dashboard/issues

Flags: needinfo?(klahnakoski)

Fantastic, thanks!

Removing the discussion tag from this bug.

Summary: [discussion] Migrate dashboards from mozilla-central to autoland → Migrate dashboards from mozilla-central to autoland
Depends on: 1639314
Priority: P3 → P2
Blocks: 1639314
No longer depends on: 1639314

what is the timeline for working on this bug?

:jmaher, we're going to work on this in our june sprint. Here's the JIRA ticket: https://jira.mozilla.com/browse/FXP-1018

Severity: -- → S3
Depends on: 1669439
Depends on: 1669440
Assignee: nobody → alexandru.capalneanu
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED

Only arewefastyet.com has been migrated to use autoland where possible. We still need to consider the value of performing the same migration for health.graphics.

Summary: Migrate dashboards from mozilla-central to autoland → Migrate arewefastyet.com from mozilla-central to autoland
You need to log in before you can comment on or make changes to this bug.