av9ash/GitBugs huggingface dataset:
Bug: Bookmarks toolbar is unexpectedly shown when click star icon
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-05-29 20:31:32+00:00
Resolved: 2021-07-06 13:18:54+00:00

Steps to reproduce:
1. Start Nightly90.0a1 with new profile
2. Open an unbookmarked web page, so that Bookmarks toolbar will automatically hide
3. Click star icon


Actual Results:
Bookmarks toolbar appears.
The bookmarks toolbar does not automatically hide unless you switch tabs.

Expected Results:
Bookmarks toolbar should not appear.
Bug: Two "Recently closed tabs" entries open when middle-clicked and focus switches to the additional tab
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-05-29 21:54:17+00:00
Resolved: 2021-08-03 19:51:57+00:00

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

Steps to reproduce:

Close three tabs, go to History->Recently closed tabs->middle-click any tab that's not on the bottom.


Actual results:

Tab below will also open while tab focus jumps to the additionally opened tab instead of the one that was clicked.


Expected results:

The tab that was middle-clicked opens and gets focus.
Bug: Tab context menu fluent strings not added if it's opened on all tabs menu before it's opened on tab browser
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-05-30 11:48:19+00:00
Resolved: 2022-02-01 12:09:55+00:00

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

Steps to reproduce:

- Start firefox
- Don't right click the tab browser
- Open the all tabs menu
- Right click a tab in the all tabs menu


Actual results:

- Most context menus have no labels due to no fluent attributes


Expected results:

