Bug 265057 - REGRESSION (270849@main): [ macOS ] http/tests/inspector/target/provisional-load-cancels-previous-load.html is a constant failure
Summary: REGRESSION (270849@main): [ macOS ] http/tests/inspector/target/provisional-l...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2023-11-17 11:41 PST by Marta Darbinyan
Modified: 2023-11-19 18:19 PST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marta Darbinyan 2023-11-17 11:41:57 PST
Description:
http/tests/inspector/target/provisional-load-cancels-previous-load.html is failing on macOS ToT starting from 270849@main.

This issue can be bisected to 270849@main using the command: 
run-webkit-tests --release --iterations=1 http/tests/inspector/target/provisional-load-cancels-previous-load.html

History:
https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Finspector%2Ftarget%2Fprovisional-load-cancels-previous-load.html

Diff Crash:
@@ -8,10 +8,7 @@
 PASS: Target 1 should be provisional.
 PASS: Target 1 should be paused on start.
 PASS: Should receive TargetRemoved event for target 1
-PASS: Should receive TargetAdded event for target 2.
-PASS: Target 2 should be provisional.
-PASS: Target 2 should be paused on start.
-PASS: Should receive TargetRemoved event for target 0
-PASS: Should receive DidCommitProvisionalTarget event 0 => 2.
-PASS: Should have seen 3 different targets.
+FAIL: Should have seen 3 different targets.
+    Expected: 3
+    Actual: 2


Link:
https://build.webkit.org/results/GTK-Linux-64-bit-Release-Skip-Failing-Tests/270849@main%20(14860)/http/tests/inspector/target/provisional-load-cancels-previous-load-pretty-diff.html
Comment 1 Radar WebKit Bug Importer 2023-11-17 11:42:46 PST
<rdar://problem/118574473>
Comment 2 Alexey Proskuryakov 2023-11-19 18:19:52 PST
Seems like this got fixed via bug 265063 for some reason?