Adding upstream version 125.0.1.upstream/125.0.1

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 7 insertions, 5 deletions

diff --git a/security/manager/ssl/tests/unit/test_ocsp_timeout.js b/security/manager/ssl/tests/unit/test_ocsp_timeout.js
index 8d606bc028..5d3487bfe7 100644
--- a/security/manager/ssl/tests/unit/test_ocsp_timeout.js
+++ b/security/manager/ssl/tests/unit/test_ocsp_timeout.js
@@ -21,7 +21,7 @@ var gSocketListener = {
     socketTransport.setTimeout(Ci.nsISocketTransport.TIMEOUT_READ_WRITE, 30);
   },
 
-  onStopListening(serverSocket, status) {},
+  onStopListening() {},
 };
 
 function run_test() {
@@ -77,8 +77,9 @@ function add_one_test(useHardFail, timeoutPrefName, timeoutMilliseconds) {
     // prevent intermittent failures (this only appeared to be a problem on
     // Windows XP). See Bug 1121117.
     const FUZZ_MS = 300;
-    ok(
-      timeDifference + FUZZ_MS > timeoutMilliseconds,
+    Assert.greater(
+      timeDifference + FUZZ_MS,
+      timeoutMilliseconds,
       `OCSP timeout should be ~${timeoutMilliseconds}s for ` +
         `${useHardFail ? "hard" : "soft"}-fail`
     );
@@ -86,8 +87,9 @@ function add_one_test(useHardFail, timeoutPrefName, timeoutMilliseconds) {
     // (Unfortunately, we probably can't have a tight upper bound on
     // how long is too long for this test, because we might be running
     // on slow hardware.)
-    ok(
-      timeDifference < 60000,
+    Assert.less(
+      timeDifference,
+      60000,
       "Automatic OCSP timeout shouldn't be more than 60s"
     );