1932304 - Perma [tier 2] /notifications/cross-origin-nested.tentative.https.sub.html | nested first party iframe - assert_true: notification should be shown expected true got false

Status: RESOLVED INCOMPLETE

(Core :: DOM: Notifications, defect, P5)

Description

[Treeherder Bug Filer]

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

---

[task 2024-11-20T07:22:29.943Z] 07:22:29     INFO - TEST-START | /notifications/cross-origin-nested.tentative.https.sub.html
[task 2024-11-20T07:22:29.947Z] 07:22:29     INFO - Closing window 9295288e-0d9b-41e1-85c1-8fe249c81f1c
[task 2024-11-20T07:22:30.331Z] 07:22:30     INFO - PID 23001 | GLib-GIO-Message: 07:22:30.330: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.
[task 2024-11-20T07:22:31.007Z] 07:22:31     INFO - 
[task 2024-11-20T07:22:31.007Z] 07:22:31     INFO - TEST-PASS | /notifications/cross-origin-nested.tentative.https.sub.html | third party iframe 
[task 2024-11-20T07:22:31.007Z] 07:22:31     INFO - TEST-UNEXPECTED-FAIL | /notifications/cross-origin-nested.tentative.https.sub.html | nested first party iframe - assert_true: notification should be shown expected true got false
[task 2024-11-20T07:22:31.007Z] 07:22:31     INFO - @https://web-platform.test:8443/notifications/cross-origin-nested.tentative.https.sub.html:60:14
[task 2024-11-20T07:22:31.012Z] 07:22:31     INFO - ..
[task 2024-11-20T07:22:31.012Z] 07:22:31     INFO - TEST-OK | /notifications/cross-origin-nested.tentative.https.sub.html | took 1066ms
[task 2024-11-20T07:22:31.015Z] 07:22:31     INFO - PID 23001 | [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt
[task 2024-11-20T07:22:31.016Z] 07:22:31     INFO - PID 23001 | 1732087351012	Marionette	INFO	Stopped listening on port 47240
[task 2024-11-20T07:22:31.655Z] 07:22:31     INFO - PID 23001 | [GFX1-]: VideoBridgeParent receives IPC close with reason=AbnormalShutdown
[task 2024-11-20T07:22:31.685Z] 07:22:31     INFO - Browser exited with return code -15
[task 2024-11-20T07:22:31.686Z] 07:22:31     INFO - Closing logging queue
[task 2024-11-20T07:22:31.687Z] 07:22:31     INFO - queue closed
[task 2024-11-20T07:22:31.699Z] 07:22:31     INFO - Application command: /builds/worker/workspace/build/application/firefox/firefox --marionette about:blank -profile /tmp/tmp3m82lkb2
[task 2024-11-20T07:22:31.721Z] 07:22:31     INFO - PID 23697 | Gtk-Message: 07:22:27.420: Failed to load module "canberra-gtk-module"
[task 2024-11-20T07:22:31.722Z] 07:22:31     INFO - PID 23697 | Gtk-Message: 07:22:27.421: Failed to load module "canberra-gtk-module"
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: glxtest: libpci missing
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: glxtest: libEGL missing
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: glxtest: libGL.so.1 missing
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: No GPUs detected via PCI
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | 1732087347904	Marionette	INFO	Marionette enabled
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | 1732087348088	Marionette	INFO	Listening on port 55438
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: Failed GL context creation for WebRender: 0
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: FEATURE_FAILURE_WEBRENDER_INITIALIZE_UNSPECIFIED
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=true
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [GFX1-]: Fallback WR to SW-WR
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | console.error: ({})
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [ERROR error_support::handling] logins-unexpected: Error parsing URL: relative URL with a cannot-be-a-base base
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | [ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Remote settings error: Error parsing URL: relative URL with a cannot-be-a-base base
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | console.error: URLBar - QuickSuggest.SuggestBackendRust: "Error initializing SuggestStore:"
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - PID 23697 | console.error: URLBar - QuickSuggest.SuggestBackendRust: (new Error("reason: Error from Remote Settings: Remote settings error: Error parsing URL: relative URL with a cannot-be-a-base base", "resource://gre/modules/RustSuggest.sys.mjs", 1705))
[task 2024-11-20T07:22:31.728Z] 07:22:31     INFO - Starting runner
[task 2024-11-20T07:22:32.348Z] 07:22:32     INFO - TEST-START | /notifications/cross-origin-serviceworker.tentative.https.sub.html

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1931497

:saschanaz, since you are the author of the regressor, bug 1931497, could you take a look?

For more information, please visit BugBot documentation.

Comment 2

[Kagami Rosylight [:saschanaz] (they/them)]

linux32 specific? I don't think that can be a thing... 🤔 Let's wait and see a bit.

Comment 3

[Intermittent Failures Robot]

18 failures in 3002 pushes (0.006 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 14
• try: 4

Platform and build breakdown:

• linux1804-32-shippable-qr: 18
  • opt: 18

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1932304&startday=2024-11-18&endday=2024-11-24&tree=all

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1931497

Comment 5

[Andrew Sutherland [:asuth] (he/him)]

Since :saschanaz is out, I'll take a look.

Comment 6

[Intermittent Failures Robot]

41 failures in 3953 pushes (0.01 failures/push) were associated with this bug in the last 7 days.

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:

• mozilla-beta: 28
• mozilla-central: 9
• try: 4

Platform and build breakdown:

• linux1804-32-shippable-qr: 41
  • opt: 41

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1932304&startday=2024-11-25&endday=2024-12-01&tree=all

Comment 7

[Intermittent Failures Robot]

34 failures in 4722 pushes (0.007 failures/push) were associated with this bug in the last 7 days.

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:

• mozilla-beta: 31
• try: 3

Platform and build breakdown:

• linux1804-32-shippable-qr: 34
  • opt: 34

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1932304&startday=2024-12-02&endday=2024-12-08&tree=all

Comment 8

[Andrew Sutherland [:asuth] (he/him)]

The failure proper seems legit and not x32 specific?

The failure line looks like:

TEST-UNEXPECTED-FAIL | /notifications/cross-origin-nested.tentative.https.sub.html | nested first party iframe - assert_true: notification should be shown expected true got false
@https://web-platform.test:8443/notifications/cross-origin-nested.tentative.https.sub.html:60:14

Which is this line which corresponds to the ABA iframe which is notable.

Looking at https://wpt.fyi/results/notifications/cross-origin-nested.tentative.https.sub.html?label=experimental&label=master&aligned and in particular the history, we can see that we used to pass the "nested first party iframe" but started failing it when bug 1931497 landed.

It seems like maybe we're just not running these tentative tests on that many platforms in the first case, I guess? This may not be 32-bit specific?

This stopped permafailing on m-c because wpt-sync bot made the test an expected failure.

So according to the intermittent-failures, this m-c run on Nov 27th was the last permafail in wpt8, and then this next push with /notifications still in wpt8 was green

Looking at the commits in that push with --stat we see for this commit:

 testing/web-platform/meta/notifications/cross-origin-nested.tentative.https.sub.html.ini                                               |   4 ++
 testing/web-platform/meta/notifications/event-onclose.https.html.ini                                                                   |   6 ---
 testing/web-platform/meta/notifications/idlharness.https.any.js.ini                                                                    |  12 ++++-
 testing/web-platform/meta/notifications/instance.https.window.js.ini                                                                   |  58 +++++++++---------------
 testing/web-platform/meta/notifications/lang.https.html.ini                                                                            |   2 +
 testing/web-platform/meta/notifications/shownotification.https.window.js.ini                                                           |   5 ++
 testing/web-platform/meta/notifications/tag.https.html.ini                                                                             |   4 +-

And looking at the specific diff we see the sync robot made this an expected fail:

new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/notifications/cross-origin-nested.tentative.https.sub.html.ini
@@ -0,0 +1,4 @@
+[cross-origin-nested.tentative.https.sub.html]
+  [nested first party iframe]
+    expected:
+      if (processor == "x86") and (os == "linux"): FAIL

Comment 9

[Intermittent Failures Robot]

Summary

25 failures in 4615 pushes (0.005 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-beta: 24
• try: 1

Platform and build breakdown:

• linux1804-32-shippable-qr: 25
  • opt: 25

Table

	1proc	1proc-s	a11y-checks-swr	condprof	condprof-s	fis	fis-hv	fis-hv-s	fis-s	headless	headless-s	http2	http3	msix	msix-s	no_variant	nofis	nofis-aab	nofis-s	nofis-ship	nofis-ship-s	nofis-spi	nofis-swr	nofis-swr-s	nogpu	nogpu-s	s	spi	spi-nw	spi-nw-1proc	spi-nw-s	spi-s	swr	wr-dc1-p	xorig	xorig-s
linux1804-32-shippable-qr/opt																											25

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1932304&startday=2024-12-09&endday=2024-12-15&tree=all

Comment 10

[Kagami Rosylight [:saschanaz] (they/them)]

Perhaps I should test with linux 32bit build, it certainly doesn't fail on my local Windows x64 build, can't understand why perma only there and not even intermittent anywhere else.

Comment 11

[Cosmin Sabou [:CosminS]]

Looking at the failures they do happen only on linux1804-32-shippable-qr https://treeherder.mozilla.org/intermittent-failures/bugdetails?startday=2024-12-09&endday=2024-12-16&tree=all&failurehash=all&bug=1932304

Comment 12

[Kagami Rosylight [:saschanaz] (they/them)]

Thanks, and that list only has mozilla-beta (and one try run also based on mozilla-beta), very interesting.

Comment 13

[Kagami Rosylight [:saschanaz] (they/them)]

Mysteriously not on 32bit build, but I get this on 64bit Linux local build on m-c without beta simulation:

 1:17.00 TEST_START: /notifications/cross-origin-nested.tentative.https.sub.html
 1:17.02 INFO Closing window 777a37db-9e77-48c8-bce0-197925f5b427
 1:19.38 pid:277738 [Parent 277738, Main Thread] WARNING: Failed to connect to proxy: 'glib warning', file /home/krosylight/gecko/toolkit/xre/nsSigHandlers.cpp:201
 1:19.38 pid:277738 (firefox-default:277738): libnotify-WARNING **: 19:38:11.226: Failed to connect to proxy
 1:19.87 TEST_END: Test OK. Subtests passed 3/4. Unexpected 1
FAIL nested first party iframe - assert_true: notification should be shown expected true got false
@https://web-platform.test:8443/notifications/cross-origin-nested.tentative.https.sub.html:60:14

 1:19.87 pid:277738 1734547091717       Marionette      INFO    Stopped listening on port 46605

And this is the only test failing when I run the whole notification WPT test. 🤔

Comment 14

[Intermittent Failures Robot]

Summary

18 failures in 3774 pushes (0.005 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-beta: 17
• try: 1

Platform and build breakdown:

• linux1804-32-shippable-qr: 18
  • opt: 18

Table

	1proc	1proc-s	fis	fis-hv	fis-hv-s	fis-s	headless	http2	http3	mda-gpu-s	no_variant	nofis	nofis-aab	nofis-s	nofis-ship	nofis-ship-s	nofis-spi	nofis-swr	nofis-swr-s	nogpu	nogpu-s	s	spi	spi-nw	spi-nw-s	swr	wmfme	xorig	xorig-s
linux1804-32-shippable-qr/opt																						18

For more details, see:

https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1932304&startday=2024-12-16&endday=2024-12-22&tree=all

Comment 15

[BugBot [:suhaib / :marco/ :calixte]]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Comment 17

[Kagami Rosylight [:saschanaz] (they/them)]

Per bug 1938568.

Comment 18

[Kagami Rosylight [:saschanaz] (they/them)]

So this stopped being a problem as soon as it's merged to the release branch? 🤔🤔🤔🤔

Comment 19

[BugBot [:suhaib / :marco/ :calixte]]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Comment 20

[Kagami Rosylight [:saschanaz] (they/them)]

This was total mysterious.