av9ash/GitBugs huggingface dataset:
Bug: [Windows 11] Nightly window frame border has disappeared
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-11-19 22:09:18+00:00
Resolved: 2024-11-19 22:50:46+00:00

Steps to reproduce:

Was modifying my custom css in dev toolbox using Firefox Nightly 134.0a1 (2024-11-19) when suddenly firefox window frame lost its border.


Actual results:

Firefox window frame doesn't have border anymore, corners aren't rounded. Stable firefox version works fine.


Expected results:

Removed my custom chrome folder, didn't fix it.
Reset,cleared,deleted my profile, didn't fix it.
Reinstalled firefox nightly, didn't fit it.
Bug: Intermittent browser/components/urlbar/tests/browser/browser_searchModeSwitcher_basic.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-11-20 01:52:53+00:00
Resolved: 2025-01-20 07:26:54+00:00

**Filed by:** sstanca [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=483416775&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Cp8utxv2TZ6i9IMr37BKuw/runs/1/artifacts/public/logs/live_backing.log
**Reftest URL:** https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Cp8utxv2TZ6i9IMr37BKuw/runs/1/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2024-11-20T01:50:25.026Z] 01:50:25     INFO - TEST-PASS | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_basic.js | Expected placeholder l10n when search mode is inactive - true == true - 
[task 2024-11-20T01:50:25.027Z] 01:50:25     INFO - Leaving test bound test_search_mode_switcher_engine_no_icon
[task 2024-11-20T01:50:25.029Z] 01:50:25     INFO - Closing the view directly
[task 2024-11-20T01:50:25.030Z] 01:50:25     INFO - Waiting for the view to close
[task 2024-11-20T01:50:25.030Z] 01:50:25     INFO - Urlbar view closed
[task 2024-11-20T01:50:25.031Z] 01:50:25     INFO - Buffered messages finished
[task 2024-11-20T01:50:25.031Z] 01:50:25     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_basic.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2024-11-20T01:50:25.031Z] 01:50:25     INFO - GECKO(8031) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2024-11-20T01:50:25.032Z] 01:50:25     INFO - GECKO(8031) | MEMORY STAT | vsize 11850MB | residentFast 626MB | heapAllocated 335MB
[task 2024-11-20T01:50:25.032Z] 01:50:25     INFO - TEST-OK | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_basic.js | took 48133ms
```
Bug: Dedicated search button not in normal (Shift+)Tab order when focussing urlbar with Ctrl + L
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-11-20 10:44:46+00:00
Resolved: 2024-11-25 16:51:05+00:00

Not sure if it is a bug, but it is confusing me, therefore might also be confusing to others and worth fixing.

Copy of Bug 1931920 comment 2

> Note that the `Shift + Tab` isn't the inverse of `Tab` in the URL bar anymore after pressing `Ctrl+L`:
> 
> * going forward first lands you in a different position than just going back one item: `Shift + tab` (search icon) != `Tab` + `Shift + Tab` + `Shift + Tab` (shield icon)
> * going backwards first lands you in a different position than just going forward one item: `Tab` (right URL icons) != `Shift + Tab` + `Tab` + `Tab` (search with Google)

Expected result: the dedicated search button is somewhere in the normal `Tab`, `Shift + Tab` order and not something extra.

Additional: Previously you could get to the shield icon by pressing `Shift + Tab`. That is now not reachable with `Shift Tab` + `Shift + Tab` anymore (as one would expect if there was one more item before it). But it is necessary to press  `Tab` + `Shift + Tab` + `Shift + Tab` + `Shift + Tab`
Bug: Users cannot enroll in the “Sidebar button feature callout rollout” due to the way the Required Experiments are set
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-11-20 13:30:15+00:00
Resolved: 2024-11-25 14:51:03+00:00

[Notes]:
- Due to the way the “Required Experiments” section is configured for the rollout, the user has to be enrolled in all of the branches of the experiments mentioned there. 
- The enrollment condition should be fulfilled if the user was previously enrolled only in one of the branches.

[Affected versions]:
- Firefox Release Candidate 133.0 BUILD ID: 20241118181856

[Affected Platforms]:
- Windows 10.
- Ubuntu 22.04.
- macOS 14.7.

[Prerequisites]:
- User is or was enrolled in one of the required experiments for the [Sidebar button feature callout](https://experimenter.services.mozilla.com/nimbus/sidebar-button-feature-callout/summary) rollout; for example in the Treatment A branch of the [New users: sidebar + GenAI](https://experimenter.services.mozilla.com/nimbus/new-users-sidebar-genai/summary) experiment.
- Firefox 133 minimum version is used.

[Steps to reproduce]:
1. Open the browser with the profile from the prerequisites.
2. Try to enroll in the [Sidebar button feature callout](https://experimenter.services.mozilla.com/nimbus/sidebar-button-feature-callout/summary) rollout by adding this [user.js](https://drive.google.com/file/d/1NvdOBefMuu2gUNV4YpMYZNVANKq53oHk/view?usp=sharing) file to the profile folder.
3. Restart the browser and observe the behavior.

[Expected result]:
- The user is enrolled in the [Sidebar button feature callout](https://experimenter.services.mozilla.com/nimbus/sidebar-button-feature-callout/summary) rollout successfully.

[Actual result]:
- The user is not enrolled in the [Sidebar button feature callout](https://experimenter.services.mozilla.com/nimbus/sidebar-button-feature-callout/summary) rollout.
Bug: Unable to get past splash page on https://pittsburghpanthers.com
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-11-20 17:25:37+00:00
Resolved: 2024-11-20 22:43:27+00:00

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:132.0) Gecko/20100101 Firefox/132.0

Steps to reproduce:

Go to https://pittsburghpanthers.com.  Never get past splash page.


Actual results:

Never get past splash page.


Expected results:

Should have gotten to the site's homepage.
Bug: Focus order of elements within story cards on the New Tab Page does not follow the visual reading order
Status: NEW
Priority: P3
Created: 2024-11-20 17:29:03+00:00
Resolved: 2024-11-20 20:10:51+00:00

### Steps to reproduce
1. Navigate to the New Tab
2. Using keyboard alone, navigate from the first story card to the third and observe the visual focus movements

### Expected behavior
1. Visual reading order is followed and, for the LTR language like English, it is left-to-right top-to-bottom, in the card's case it would be the following:
    1. Card itself
    2. (card's header) `Save` to Pocket
    3. (card's header) `...` more options
    4. (card's footer) Thumbs Up
    5. (card's footer) Thumbs Down

### Actual behavior
1. The focus is jumping first to the bottom of the card and then coming back to the top, making it confusing to follow the focus order and to set expectations for the keyboard-only navigation. The focus order for a card is the following (referencing from the "Expected" behavior section): 1 > 4 > 5 > 2 > 3.
Bug: Tab group label should shift over when dragging first tab out of group
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-11-20 21:01:34+00:00
Resolved: 2025-02-24 14:59:05+00:00

**Steps to reproduce [can add screenshots or video recordings for reference]:**

1. Create a tab group with 2 or more tabs and have an ungroup tab to the left of the group
2. Drag the first tab in the group (next to label) to the left and out of the group

**Expected behavior [What should have happened?]:**
The tab group shifts over to the right 

**Actual behavior [What actually happened?]:**
Tab group doesn't move so the ungrouped tab on the left shifts over and overlaps with the tab group label (see video)
Bug: Hairline in dark mode uses light mode colours
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-11-20 21:13:24+00:00
Resolved: 2024-11-21 15:35:59+00:00

**Steps to reproduce [can add screenshots or video recordings for reference]:**

Set browser to dark mode and create a tab group

**Expected behavior [What should have happened?]:**

Hairline for tab group should be set to dark mode colour theme

**Actual behavior [What actually happened?]:**

Hairline is set to light mode colour theme (this is seen in all colours in dark mode)
Bug: Text and outline colour for collapsed tab groups in dark theme is wrong
Status: RESOLVED
Priority: P1
Resolution: INVALID
Created: 2024-11-20 21:20:07+00:00
Resolved: 2024-11-21 22:40:02+00:00

**Steps to reproduce [can add screenshots or video recordings for reference]:**

1. Set browser to dark theme
2. Create a tab group
3. Collapse the tab group

**Expected behavior [What should have happened?]:**

The outline and text colours for each colour group is different and should match the spec here
https://www.figma.com/design/f6J2lH6XDxLxyzOLr2E8oE/Tab-Grouping-Spec?node-id=9461-173201&t=FU470NNXZjosE46w-1

**Actual behavior [What actually happened?]:**

The outline and text appears to be all white (#FFFFFF)
Bug: Text and outline colour for tab groups in dark theme is wrong
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-11-20 21:20:38+00:00
Resolved: 2024-11-21 15:43:09+00:00

**Steps to reproduce [can add screenshots or video recordings for reference]:**

1. Set browser to dark theme
2. Create a tab group
3. Collapse the tab group

**Expected behavior [What should have happened?]:**

The outline and text colours for each colour group is different and should match the spec here
https://www.figma.com/design/f6J2lH6XDxLxyzOLr2E8oE/Tab-Grouping-Spec?node-id=9461-173201&t=FU470NNXZjosE46w-1

**Actual behavior [What actually happened?]:**

The outline and text appears to be all white (#FFFFFF)
Bug: [Section Expt] Newtab if you dismiss all cards in a section with a spoc you get an error and a crash
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2024-11-20 21:28:49+00:00
Resolved: 2024-11-22 15:12:28+00:00

"TypeError: can't access property Symbol.iterator, data is undefined"

I think this may have been fixed in another bug, but I wanted to file it just in case, so it's not forgot and we can double check.
Bug: Tab Share menu doesn't support multiple tab selection
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-11-21 00:19:42+00:00
Resolved: 2024-11-26 15:45:18+00:00

When multiple tabs are selected, the right-click tab context menu offers the Share option, but only the active tab is shared. See screenshot. This is reproducible on macOS and Windows. This might be the intended behavior, but given the multi-selection support it, would be nice to support sharing multiple tabs.
Bug: Open previous windows and tabs not opening all windows
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2024-11-21 01:36:36+00:00
Resolved: 2025-01-02 22:54:29+00:00

Steps to reproduce:

1. Ensure the "Open previous windows and tabs" option is enabled
1. Open 10 windows, each with a couple of tabs open
2. Close all windows at once
3. Open Firefox and some of the previous windows will reopen


Actual results:

Only some of the windows will reopen, not all of them.

Tested in Arch Linux, against Firefox 132 and 131 (both installed via Flatpak).


Expected results:

All of the windows should reopen.
Bug: sync is missing
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-11-21 02:21:22+00:00
Resolved: 2025-02-13 18:48:05+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:132.0) Gecko/20100101 Firefox/132.0

Steps to reproduce:

I installed Firefox and Sync option is missing from the Settings. I don't see Sync option int he Settings, and I don't see "Sign in to Sync" when I click on the hamburger on the upper right corner.


Actual results:

I installed Firefox and Sync option is missing from the Settings. I don't see Sync option int he Settings, and I don't see "Sign in to Sync" when I click on the hamburger on the upper right corner.
Bug: Frequent browser/components/urlbar/tests/browser/browser_searchModeSwitcher_keyNavigation.js | single tracking bug
Status: RESOLVED
Priority: P5
Resolution: FIXED
Created: 2024-11-21 04:44:55+00:00
Resolved: 2025-01-27 07:01:58+00:00

**Filed by:** smolnar [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=483581993&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/GWb4JeMURTyDLqcIeo1z_Q/runs/0/artifacts/public/logs/live_backing.log

---
```
INFO - GECKO(4164) | [Child 4182: Main Thread]: I/DocShellAndDOMWindowLeak --DOMWINDOW == 2 (106a71000) [pid = 4182] [serial = 288] [outer = 0] [url = about:newtab]
[task 2024-11-21T03:59:07.449Z] 03:59:07     INFO - GECKO(4164) | [Parent 4164, sqldb:places.sqlite #2] WARNING: Suboptimal indexes for the SQL statement 0x16f4fc200 (http://mzl.la/1FuID0j).: file /builds/worker/checkouts/gecko/storage/mozStoragePrivateHelpers.cpp:114
[task 2024-11-21T03:59:07.450Z] 03:59:07     INFO - GECKO(4164) | [Parent 4164, sqldb:places.sqlite #2] WARNING: Suboptimal indexes for the SQL statement 0x16f4fc200 (http://mzl.la/1FuID0j).: file /builds/worker/checkouts/gecko/storage/mozStoragePrivateHelpers.cpp:114
[task 2024-11-21T03:59:07.450Z] 03:59:07     INFO - GECKO(4164) | [Parent 4164, sqldb:places.sqlite #2] WARNING: Suboptimal indexes for the SQL statement 0x16f4fc200 (http://mzl.la/1FuID0j).: file /builds/worker/checkouts/gecko/storage/mozStoragePrivateHelpers.cpp:114
[task 2024-11-21T03:59:07.451Z] 03:59:07     INFO - GECKO(4164) | [Parent 4164, sqldb:places.sqlite #2] WARNING: Suboptimal indexes for the SQL statement 0x16f4fc200 (http://mzl.la/1FuID0j).: file /builds/worker/checkouts/gecko/storage/mozStoragePrivateHelpers.cpp:114
[task 2024-11-21T03:59:46.707Z] 03:59:46     INFO - TEST-INFO | started process screencapture
[task 2024-11-21T03:59:47.002Z] 03:59:47     INFO - TEST-INFO | screencapture: exit 0
[task 2024-11-21T03:59:47.002Z] 03:59:47     INFO - Buffered messages logged at 03:58:16
[task 2024-11-21T03:59:47.006Z] 03:59:47     INFO - Entering setup bound setup
[task 2024-11-21T03:59:47.007Z] 03:59:47     INFO - Leaving setup bound setup
[task 2024-11-21T03:59:47.008Z] 03:59:47     INFO - Entering test bound test_keyboard_nav
[task 2024-11-21T03:59:47.009Z] 03:59:47     INFO - Open the urlbar and open the switcher via keyboard (KEY_Enter)
[task 2024-11-21T03:59:47.010Z] 03:59:47     INFO - Buffered messages finished
[task 2024-11-21T03:59:47.010Z] 03:59:47     INFO - TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser/browser_searchModeSwitcher_keyNavigation.js | Test timed out - 
[task 2024-11-21T03:59:47.012Z] 03:59:47     INFO - GECKO(4164) | Completed ShutdownLeaks collections in process 4164
[task 2024-11-21T03:59:47.012Z] 03:59:47     INFO - TEST-START | Shutdown
```
Bug: [win10] App Menu options are not visible when hovered with High Contrast#1 Windows theme and Firefox System theme
Status: VERIFIED
Priority: P2
Resolution: FIXED
Created: 2024-11-21 07:04:20+00:00
Resolved: 2025-02-25 15:05:06+00:00

* filed on request per [bug 1930840#c7](https://bugzilla.mozilla.org/show_bug.cgi?id=1930840#c7)

**Found in**
* 134.0a1 (2024-11-12)

**Affected versions**
* 134.0a1 (2024-11-120)
* 133.0
* 132.0.2

**Tested platforms**
* Affected platforms: Windows 10
* Unaffected platforms: macOS 12, Ubuntu 24

**Precognitions**
* Firefox System theme is set
* High Contrast #1 is set in Windows settings


**Steps to reproduce**
1. Open the App Menu and hover over options.

****Expected result****
* The options are displayed as expected.

**Actual result**
* The options are not visible.



**Regression range**
* The first bug causing buttons to be not visible on hover was bug 1917588. This issue was initially fixed by bug 1916589 but was then reverted by bug 1919611. I’ll set bug 1917588 as the initial regressor; please feel free to update it if this seems incorrect.


**Additional notes**
* Attached a screen recording.
* The same issue happens with `High contrast #2`. With `High Contrast White` there is no hover effect on toolbar buttons or app menu options. With `High contrast Black` there is no hover effect on App menu options and only an outline effect on toolbar buttons.
Bug: Firefox Android app sync error
Status: RESOLVED
Priority: --
Resolution: WORKSFORME
Created: 2024-11-21 08:09:43+00:00
Resolved: 2024-11-21 08:14:36+00:00

User Agent: Mozilla/5.0 (Android 10; Mobile; rv:132.0) Gecko/132.0 Firefox/132.0
Firefox for Android

Steps to reproduce:

Toggling on "open tabs" in Firefox Android sync settings.


Actual results:

It's ineffective as it toggles off automatically after exiting the setting tab.


Expected results:

It should be remain on since I want to sync my open tabs from my android to my PC.
Bug: Creating a Tab Group by moving a Tab past a 2nd Tab and then grouping them together will only group one tab
Status: VERIFIED
Priority: P1
Resolution: FIXED
Created: 2024-11-21 12:10:59+00:00
Resolved: 2024-12-06 08:38:36+00:00

**Found in**
* 134.0a1 (2024-11-21) 

**Affected versions**
* 134.0a1 (2024-11-21)

**Preconditions**
Set browser.tabs.groups.enabled	true

**Affected platforms**
* all

**Steps to reproduce**
1. Have a Few Tabs opened.
2. Grab a Left Tab, move it past a 2nd tab to the right and then hover over the 2nd tab in order to create a Tab group.

**Expected result**
* Both tabs should be inside the Tab Group.

**Actual result**
* Only the Moving tab is displayed in the Created Tab Group.

**Regression range**
Not a Regression.
Bug: problems with providers like onet
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2024-11-21 12:31:21+00:00
Resolved: 2024-12-10 14:13:52+00:00

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Steps to reproduce:

https://www.onet.pl/?utm_campaign=cb


Actual results:

no data


Expected results:

should display correct data
Bug: [Experiment] The "Addons CSAT 2024" MicroSurvey is triggered even if there are no add-ons installed
Status: VERIFIED
Priority: --
Resolution: FIXED
Created: 2024-11-21 12:40:17+00:00
Resolved: 2024-11-22 14:17:06+00:00

**[Affected versions]:**
- Firefox Release 132.0.0 - Build ID: 20241110231641
- Firefox RC 133.0 - Build ID: 20241118181856

**[Affected Platforms]:**
- Windows 10
- macOS 15.10.1

**[Prerequisites]:**
- Have the [user.js](https://drive.google.com/file/d/18ik_WgAgk5-jxaDKp2UOFoKnE17fDPmv/view?usp=sharing) file downloaded to your PC.
- Have a new Firefox profile with no add-ons installed.
- Have Firefox set as the default browser or have the "Always check if Firefox is your default browser" option from the "about:preferences" page unchecked.
- Verify that the profile is not enrolled in the "nalexander PDF Annotations - Highlight - not default handler" experiment in order to be able to trigger our MicroSurvey in test.
  
**[Steps to reproduce]:**
1. Open the browser using the profile from the prerequisites.
2. Navigate to the profile folder and paste the [user.js](https://drive.google.com/file/d/18ik_WgAgk5-jxaDKp2UOFoKnE17fDPmv/view?usp=sharing) file from the prerequisites.
3. Restart the browser two or three times and observe the behavior.

**[Expected result]:**
- The "Addons CSAT 2024" MicroSurvey is NOT triggered.
    
**[Actual result]:**
- The "Addons CSAT 2024" MicroSurvey is triggered after two or three browse restarts even if no add-ons are installed.

**[Additional Notes]:**
- I have not managed to reproduce this issue by opening new tabs instead of restarting the browser.
- I have evaluated the `(addonsInfo.addons | values [!.hidden] | length > 0)` expression in the "Targeting" section of the "about:asrouter" page and the result was `false`.
- I have not reproduced the issue on my Ubuntu 24.04 virtual machine.
- Attached a screen recording of the issue.
Bug: 3.01% speedometer3 NewsSite-Nuxt/NavigateToWorld/Sync (Windows) regression on Fri November 15 2024
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2024-11-21 13:27:59+00:00
Resolved: 2024-12-04 12:22:16+00:00

Perfherder has detected a browsertime performance regression from push [6c508a387477e3b72db913a9e1761e9a433d06a2](https://hg.mozilla.org/integration/autoland/pushloghtml?changeset=6c508a387477e3b72db913a9e1761e9a433d06a2). As author of one of the patches included in that push, we need your help to address this regression.

### Regressions:

| **Ratio** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)** |  **Performance Profiles** | 
|--|--|--|--|--|--| 
| [3%](https://treeherder.mozilla.org/perfherder/graphs?timerange=1209600&series=autoland,82162,1,13)  | [speedometer3](https://firefox-source-docs.mozilla.org/testing/perfdocs/raptor.html#speedometer3-d) NewsSite-Nuxt/NavigateToWorld/Sync | windows11-64-nightlyasrelease-qr | fission webrender | [14.10](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/W-hGiAa3Te25GgFNwfPdHg/runs/0/artifacts/public/test_info/browsertime-results.tgz) -> [14.53](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/LJaf_D3xT5mX2HBuISMP9w/runs/0/artifacts/public/test_info/browsertime-results.tgz) | [Before](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FW-hGiAa3Te25GgFNwfPdHg%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_speedometer3.zip)/[After](https://profiler.firefox.com/from-url/https%3A%2F%2Ffirefox-ci-tc.services.mozilla.com%2Fapi%2Fqueue%2Fv1%2Ftask%2FLJaf_D3xT5mX2HBuISMP9w%2Fruns%2F0%2Fartifacts%2Fpublic%2Ftest_info%2Fprofile_speedometer3.zip) |


Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=42721), including links to graphs and comparisons for each of the affected tests. Please follow our [guide to handling regression bugs](https://wiki.mozilla.org/TestEngineering/Performance/Handling_regression_bugs) and **let us know your plans within 3 business days, or the patch(es) may be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.

You can run all of these tests on try with `./mach try perf --alert 42721`

The following [documentation link](https://firefox-source-docs.mozilla.org/testing/perfdocs/mach-try-perf.html#running-alert-tests) provides more information about this command.

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).

If you have any questions, please do not hesitate to reach out to fbilt@mozilla.com.