The [function that sets up the fluent attributes](https://searchfox.org/mozilla-central/source/browser/base/content/tabbrowser.js#5970) is bound to a contextmenu event listener targeting the tab browser but not the all tabs menu. Event listeners should be added for the all tabs panel too.

If the FTL inserter function in tabbrowser.js was accessible from the all tabs panel's scope then it would be a lot easier. The function could be changed like this
```
this.tabContextFTLInserter = () => {
    MozXULElement.insertFTLIfNeeded("browser/tabContextMenu.ftl");
    // Un-lazify the l10n-ids now that the FTL file has been inserted.
    document
        .getElementById("tabContextMenu")
        .querySelectorAll("[data-lazy-l10n-id]")
        .forEach((el) => {
            el.setAttribute("data-l10n-id", el.getAttribute("data-lazy-l10n-id"));
            el.removeAttribute("data-lazy-l10n-id");
        });
    this.tabContainer.removeEventListener("contextmenu", this.tabContextFTLInserter, true);
    this.tabContainer.removeEventListener("mouseover", this.tabContextFTLInserter);
    this.tabContainer.removeEventListener("focus", this.tabContextFTLInserter, true);
};
this.tabContainer.addEventListener("contextmenu", this.tabContextFTLInserter, true);
this.tabContainer.addEventListener("mouseover", this.tabContextFTLInserter);
this.tabContainer.addEventListener("focus", this.tabContextFTLInserter, true);
```

and then the tabs panel could set up the same thing and remove the event listeners if it gets initialized first. in [browser-allTabsMenu.js](https://searchfox.org/mozilla-central/source/browser/base/content/browser-allTabsMenu.js)...
```
gTabsPanel = {
    // ...
    init() {
        // ...
        let lazies = document
            .getElementById("tabContextMenu")
            .querySelectorAll("[data-lazy-l10n-id]");
        if (lazies) {
            MozXULElement.insertFTLIfNeeded("browser/tabContextMenu.ftl");
            lazies.forEach((el) => {
                el.setAttribute("data-l10n-id", el.getAttribute("data-lazy-l10n-id"));
                el.removeAttribute("data-lazy-l10n-id");
            });
            gBrowser.tabContainer.removeEventListener(
                "contextmenu",
                gBrowser.tabContextFTLInserter,
                true
            );
            gBrowser.tabContainer.removeEventListener("mouseover", gBrowser.tabContextFTLInserter);
            gBrowser.tabContainer.removeEventListener(
                "focus",
                gBrowser.tabContextFTLInserter,
                true
            );
        }
    },
};
```
Bug: Selective history delete is exceedingly slow
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-05-30 13:17:18+00:00
Resolved: 2021-05-31 09:29:57+00:00

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

Steps to reproduce:

Open history, search for particular site (eg, google.com), select all results, press delete. 


Actual results:

I literally drank a cup of coffee while waiting for the delete to finish.   Firefox was otherwise useless during this time as history operations seem to run on the main thread(?)


Expected results:

On a new, high end Thinkpad it took approximately 1 sec to return that there were 10,777 results for google.com.   The delete started at 08:39:00.  It finished at 09:05:34

It should not take 26+ minutes to delete those items from the history, even on low end equipment let alone recent top end lap/desktops.
Bug: Can't drag tabs out of browser window when used the "Select all tabs" context menu item
Status: NEW
Priority: P5
Created: 2021-05-30 14:11:03+00:00
Resolved: 2023-03-06 19:24:11+00:00

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

Steps to reproduce:

See video.


Actual results:

The dragged tab will not open in a new browser window.


Expected results:

Should have opened in a new browser window or at least disable the drag function for tabs when all tabs are selected.
Bug: Intermittent browser/components/places/tests/browser/browser_bookmarksProperties.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-05-30 15:34:46+00:00
Resolved: 2025-02-03 12:06:24+00:00

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

---
```
[task 2021-05-30T13:59:15.514Z] 13:59:15     INFO - TEST-PASS | browser/components/places/tests/browser/browser_bookmarksProperties.js | Dialog window should not be closed by pressing ESC in folder name textbox - true == true - 
[task 2021-05-30T13:59:15.514Z] 13:59:15     INFO - Buffered messages logged at 13:57:15
[task 2021-05-30T13:59:15.514Z] 13:59:15     INFO - Longer timeout required, waiting longer...  Remaining timeouts: 1
[task 2021-05-30T13:59:15.514Z] 13:59:15     INFO - Buffered messages finished
[task 2021-05-30T13:59:15.514Z] 13:59:15     INFO - TEST-UNEXPECTED-FAIL | browser/components/places/tests/browser/browser_bookmarksProperties.js | Test timed out - 
[task 2021-05-30T13:59:15.514Z] 13:59:15     INFO - GECKO(1582) | MEMORY STAT | vsize 130551654MB | residentFast 2393MB
```
Bug: Intermittent browser/components/places/tests/browser/interactions/browser_interactions_view_time.js | Should have stored the interaction time. - 0 > 10000 - JS frame ::/browser_interactions_view_time.js :: assertDatabaseValues :: line 40
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-05-30 18:22:26+00:00
Resolved: 2021-07-06 17:01:54+00:00

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

---
```
[task 2021-05-30T16:41:00.039Z] 16:41:00     INFO - TEST-PASS | browser/components/places/tests/browser/interactions/browser_interactions_view_time.js | Should have saved the page into the database - "https://example.com/" == "https://example.com/" - 
[task 2021-05-30T16:41:00.040Z] 16:41:00     INFO - Buffered messages finished
[task 2021-05-30T16:41:00.042Z] 16:41:00     INFO - TEST-UNEXPECTED-FAIL | browser/components/places/tests/browser/interactions/browser_interactions_view_time.js | Should have stored the interaction time. - 0 > 10000 - JS frame :: chrome://mochitests/content/browser/browser/components/places/tests/browser/interactions/browser_interactions_view_time.js :: assertDatabaseValues :: line 40
[task 2021-05-30T16:41:00.042Z] 16:41:00     INFO - Stack trace:
[task 2021-05-30T16:41:00.043Z] 16:41:00     INFO - chrome://mochitests/content/browser/browser/components/places/tests/browser/interactions/browser_interactions_view_time.js:assertDatabaseValues:40
[task 2021-05-30T16:41:00.044Z] 16:41:00     INFO - GECKO(5609) | console.debug: InteractionsManager: "End of interaction for" ({url:"https://example.com/browser", totalViewTime:20061.775079})
[task 2021-05-30T16:41:00.047Z] 16:41:00     INFO - TEST-PASS | browser/components/places/tests/browser/interactions/browser_interactions_view_time.js | Should have saved the page into the database - "https://example.com/" == "https://example.com/" - 
```
Bug: Firefox 78.10.1 ESR (64-bit): All saved logins dissappear from lockwise when the MOZ_FORCE_DISABLE_E10S environment variable is set. All logins return when the variable is unset. Using Win 7 64.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-05-30 19:56:01+00:00
Resolved: 2021-05-31 12:55:38+00:00

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

Steps to reproduce:

Clear from summary.


Actual results:

Clear from summary.
Bug: When 2 windows are open in a dual monitor setup and the window on the secondary monitor is minimized, when maximized, Firefox opens the window on the primary monitor instead of the secondary monitor again
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-05-30 21:54:24+00:00
Resolved: 2021-06-03 00:38:55+00:00

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

Steps to reproduce:

1) Open 2 windows of Firefox and dragged one window to the secondary monitor in an extended display setup.
2) Minimize the window on the primary monitor.
3) Minimize the window on the secondary monitor.
4) Maximize the window which was located on the secondary monitor.


