Bug 229099 - Rebaselining [ Win EWS ] http/tests/misc/webtiming-slow-load.py
Summary: Rebaselining [ Win EWS ] http/tests/misc/webtiming-slow-load.py
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-08-13 14:47 PDT by ayumi_kojima
Modified: 2022-02-11 14:23 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 ayumi_kojima 2021-08-13 14:47:52 PDT
http/tests/misc/webtiming-slow-load.py

Is failing on Windows-EWS and the OpenSource https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fmisc%2Fwebtiming-slow-load.py

Diff:

--- /home/buildbot/worker/Windows-EWS/build/layout-test-results/http/tests/misc/webtiming-slow-load-expected.txt
+++ /home/buildbot/worker/Windows-EWS/build/layout-test-results/http/tests/misc/webtiming-slow-load-actual.txt
@@ -3,9 +3,9 @@
 On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
 
 
-FAIL timing.requestStart should be non-zero. Was 0
-FAIL timing.responseStart should be non-zero. Was 0
-FAIL timing.responseEnd should be non-zero. Was 0
+PASS timing.requestStart is non-zero.
+PASS timing.responseStart is non-zero.
+PASS timing.responseEnd is non-zero.
 PASS successfullyParsed is true
 
 TEST COMPLETE

Result (EWS): https://ews-build.s3-us-west-2.amazonaws.com/Windows-EWS/r435325-101425/results.html

Looks like it started failing recently at around https://ews-build.webkit.org/#/builders/10/builds/101425. Will research more.
Comment 1 Radar WebKit Bug Importer 2021-08-13 14:48:16 PDT
<rdar://problem/81917212>
Comment 2 ayumi_kojima 2021-08-13 15:07:35 PDT
Updated test expectations https://trac.webkit.org/changeset/281038/webkit

According to the Open-source history, it looks like the failure started between r280957 and r280913, but I cannot confirm that since I cannot reproduce the failure.
Comment 3 Ryan Haddad 2021-08-13 15:58:07 PDT
Could be related to https://trac.webkit.org/changeset/280931/webkit, which dealt with performance timing.

If this is consistently "failing", it looks like it is a progression since we are now passing more subtests.

We should consider rebaselining this/
Comment 4 ayumi_kojima 2021-08-17 13:45:50 PDT
Rebaselined and removed the expectations I marked previously:  https://trac.webkit.org/changeset/281162/webkit