Bug 1513561 [wpt PR 14479] - Update wpt metadata, a=testonly
authormoz-wptsync-bot <wptsync@mozilla.com>
Wed, 12 Dec 2018 19:37:22 +0000
changeset 515048 0e4cc4552f5ef0af9e71237c801638e7bfc587e3
parent 515047 4f9e6a2b7a8fb41aa993ee0ae21a586e38d33c67
child 515049 ff9fa16f3af38e3521bc304e5700b84d5dcbb696
push id1953
push userffxbld-merge
push dateMon, 11 Mar 2019 12:10:20 +0000
treeherdermozilla-release@9c35dcbaa899 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1513561, 14479
milestone66.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1513561 [wpt PR 14479] - Update wpt metadata, a=testonly wpt-pr: 14479 wpt-type: metadata
testing/web-platform/meta/resource-timing/buffer-full-add-after-full-event.html.ini
testing/web-platform/meta/resource-timing/buffer-full-add-entries-during-callback-that-drop.html.ini
testing/web-platform/meta/resource-timing/buffer-full-add-entries-during-callback.html.ini
testing/web-platform/meta/resource-timing/buffer-full-add-then-clear.html.ini
testing/web-platform/meta/resource-timing/buffer-full-inspect-buffer-during-callback.html.ini
testing/web-platform/meta/resource-timing/buffer-full-set-to-current-buffer.html.ini
testing/web-platform/meta/resource-timing/buffer-full-store-and-clear-during-callback.html.ini
testing/web-platform/meta/resource-timing/buffer-full-then-increased.html.ini
testing/web-platform/meta/resource-timing/buffer-full-when-populate-entries.html.ini
testing/web-platform/meta/resource-timing/resource_timing_store_and_clear_during_callback.html.ini
testing/web-platform/meta/service-workers/service-worker/performance-timeline.https.html.ini
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-add-after-full-event.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-add-after-full-event.html]
+  expected: TIMEOUT
+  [Test that entry was added to the buffer after a buffer full event]
+    expected: TIMEOUT
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-add-entries-during-callback-that-drop.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-add-entries-during-callback-that-drop.html]
+  expected: TIMEOUT
+  [Test that entries synchronously added to the buffer during the callback are dropped]
+    expected: TIMEOUT
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-add-entries-during-callback.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-add-entries-during-callback.html]
+  expected: TIMEOUT
+  [Test that entries synchronously added to the buffer during the callback don't get dropped if the buffer is increased]
+    expected: TIMEOUT
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-add-then-clear.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-add-then-clear.html]
+  expected: ERROR
+  [Test that if the buffer is cleared after entries were added to the secondary buffer, those entries make it into the primary one]
+    expected: FAIL
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-inspect-buffer-during-callback.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-inspect-buffer-during-callback.html]
+  expected: ERROR
+  [Test that entries in the secondary buffer are not exposed during the callback and before they are copied to the primary buffer]
+    expected: TIMEOUT
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-set-to-current-buffer.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-set-to-current-buffer.html]
+  expected: TIMEOUT
+  [Test that entries added and event firing happened in the right sequence]
+    expected: TIMEOUT
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-store-and-clear-during-callback.html.ini
@@ -0,0 +1,4 @@
+[buffer-full-store-and-clear-during-callback.html]
+  [Test that entries overflowing the buffer trigger the buffer full event, can be stored, and find themselves in the primary buffer after it's cleared.]
+    expected: FAIL
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-then-increased.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-then-increased.html]
+  expected: ERROR
+  [Test that overflowing the buffer and immediately increasing its limit does not trigger the resourcetimingbufferfull event]
+    expected: FAIL
+
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/meta/resource-timing/buffer-full-when-populate-entries.html.ini
@@ -0,0 +1,5 @@
+[buffer-full-when-populate-entries.html]
+  expected: ERROR
+  [Test that a buffer full event does not bubble and that resourcetimingbufferfull is called only once per overflow]
+    expected: TIMEOUT
+
deleted file mode 100644
--- a/testing/web-platform/meta/resource-timing/resource_timing_store_and_clear_during_callback.html.ini
+++ /dev/null
@@ -1,25 +0,0 @@
-[resource_timing_store_and_clear_during_callback.html]
-  [http://web-platform.test:8000/resources/testharnessreport.js is expected to be in the Resource Timing buffer]
-    expected: FAIL
-
-  [http://web-platform.test:8000/resource-timing/resources/empty_script.js is expected to be in the Resource Timing buffer]
-    expected: FAIL
-
-  [6 resource timing entries should be moved to global buffer.]
-    expected: FAIL
-
-  [No entry should be stored in resource timing buffer since its cleared once an item arrived.]
-    expected: FAIL
-
-  [http://web-platform.test:8000/resource-timing/resources/webperftestharness.js is expected to be in the Resource Timing buffer]
-    expected: FAIL
-
-  [http://web-platform.test:8000/resources/testharness.js is expected to be in the Resource Timing buffer]
-    expected: FAIL
-
-  [http://web-platform.test:8000/resource-timing/resources/resource_timing_test0.js is expected to be in the Resource Timing buffer]
-    expected: FAIL
-
-  [http://web-platform.test:8000/resource-timing/resources/webperftestharnessextension.js is expected to be in the Resource Timing buffer]
-    expected: FAIL
-
--- a/testing/web-platform/meta/service-workers/service-worker/performance-timeline.https.html.ini
+++ b/testing/web-platform/meta/service-workers/service-worker/performance-timeline.https.html.ini
@@ -1,6 +1,13 @@
 prefs: [privacy.reduceTimerPrecision:false]
 [performance-timeline.https.html]
+  expected: TIMEOUT
   [Resource Timing]
-    expected: FAIL
+    expected: TIMEOUT
     bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1432758
 
+  [Test Performance Timeline API in Service Worker]
+    expected: TIMEOUT
+
+  [empty service worker fetch event included in performance timings]
+    expected: NOTRUN
+