Actual results:

The window maximized on the primary monitor.


Expected results:

The window maximizing on the secondary monitor.
Bug: 3.62% installer size (OSX) regression on Fri May 28 2021
Status: RESOLVED
Priority: --
Resolution: FIXED
Created: 2021-05-31 07:50:33+00:00
Resolved: 2021-07-15 09:42:13+00:00

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

### Regressions:

| **Ratio** | **Suite** | **Test** | **Platform** | **Options** | **Absolute values (old vs new)**| 
|--|--|--|--|--|--| 
| 4% | installer size |  | osx-cross |  | 80,144,193.08 -> 83,042,250.92 |


Details of the alert can be found in the [alert summary](https://treeherder.mozilla.org/perfherder/alerts?id=30219), 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 offending patch(es) will be backed out** in accordance with our [regression policy](https://www.mozilla.org/en-US/about/governance/policies/regressions/).

For more information on performance sheriffing please see our [FAQ](https://wiki.mozilla.org/TestEngineering/Performance/FAQ).
Bug: startup crash or hang
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-05-31 11:13:46+00:00
Resolved: 2021-06-26 13:47:23+00:00

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

Steps to reproduce:

1.Start Laptop(Win10)
2.After sometime Double Click on firefox icon



Actual results:

After launching firefox browser sometimes it take more than 5 minutes to open or
sometime it get crashed


Expected results:

After launching firefox browser it should be stable
Bug: Start-up pop-up is dismissed when selecting 'Not now' on 'Say hello to a new Firefox' page
Status: RESOLVED
Priority: --
Resolution: INVALID
Created: 2021-05-31 12:20:28+00:00
Resolved: 2021-06-03 22:19:48+00:00

**Affected versions**
* Firefox 89.0-build2 (20210527174632)

**Affected platforms**
* macOS 10.13 and macOS 10.14

**Steps to reproduce**
1.  Download an old Firefox build. Eg. http://archive.mozilla.org/pub/firefox/candidates/88.0-candidates/build2/mac/en-US/
2. Set the update channel from 'release' to 'release-cdntest'.
3. Launch Firefox and trigger the update from 'About Firefox'.
4. Restart Firefox.
5. Select 'Not now' from 'Say hello to a new Firefox' pop-up.

**Expected result**
* 'Get a clean start with an update theme' page is displayed and a theme can be selected.

**Actual result**
* Pop-up is dismissed.

**Regression range**
* Regression cannot be searched. 

**Additional notes**
* The issue is not reproducible on macOS 10.15, Windows 10x64, or on Ubuntu 20.04x64.
Bug: Intermittent browser/base/content/test/tabs/browser_tab_tooltips.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-05-31 14:42:03+00:00
Resolved: 2023-07-05 12:03:32+00:00

**Filed by:** cbrindusan [at] mozilla.com
**Parsed log:** https://treeherder.mozilla.org/logviewer?job_id=341280040&repo=autoland
**Full log:** https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ODw8vjOgRZ-_wttvG624Hw/runs/0/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/ODw8vjOgRZ-_wttvG624Hw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---
```
[task 2021-05-31T13:50:43.982Z] 13:50:43     INFO - TEST-START | browser/base/content/test/tabs/browser_tab_tooltips.js
[task 2021-05-31T13:51:28.996Z] 13:51:28     INFO - TEST-INFO | started process screentopng
[task 2021-05-31T13:51:29.289Z] 13:51:29     INFO - TEST-INFO | screentopng: exit 0
[task 2021-05-31T13:51:29.291Z] 13:51:29     INFO - Buffered messages logged at 13:50:43
[task 2021-05-31T13:51:29.291Z] 13:51:29     INFO - Entering test bound 
[task 2021-05-31T13:51:29.295Z] 13:51:29     INFO - Buffered messages logged at 13:50:44
[task 2021-05-31T13:51:29.296Z] 13:51:29     INFO - Console message: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "data:text/html,<html><head><title>A Tab</title></head><body>Hello</body></html>" line: 0}]
[task 2021-05-31T13:51:29.297Z] 13:51:29     INFO - Buffered messages finished
[task 2021-05-31T13:51:29.297Z] 13:51:29     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/tabs/browser_tab_tooltips.js | Test timed out - 
```
Bug: Spellcheck items not available the first time a context menu is opened in a reloaded frame
Status: RESOLVED
Priority: --
Resolution: WONTFIX
Created: 2021-05-31 15:47:10+00:00
Resolved: 2021-10-21 16:29:29+00:00

**Affected versions**
* Firefox 89.0
* Latest Nightly 90.0a1

**Affected platforms**
* Windows 10 64bit
* MacOS 11.3
* Ubuntu 18.04

**Steps to reproduce**
1. Start Firefox
2. Visit https://www.w3schools.com/html/tryit.asp?filename=tryhtml_elem_textarea
3. Right click inside textarea
4. Enable Check Spelling (if not already enabled)
5. Right click inside textarea again
6. Select This Frame and Reload Frame
7. Right click inside the textarea again

**Expected result**
* The same labels are displayed inside contextmenu 

**Actual result**
* Check Spelling and Languages are missing from contextmenu also the left padding used by the checkmark icon is missing as well from both contextmenus.

**Regression range**
* This is not a regression, it also reproduces in the first Nightly where `browser.proton.contextmenus.enabled` pref was first available in about:config (in bug 1698132)

**Additional notes**
* If dismissing the faulty contextmenu and enabling it again, it will be displayed as expected.

**Suggested severity**
* Since this is fixed if context menu is reopened and not sure who many users will run into this I would say it should have an S3 severity since the issue is about missing labels.
Bug: firefox keeps overloading and crashing my pc you should fix this in the next update
Status: RESOLVED
Priority: --
Resolution: INCOMPLETE
Created: 2021-05-31 19:10:49+00:00
Resolved: 2021-06-18 07:46:32+00:00

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

Steps to reproduce:

normal usage


Actual results:

overloads and freezes my pc


Expected results:

continuous workflow
Bug: Tab-to-search engines unrelated to the autofilled domain sometimes appear
Status: RESOLVED
Priority: P1
Resolution: FIXED
Created: 2021-05-31 19:11:26+00:00
Resolved: 2021-07-05 13:16:55+00:00

From bug 1610718 comment 16:

> We were specifically concerned about inundating the user with too many tab-to-search results. We're only supposed to show a tab-to-search result if the engine domain is autofilled. It would be annoying if we showed a Google tab-to-search result every time "g" was typed, but that appears to be almost what we're doing. I can reproduce in a different scenario: when an autofilled site starts with "g", we show a tab-to-search result for Google Drive. Weirdly, if I disable my Google Drive engine, neither Google nor Google Maps (which I have installed as an OpenSearch engine!) shows a tab-to-search result. It's not clear what's broken here.

> I ran mozregression and the Wikipedia issue was sort of reproducible on the 2020-10-01 build when tab-to-search was introduced. A key difference being that we didn't yet show a Wikipedia tab-to-search result when "wikipedia.org" was autofilled, because the engine was actually for <locale>.wikipedia.org. I could reproduce the issue after installing an OpenSearch engine that pointed directly to wikipedia.org.

> Something weird is happening with the muxer here.
Bug: Shift+up/Shift+down for text selection fail in the context of the address bar on Mac
Status: VERIFIED
Priority: P3
Resolution: FIXED
Created: 2021-05-31 21:12:52+00:00
Resolved: 2023-06-27 12:50:54+00:00

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

Steps to reproduce:

1. Enter text in address bar
2. Place cursor somewhere in the middle
3. Press either Shift+Up or Shift+Down


Actual results:

selection moves from the text into the suggestions, the same as pressing up or down without holding shift


Expected results:

Shift+Up: select text between insertion point and the start of the line, cursor now at start of line
Shift+Down: select text between insertion point and the end of the line, cursor now at end of line

This appears to already be the behavior of Shift+Control+Up / Shift+Control+Down in this context.

Shift+Up/Shift+Down being bound to moving the cursor with selection is standard behavior for single line text fields on MacOS, and both Safari and Chrome on MacOS support this in location bar contexts.
Bug: "Show All Bookmarks" is inconsistent with appmenu (Manage Bookmarks)
Status: RESOLVED
Priority: P3
Resolution: FIXED
Created: 2021-05-31 23:47:23+00:00
Resolved: 2021-06-10 03:51:01+00:00

Steps to reproduce:

1. Click Bookmarks menu
2. Exit menu
3. Click appmenu
4. Click Bookmarks

What happens:

I see an item labeled "Show All Bookmarks" in the Bookmarks menu and "Manage Bookmarks" at the bottom of the menu in the appmenu. 

Expected result:

A consistent label. "Manage Bookmarks" seems to be the later one and it makes sense to me to change the menubar entry to that.
Bug: tab gets moved to new window when canceling a menu action
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-06-01 00:51:47+00:00
Resolved: 2021-06-22 20:41:19+00:00

STR (mac):
control-click a tab (on mac, RMB I assume on windows/linux).
Go down to Open in Container tab
Mouse over submenu
Click in the page outside of the menu/submenu

RESULT:
menu is cancelled, but the tab is moved to a new window

Repeatable, Nightly 5/30 on mac

May be related to other instances I've seen recently where "Move Tab -> Move Tab to End" sometimes causes the tab to be moved to a new window (it appears)
Bug: Context Menu styling in Win7
Status: RESOLVED
Priority: P3
Resolution: DUPLICATE
Created: 2021-06-01 01:11:31+00:00
Resolved: 2021-06-04 11:16:06+00:00

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

Steps to reproduce:

I dont know if this is a bug or not, but now context menus has some kind of "border" around them. I dont mind them, but dont know if this is intensional or not.

Also the context menu in the downloads panel seems broken.

Windows 7.
Nightly 91.0a1 (2021-05-31) (64-bit)
Clean Profile.
Bug: Bookmarks Toolbar does not show on new tab with blank page.
Status: RESOLVED
Priority: --
Resolution: DUPLICATE
Created: 2021-06-01 02:01:13+00:00
Resolved: 2021-06-07 08:48:47+00:00

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

Steps to reproduce:

Set new tab to open as blank page and bookmarks toolbar to show on new tab.


Actual results:

Bookmarks toolbar does not show on new tab.


Expected results:

Bookmarks toolbar should show on new tab.
Bug: Intermittent browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_nimbus.js | Test timed out -
Status: RESOLVED
Priority: P5
Resolution: INCOMPLETE
Created: 2021-06-01 03:16:22+00:00
Resolved: 2022-03-08 17:02:16+00:00

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

---
```
INFO - TEST-START | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_nimbus.js
[task 2021-06-01T02:57:20.853Z] 02:57:20     INFO - TEST-INFO | started process screentopng
[task 2021-06-01T02:57:21.151Z] 02:57:21     INFO - TEST-INFO | screentopng: exit 0
[task 2021-06-01T02:57:21.151Z] 02:57:21     INFO - Buffered messages logged at 02:55:50
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - TEST-PASS | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_nimbus.js | Sanity check the temporary file doesn't exist. - true == true - 
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - Entering test bound test_experiment_plain_text
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - Buffered messages finished
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - TEST-UNEXPECTED-FAIL | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_nimbus.js | Test timed out - 
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - GECKO(1559) | MEMORY STAT | vsize 20975397MB | residentFast 1153MB
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - TEST-OK | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_nimbus.js | took 90047ms
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - checking window state
[task 2021-06-01T02:57:21.152Z] 02:57:21     INFO - TEST-START | browser/components/privatebrowsing/test/browser/browser_privatebrowsing_about_search_banner.js
```