Recently we landed a patch in NSS to enable TLS 1.3 by default: https://hg.mozilla.org/projects/nss/rev/bc77cf318f388f55790b99d5f23a9c1f2bd9f900 When preparing to uplift this as part of D50840, I noticed test failures in `browser_networkIsolation.js`: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273385405&repo=try&lineNumber=6529 - I confirmed local failures with this updated default.
Bug 1592175 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Recently we landed a patch in NSS to enable TLS 1.3 by default: https://hg.mozilla.org/projects/nss/rev/bc77cf318f388f55790b99d5f23a9c1f2bd9f900 When preparing to uplift this as part of D50840, I noticed test failures in `browser_networkIsolation.js`: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273385405&repo=try&lineNumber=6529 - I confirmed local failures with this updated default. This test should handle the updated default (whether by not running, or running an updated version of itself).
Recently we landed a patch in NSS to enable TLS 1.3 by default: https://hg.mozilla.org/projects/nss/rev/bc77cf318f388f55790b99d5f23a9c1f2bd9f900 When preparing to uplift this as part of D50840, I noticed test failures in `browser_networkIsolation.js`: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273385405&repo=try&lineNumber=6529 - I confirmed local failures with this updated default. This test should handle the updated default (whether by not running, or running an updated version of itself). This may be a test server bug, but I haven't investigated that yet.
Recently we landed a patch in NSS to enable TLS 1.3 by default: https://hg.mozilla.org/projects/nss/rev/bc77cf318f388f55790b99d5f23a9c1f2bd9f900 When preparing to uplift this as part of D50840, I noticed test failures in `browser_networkIsolation.js`: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273385405&repo=try&lineNumber=6529 ``` [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/antitracking/test/browser/browser_networkIsolation.js | The third load SHOULD have been resumed - [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - Stack trace: [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - chrome://mochikit/content/browser-test.js:test_ok:1297 [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - chrome://mochitests/content/browser/toolkit/components/antitracking/test/browser/browser_networkIsolation.js:null:148 [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - promise callback*chrome://mochitests/content/browser/toolkit/components/antitracking/test/browser/browser_networkIsolation.js:null:138 [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest/<:1067 [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1102 [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:930 [task 2019-10-29T01:23:16.816Z] 01:23:16 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/waitForFocusInner/focusedOrLoaded/<:805 ``` I confirmed local failures with this updated default. This test should handle the updated default (whether by not running, or running an updated version of itself). This may be a test server bug, but I haven't investigated that yet.