Mark upgrade-transaction-lifecycle-committed.any.js as unstable

Author: nolanlawson

src/test/web-platform-tests/manifests/upgrade-transaction-lifecycle-committed.any.toml

@@ -0,0 +1,6 @@
+# See discussion in https://github.com/dumbmatter/fakeIndexedDB/issues/167
+# The issue here is a subtle timing issue with setTimeout vs setImmediate that's not straightforward to resolve in Node
+expectTimeout = "UNSTABLE"
+
+["in a setTimeout(0) callback after the complete event is fired for a committed transaction"]
+expectation = "UNSTABLE"

src/test/web-platform-tests/run-all.js

@@ -134,7 +134,11 @@ for (const absFilename of filenames) {
                 });
             }
 
-            if (generatedManifest.expectTimeout) {
+            if (expectedManifest?.contents?.expectTimeout === "UNSTABLE") {
+                // If the timeout is unstable, then don't pass/fail based on whether we actually got a timeout or not
+                generatedManifest.expectTimeout = "UNSTABLE";
+                numExpectedTimeouts += 1;
+            } else if (generatedManifest.expectTimeout) {
                 if (expectedManifest?.contents?.expectTimeout) {
                     numExpectedTimeouts += 1;
                 } else {