1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-23 07:44:48 -05:00
denoland-deno/tools/wpt/expectation.json

9193 lines
546 KiB
JSON
Raw Normal View History

{
"WebCryptoAPI": {
"getRandomValues.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"getRandomValues.any.worker.html": true,
"derive_bits_keys": {
"ecdh_bits.https.any.html": [
"P-521 good parameters",
"P-521 mixed case parameters",
"P-521 with null length",
"P-521 short result",
"P-521 non-multiple of 8 bits",
"P-521 mismatched curves",
"P-521 public property of algorithm is not an ECDSA public key",
"P-521 no deriveBits usage for base key",
"P-521 base key is not a private key",
"P-521 public property value is a private key",
"P-521 public property value is a secret key",
"P-521 asking for too many bits"
],
"ecdh_bits.https.any.worker.html": [
"P-521 good parameters",
"P-521 mixed case parameters",
"P-521 with null length",
"P-521 short result",
"P-521 non-multiple of 8 bits",
"P-521 mismatched curves",
"P-521 public property of algorithm is not an ECDSA public key",
"P-521 no deriveBits usage for base key",
"P-521 base key is not a private key",
"P-521 public property value is a private key",
"P-521 public property value is a secret key",
"P-521 asking for too many bits"
],
"ecdh_keys.https.any.html": [
"P-521 good parameters",
"P-521 mixed case parameters",
"P-521 mismatched curves",
"P-521 public property of algorithm is not an ECDSA public key",
"P-521 no deriveKey usage for base key",
"P-521 base key is not a private key",
"P-521 public property value is a private key",
"P-521 public property value is a secret key"
],
"ecdh_keys.https.any.worker.html": [
"P-521 good parameters",
"P-521 mixed case parameters",
"P-521 mismatched curves",
"P-521 public property of algorithm is not an ECDSA public key",
"P-521 no deriveKey usage for base key",
"P-521 base key is not a private key",
"P-521 public property value is a private key",
"P-521 public property value is a secret key"
],
"hkdf.https.any.html?1-1000": true,
"hkdf.https.any.html?1001-2000": true,
"hkdf.https.any.html?2001-3000": true,
"hkdf.https.any.html?3001-last": true,
"hkdf.https.any.worker.html?1-1000": true,
"hkdf.https.any.worker.html?1001-2000": true,
"hkdf.https.any.worker.html?2001-3000": true,
"hkdf.https.any.worker.html?3001-last": true,
"pbkdf2.https.any.html?1-1000": true,
"pbkdf2.https.any.html?1001-2000": true,
"pbkdf2.https.any.html?2001-3000": true,
"pbkdf2.https.any.html?3001-4000": true,
"pbkdf2.https.any.html?4001-5000": true,
"pbkdf2.https.any.html?5001-6000": true,
"pbkdf2.https.any.html?6001-7000": true,
"pbkdf2.https.any.html?7001-8000": true,
"pbkdf2.https.any.html?8001-last": true,
"pbkdf2.https.any.worker.html?1-1000": true,
"pbkdf2.https.any.worker.html?1001-2000": true,
"pbkdf2.https.any.worker.html?2001-3000": true,
"pbkdf2.https.any.worker.html?3001-4000": true,
"pbkdf2.https.any.worker.html?4001-5000": true,
"pbkdf2.https.any.worker.html?5001-6000": true,
"pbkdf2.https.any.worker.html?6001-7000": true,
"pbkdf2.https.any.worker.html?7001-8000": true,
2022-09-22 05:07:50 -04:00
"pbkdf2.https.any.worker.html?8001-last": true,
"cfrg_curves_bits.https.any.html": [
"X25519 key derivation checks for all-zero value result with a key of order 0",
"X25519 key derivation checks for all-zero value result with a key of order 1",
"X25519 key derivation checks for all-zero value result with a key of order 8",
"X25519 key derivation checks for all-zero value result with a key of order p-1 (order 2)",
"X25519 key derivation checks for all-zero value result with a key of order p (=0, order 4)",
"X25519 key derivation checks for all-zero value result with a key of order p+1 (=1, order 1)",
"X448 key derivation checks for all-zero value result with a key of order 0",
"X448 key derivation checks for all-zero value result with a key of order 1",
"X448 key derivation checks for all-zero value result with a key of order p-1 (order 2)",
"X448 key derivation checks for all-zero value result with a key of order p (=0, order 4)",
"X448 key derivation checks for all-zero value result with a key of order p+1 (=1, order 1)",
"X25519 good parameters",
"X25519 mixed case parameters",
"X25519 with null length",
"X25519 short result",
"X25519 non-multiple of 8 bits",
"X25519 mismatched algorithms",
"X25519 no deriveBits usage for base key",
"X448 good parameters",
"X448 mixed case parameters",
"X448 with null length",
"X448 short result",
"X448 non-multiple of 8 bits",
"X448 mismatched algorithms",
"X448 no deriveBits usage for base key",
"X448 base key is not a private key",
"X448 public property value is a private key",
"X448 public property value is a secret key",
"X448 asking for too many bits"
],
"cfrg_curves_bits.https.any.worker.html": [
"X25519 key derivation checks for all-zero value result with a key of order 0",
"X25519 key derivation checks for all-zero value result with a key of order 1",
"X25519 key derivation checks for all-zero value result with a key of order 8",
"X25519 key derivation checks for all-zero value result with a key of order p-1 (order 2)",
"X25519 key derivation checks for all-zero value result with a key of order p (=0, order 4)",
"X25519 key derivation checks for all-zero value result with a key of order p+1 (=1, order 1)",
"X448 key derivation checks for all-zero value result with a key of order 0",
"X448 key derivation checks for all-zero value result with a key of order 1",
"X448 key derivation checks for all-zero value result with a key of order p-1 (order 2)",
"X448 key derivation checks for all-zero value result with a key of order p (=0, order 4)",
"X448 key derivation checks for all-zero value result with a key of order p+1 (=1, order 1)",
"X25519 good parameters",
"X25519 mixed case parameters",
"X25519 with null length",
"X25519 short result",
"X25519 non-multiple of 8 bits",
"X25519 mismatched algorithms",
"X25519 no deriveBits usage for base key",
"X448 good parameters",
"X448 mixed case parameters",
"X448 with null length",
"X448 short result",
"X448 non-multiple of 8 bits",
"X448 mismatched algorithms",
"X448 no deriveBits usage for base key",
"X448 base key is not a private key",
"X448 public property value is a private key",
"X448 public property value is a secret key",
"X448 asking for too many bits"
],
"cfrg_curves_keys.https.any.html": [
"Key derivation using a X25519 generated keys.",
"Key derivation using a X448 generated keys.",
"X25519 good parameters",
"X25519 mixed case parameters",
"X25519 mismatched algorithms",
"X448 good parameters",
"X448 mixed case parameters",
"X448 mismatched algorithms",
"X448 no deriveKey usage for base key",
"X448 base key is not a private key",
"X448 public property value is a private key",
"X448 public property value is a secret key"
],
"cfrg_curves_keys.https.any.worker.html": [
"Key derivation using a X25519 generated keys.",
"Key derivation using a X448 generated keys.",
"X25519 good parameters",
"X25519 mixed case parameters",
"X25519 mismatched algorithms",
"X448 good parameters",
"X448 mixed case parameters",
"X448 mismatched algorithms",
"X448 no deriveKey usage for base key",
"X448 base key is not a private key",
"X448 public property value is a private key",
"X448 public property value is a secret key"
]
},
"digest": {
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"digest.https.any.html": true,
"digest.https.any.worker.html": true
},
"encrypt_decrypt": {
"aes_cbc.https.any.html": true,
"aes_cbc.https.any.worker.html": true,
"aes_ctr.https.any.html": true,
"aes_ctr.https.any.worker.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"aes_gcm.https.any.html": [
"AES-GCM 128-bit key, 32-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 64-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 96-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 104-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 112-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 120-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 32-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 64-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 96-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 104-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 112-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 120-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 32-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 64-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 96-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 104-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 112-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 120-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 96-bit iv decryption with altered ciphertext"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"aes_gcm.https.any.worker.html": [
"AES-GCM 128-bit key, 32-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 64-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 96-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 104-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 112-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 120-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 32-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 64-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 96-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 104-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 112-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, 120-bit tag, 96-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 32-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 64-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 96-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 104-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 112-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, 120-bit tag, 96-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 96-bit iv decryption",
"AES-GCM 128-bit key, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 120-bit tag, 96-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 96-bit iv decryption with altered ciphertext"
],
"rsa_oaep.https.any.html": true,
"rsa_oaep.https.any.worker.html": true,
"aes_gcm_256_iv.https.any.html": [
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv decryption with altered ciphertext"
],
"aes_gcm_256_iv.https.any.worker.html": [
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv",
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv with altered plaintext",
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv decryption",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv decryption",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv decryption",
"AES-GCM 128-bit key, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 128-bit key, no additional data, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 192-bit key, no additional data, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 32-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 64-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 96-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 104-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 112-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 120-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, 128-bit tag, 256-bit iv decryption with altered ciphertext",
"AES-GCM 256-bit key, no additional data, 128-bit tag, 256-bit iv decryption with altered ciphertext"
]
},
"generateKey": {
"failures_AES-CBC.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_AES-CBC.https.any.worker.html": true,
"failures_AES-CTR.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_AES-CTR.https.any.worker.html": true,
"failures_AES-GCM.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_AES-GCM.https.any.worker.html": true,
"failures_AES-KW.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_AES-KW.https.any.worker.html": true,
"failures_ECDH.https.any.html": [
"Empty usages: generateKey({name: ECDH, namedCurve: P-521}, false, [])",
"Empty usages: generateKey({name: ECDH, namedCurve: P-521}, true, [])"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_ECDH.https.any.worker.html": [
"Empty usages: generateKey({name: ECDH, namedCurve: P-521}, false, [])",
"Empty usages: generateKey({name: ECDH, namedCurve: P-521}, true, [])"
],
"failures_ECDSA.https.any.html": [
"Empty usages: generateKey({name: ECDSA, namedCurve: P-521}, false, [])",
"Empty usages: generateKey({name: ECDSA, namedCurve: P-521}, true, [])"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_ECDSA.https.any.worker.html": [
"Empty usages: generateKey({name: ECDSA, namedCurve: P-521}, false, [])",
"Empty usages: generateKey({name: ECDSA, namedCurve: P-521}, true, [])"
],
"failures_HMAC.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_HMAC.https.any.worker.html": true,
"failures_RSA-OAEP.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_RSA-OAEP.https.any.worker.html": true,
"failures_RSA-PSS.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_RSA-PSS.https.any.worker.html": true,
"failures_RSASSA-PKCS1-v1_5.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"failures_RSASSA-PKCS1-v1_5.https.any.worker.html": true,
"successes_AES-CBC.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_AES-CBC.https.any.worker.html": true,
"successes_AES-CTR.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_AES-CTR.https.any.worker.html": true,
"successes_AES-GCM.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_AES-GCM.https.any.worker.html": true,
"successes_AES-KW.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_AES-KW.https.any.worker.html": true,
"successes_HMAC.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_HMAC.https.any.worker.html": true,
"successes_ECDH.https.any.html": [
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveBits])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveBits])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_ECDH.https.any.worker.html": [
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveBits])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveBits])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, false, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: ECDH, namedCurve: P-521}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, false, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: ecdh, namedCurve: P-521}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, false, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])",
"Success: generateKey({name: Ecdh, namedCurve: P-521}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits])"
],
"successes_ECDSA.https.any.html": [
"Success: generateKey({name: ECDSA, namedCurve: P-521}, false, [sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, true, [sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, false, [verify, sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, true, [verify, sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, false, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, true, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, false, [sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, true, [sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, false, [verify, sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, true, [verify, sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, false, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, true, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, false, [sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, true, [sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, false, [verify, sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, true, [verify, sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, false, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, true, [sign, verify, sign, sign, verify])"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"successes_ECDSA.https.any.worker.html": [
"Success: generateKey({name: ECDSA, namedCurve: P-521}, false, [sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, true, [sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, false, [verify, sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, true, [verify, sign])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, false, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: ECDSA, namedCurve: P-521}, true, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, false, [sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, true, [sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, false, [verify, sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, true, [verify, sign])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, false, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: ecdsa, namedCurve: P-521}, true, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, false, [sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, true, [sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, false, [verify, sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, true, [verify, sign])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, false, [sign, verify, sign, sign, verify])",
"Success: generateKey({name: Ecdsa, namedCurve: P-521}, true, [sign, verify, sign, sign, verify])"
],
"successes_RSA-OAEP.https.any.html?1-10": true,
"successes_RSA-OAEP.https.any.html?101-110": true,
"successes_RSA-OAEP.https.any.html?11-20": true,
"successes_RSA-OAEP.https.any.html?111-120": true,
"successes_RSA-OAEP.https.any.html?121-130": true,
"successes_RSA-OAEP.https.any.html?131-140": true,
"successes_RSA-OAEP.https.any.html?141-150": true,
"successes_RSA-OAEP.https.any.html?151-last": true,
"successes_RSA-OAEP.https.any.html?21-30": true,
"successes_RSA-OAEP.https.any.html?31-40": true,
"successes_RSA-OAEP.https.any.html?41-50": true,
"successes_RSA-OAEP.https.any.html?51-60": true,
"successes_RSA-OAEP.https.any.html?61-70": true,
"successes_RSA-OAEP.https.any.html?71-80": true,
"successes_RSA-OAEP.https.any.html?81-90": true,
"successes_RSA-OAEP.https.any.html?91-100": true,
"successes_RSA-OAEP.https.any.worker.html?1-10": true,
"successes_RSA-OAEP.https.any.worker.html?101-110": true,
"successes_RSA-OAEP.https.any.worker.html?11-20": true,
"successes_RSA-OAEP.https.any.worker.html?111-120": true,
"successes_RSA-OAEP.https.any.worker.html?121-130": true,
"successes_RSA-OAEP.https.any.worker.html?131-140": true,
"successes_RSA-OAEP.https.any.worker.html?141-150": true,
"successes_RSA-OAEP.https.any.worker.html?151-last": true,
"successes_RSA-OAEP.https.any.worker.html?21-30": true,
"successes_RSA-OAEP.https.any.worker.html?31-40": true,
"successes_RSA-OAEP.https.any.worker.html?41-50": true,
"successes_RSA-OAEP.https.any.worker.html?51-60": true,
"successes_RSA-OAEP.https.any.worker.html?61-70": true,
"successes_RSA-OAEP.https.any.worker.html?71-80": true,
"successes_RSA-OAEP.https.any.worker.html?81-90": true,
"successes_RSA-OAEP.https.any.worker.html?91-100": true,
"successes_RSA-PSS.https.any.html?1-10": true,
"successes_RSA-PSS.https.any.html?11-20": true,
"successes_RSA-PSS.https.any.html?21-30": true,
"successes_RSA-PSS.https.any.html?31-last": true,
"successes_RSA-PSS.https.any.worker.html?1-10": true,
"successes_RSA-PSS.https.any.worker.html?11-20": true,
"successes_RSA-PSS.https.any.worker.html?21-30": true,
"successes_RSA-PSS.https.any.worker.html?31-last": true,
"successes_RSASSA-PKCS1-v1_5.https.any.html?1-10": true,
"successes_RSASSA-PKCS1-v1_5.https.any.html?11-20": true,
"successes_RSASSA-PKCS1-v1_5.https.any.html?21-30": true,
"successes_RSASSA-PKCS1-v1_5.https.any.html?31-last": true,
"successes_RSASSA-PKCS1-v1_5.https.any.worker.html?1-10": true,
"successes_RSASSA-PKCS1-v1_5.https.any.worker.html?11-20": true,
"successes_RSASSA-PKCS1-v1_5.https.any.worker.html?21-30": true,
2022-09-22 05:07:50 -04:00
"successes_RSASSA-PKCS1-v1_5.https.any.worker.html?31-last": true,
"failures_Ed25519.https.any.html": true,
"failures_Ed25519.https.any.worker.html": true,
2022-09-22 05:07:50 -04:00
"failures_Ed448.https.any.html": [
"Bad usages: generateKey({name: Ed448}, true, [encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [deriveBits])",
"Bad usages: generateKey({name: Ed448}, true, [sign, deriveBits])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, deriveBits])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, deriveBits])",
"Empty usages: generateKey({name: Ed448}, false, [])",
"Empty usages: generateKey({name: Ed448}, true, [])"
],
"failures_Ed448.https.any.worker.html": [
"Bad usages: generateKey({name: Ed448}, true, [encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, encrypt])",
"Bad usages: generateKey({name: Ed448}, true, [decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, decrypt])",
"Bad usages: generateKey({name: Ed448}, true, [wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, wrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, unwrapKey])",
"Bad usages: generateKey({name: Ed448}, true, [deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, deriveKey])",
"Bad usages: generateKey({name: Ed448}, true, [deriveBits])",
"Bad usages: generateKey({name: Ed448}, true, [sign, deriveBits])",
"Bad usages: generateKey({name: Ed448}, true, [verify, sign, deriveBits])",
"Bad usages: generateKey({name: Ed448}, true, [sign, verify, sign, sign, verify, deriveBits])",
"Empty usages: generateKey({name: Ed448}, false, [])",
"Empty usages: generateKey({name: Ed448}, true, [])"
],
"failures_X25519.https.any.html": true,
"failures_X25519.https.any.worker.html": true,
2022-09-22 05:07:50 -04:00
"failures_X448.https.any.html": [
"Bad usages: generateKey({name: X448}, true, [encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, encrypt])",
"Bad usages: generateKey({name: X448}, true, [decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, decrypt])",
"Bad usages: generateKey({name: X448}, true, [sign])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, sign])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, sign])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, sign])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, sign])",
"Bad usages: generateKey({name: X448}, true, [verify])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, verify])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, verify])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, verify])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, verify])",
"Bad usages: generateKey({name: X448}, true, [wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, unwrapKey])",
"Empty usages: generateKey({name: X448}, false, [])",
"Empty usages: generateKey({name: X448}, true, [])"
],
"failures_X448.https.any.worker.html": [
"Bad usages: generateKey({name: X448}, true, [encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, encrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, encrypt])",
"Bad usages: generateKey({name: X448}, true, [decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, decrypt])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, decrypt])",
"Bad usages: generateKey({name: X448}, true, [sign])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, sign])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, sign])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, sign])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, sign])",
"Bad usages: generateKey({name: X448}, true, [verify])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, verify])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, verify])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, verify])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, verify])",
"Bad usages: generateKey({name: X448}, true, [wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, wrapKey])",
"Bad usages: generateKey({name: X448}, true, [unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, deriveKey, unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveBits, unwrapKey])",
"Bad usages: generateKey({name: X448}, true, [deriveKey, deriveBits, deriveKey, deriveBits, deriveKey, deriveBits, unwrapKey])",
"Empty usages: generateKey({name: X448}, false, [])",
"Empty usages: generateKey({name: X448}, true, [])"
],
"successes_Ed25519.https.any.html": true,
"successes_Ed25519.https.any.worker.html": true,
2022-09-22 05:07:50 -04:00
"successes_Ed448.https.any.html": false,
"successes_Ed448.https.any.worker.html": false,
"successes_X25519.https.any.html": true,
"successes_X25519.https.any.worker.html": true,
2022-09-22 05:07:50 -04:00
"successes_X448.https.any.html": false,
"successes_X448.https.any.worker.html": false
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
},
"historical.any.html": false,
"historical.any.worker.html": false,
"idlharness.https.any.html": [
"Window interface: attribute crypto"
],
"idlharness.https.any.worker.html": [
"WorkerGlobalScope interface: attribute crypto"
],
"import_export": {
"ec_importKey.https.any.html": [
"Good parameters: P-256 bits (spki, buffer(59, compressed), {name: ECDSA, namedCurve: P-256}, true, [])",
"Good parameters: P-256 bits (raw, buffer(33, compressed), {name: ECDSA, namedCurve: P-256}, true, [])",
"Good parameters: P-384 bits (spki, buffer(72, compressed), {name: ECDSA, namedCurve: P-384}, true, [])",
"Good parameters: P-384 bits (raw, buffer(49, compressed), {name: ECDSA, namedCurve: P-384}, true, [])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDSA, namedCurve: P-521}, true, [sign])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDSA, namedCurve: P-521}, true, [sign])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDSA, namedCurve: P-521}, false, [sign])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDSA, namedCurve: P-521}, false, [sign])",
"Good parameters: P-256 bits (spki, buffer(59, compressed), {name: ECDH, namedCurve: P-256}, true, [])",
"Good parameters: P-256 bits (raw, buffer(33, compressed), {name: ECDH, namedCurve: P-256}, true, [])",
"Good parameters: P-384 bits (spki, buffer(72, compressed), {name: ECDH, namedCurve: P-384}, true, [])",
"Good parameters: P-384 bits (raw, buffer(49, compressed), {name: ECDH, namedCurve: P-384}, true, [])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, true, [deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, true, [deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, true, [deriveBits])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, true, [deriveBits])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, false, [deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, false, [deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, false, [deriveBits])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, false, [deriveBits])"
],
"ec_importKey.https.any.worker.html": [
"Good parameters: P-256 bits (spki, buffer(59, compressed), {name: ECDSA, namedCurve: P-256}, true, [])",
"Good parameters: P-256 bits (raw, buffer(33, compressed), {name: ECDSA, namedCurve: P-256}, true, [])",
"Good parameters: P-384 bits (spki, buffer(72, compressed), {name: ECDSA, namedCurve: P-384}, true, [])",
"Good parameters: P-384 bits (raw, buffer(49, compressed), {name: ECDSA, namedCurve: P-384}, true, [])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDSA, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDSA, namedCurve: P-521}, true, [sign])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDSA, namedCurve: P-521}, true, [sign])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDSA, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDSA, namedCurve: P-521}, false, [sign])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDSA, namedCurve: P-521}, false, [sign])",
"Good parameters: P-256 bits (spki, buffer(59, compressed), {name: ECDH, namedCurve: P-256}, true, [])",
"Good parameters: P-256 bits (raw, buffer(33, compressed), {name: ECDH, namedCurve: P-256}, true, [])",
"Good parameters: P-384 bits (spki, buffer(72, compressed), {name: ECDH, namedCurve: P-384}, true, [])",
"Good parameters: P-384 bits (raw, buffer(49, compressed), {name: ECDH, namedCurve: P-384}, true, [])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDH, namedCurve: P-521}, true, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, true, [deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, true, [deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, true, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, true, [deriveBits])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, true, [deriveBits])",
"Good parameters: P-521 bits (spki, buffer(158), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (spki, buffer(90, compressed), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(133), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (raw, buffer(67, compressed), {name: ECDH, namedCurve: P-521}, false, [])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, false, [deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, false, [deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, false, [deriveBits, deriveKey])",
"Good parameters: P-521 bits (pkcs8, buffer(241), {name: ECDH, namedCurve: P-521}, false, [deriveBits])",
"Good parameters: P-521 bits (jwk, object(kty, crv, x, y, d), {name: ECDH, namedCurve: P-521}, false, [deriveBits])"
],
"rsa_importKey.https.any.html": true,
"rsa_importKey.https.any.worker.html": true,
"symmetric_importKey.https.any.html": true,
2022-09-22 05:07:50 -04:00
"symmetric_importKey.https.any.worker.html": true,
"okp_importKey.https.any.html": [
"Good parameters: Ed448 bits (spki, buffer(69), {name: Ed448}, true, [])",
"Good parameters: Ed448 bits (jwk, object(kty, crv, x), {name: Ed448}, true, [])",
"Good parameters: Ed448 bits (raw, buffer(57), {name: Ed448}, true, [])",
"Good parameters: Ed448 bits (pkcs8, buffer(73), {name: Ed448}, true, [sign])",
"Good parameters: Ed448 bits (jwk, object(crv, d, x, kty), {name: Ed448}, true, [sign])",
"Good parameters: Ed448 bits (spki, buffer(69), {name: Ed448}, false, [])",
"Good parameters: Ed448 bits (jwk, object(kty, crv, x), {name: Ed448}, false, [])",
"Good parameters: Ed448 bits (raw, buffer(57), {name: Ed448}, false, [])",
"Good parameters: Ed448 bits (pkcs8, buffer(73), {name: Ed448}, false, [sign])",
"Good parameters: Ed448 bits (jwk, object(crv, d, x, kty), {name: Ed448}, false, [sign])",
"Good parameters: X25519 bits (jwk, object(crv, d, x, kty), {name: X25519}, true, [deriveKey])",
"Good parameters: X25519 bits (jwk, object(crv, d, x, kty), {name: X25519}, true, [deriveBits, deriveKey])",
"Good parameters: X25519 bits (jwk, object(crv, d, x, kty), {name: X25519}, true, [deriveBits])",
"Good parameters: X448 bits (spki, buffer(68), {name: X448}, true, [])",
"Good parameters: X448 bits (jwk, object(kty, crv, x), {name: X448}, true, [])",
"Good parameters: X448 bits (raw, buffer(56), {name: X448}, true, [])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, true, [deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, true, [deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, true, [deriveBits, deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, true, [deriveBits, deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, true, [deriveBits])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, true, [deriveBits])",
"Good parameters: X448 bits (spki, buffer(68), {name: X448}, false, [])",
"Good parameters: X448 bits (jwk, object(kty, crv, x), {name: X448}, false, [])",
"Good parameters: X448 bits (raw, buffer(56), {name: X448}, false, [])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, false, [deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, false, [deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, false, [deriveBits, deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, false, [deriveBits, deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, false, [deriveBits])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, false, [deriveBits])"
],
"okp_importKey.https.any.worker.html": [
"Good parameters: Ed448 bits (spki, buffer(69), {name: Ed448}, true, [])",
"Good parameters: Ed448 bits (jwk, object(kty, crv, x), {name: Ed448}, true, [])",
"Good parameters: Ed448 bits (raw, buffer(57), {name: Ed448}, true, [])",
"Good parameters: Ed448 bits (pkcs8, buffer(73), {name: Ed448}, true, [sign])",
"Good parameters: Ed448 bits (jwk, object(crv, d, x, kty), {name: Ed448}, true, [sign])",
"Good parameters: Ed448 bits (spki, buffer(69), {name: Ed448}, false, [])",
"Good parameters: Ed448 bits (jwk, object(kty, crv, x), {name: Ed448}, false, [])",
"Good parameters: Ed448 bits (raw, buffer(57), {name: Ed448}, false, [])",
"Good parameters: Ed448 bits (pkcs8, buffer(73), {name: Ed448}, false, [sign])",
"Good parameters: Ed448 bits (jwk, object(crv, d, x, kty), {name: Ed448}, false, [sign])",
"Good parameters: X25519 bits (jwk, object(crv, d, x, kty), {name: X25519}, true, [deriveKey])",
"Good parameters: X25519 bits (jwk, object(crv, d, x, kty), {name: X25519}, true, [deriveBits, deriveKey])",
"Good parameters: X25519 bits (jwk, object(crv, d, x, kty), {name: X25519}, true, [deriveBits])",
"Good parameters: X448 bits (spki, buffer(68), {name: X448}, true, [])",
"Good parameters: X448 bits (jwk, object(kty, crv, x), {name: X448}, true, [])",
"Good parameters: X448 bits (raw, buffer(56), {name: X448}, true, [])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, true, [deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, true, [deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, true, [deriveBits, deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, true, [deriveBits, deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, true, [deriveBits])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, true, [deriveBits])",
"Good parameters: X448 bits (spki, buffer(68), {name: X448}, false, [])",
"Good parameters: X448 bits (jwk, object(kty, crv, x), {name: X448}, false, [])",
"Good parameters: X448 bits (raw, buffer(56), {name: X448}, false, [])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, false, [deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, false, [deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, false, [deriveBits, deriveKey])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, false, [deriveBits, deriveKey])",
"Good parameters: X448 bits (pkcs8, buffer(72), {name: X448}, false, [deriveBits])",
"Good parameters: X448 bits (jwk, object(crv, d, x, kty), {name: X448}, false, [deriveBits])"
],
"okp_importKey_failures_Ed25519.https.any.html": false,
"okp_importKey_failures_Ed25519.https.any.worker.html": false,
"okp_importKey_failures_Ed448.https.any.html": false,
"okp_importKey_failures_Ed448.https.any.worker.html": false,
"okp_importKey_failures_X25519.https.any.html": false,
"okp_importKey_failures_X25519.https.any.worker.html": false,
"okp_importKey_failures_X448.https.any.html": false,
"okp_importKey_failures_X448.https.any.worker.html": false
},
"randomUUID.https.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"randomUUID.https.any.worker.html": true,
"sign_verify": {
"ecdsa.https.any.html": [
"ECDSA P-256 with SHA-1 verification",
"ECDSA P-256 with SHA-384 verification",
"ECDSA P-256 with SHA-512 verification",
"ECDSA P-384 with SHA-1 verification",
"ECDSA P-384 with SHA-256 verification",
"ECDSA P-384 with SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification",
"ECDSA P-256 with SHA-1 verification with altered signature after call",
"ECDSA P-256 with SHA-384 verification with altered signature after call",
"ECDSA P-256 with SHA-512 verification with altered signature after call",
"ECDSA P-384 with SHA-1 verification with altered signature after call",
"ECDSA P-384 with SHA-256 verification with altered signature after call",
"ECDSA P-384 with SHA-512 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification with altered signature after call",
"ECDSA P-256 with SHA-1 with altered plaintext after call",
"ECDSA P-256 with SHA-384 with altered plaintext after call",
"ECDSA P-256 with SHA-512 with altered plaintext after call",
"ECDSA P-384 with SHA-1 with altered plaintext after call",
"ECDSA P-384 with SHA-256 with altered plaintext after call",
"ECDSA P-384 with SHA-512 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-1 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-256 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-384 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-512 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-1 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-256 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-384 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-512 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-1 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-256 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-384 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-512 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-1 no verify usage",
"importVectorKeys step: ECDSA P-521 with SHA-256 no verify usage",
"importVectorKeys step: ECDSA P-521 with SHA-384 no verify usage",
"importVectorKeys step: ECDSA P-521 with SHA-512 no verify usage",
"ECDSA P-256 with SHA-1 round trip",
"ECDSA P-256 with SHA-384 round trip",
"ECDSA P-256 with SHA-512 round trip",
"ECDSA P-384 with SHA-1 round trip",
"ECDSA P-384 with SHA-256 round trip",
"ECDSA P-384 with SHA-512 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-1 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-256 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-384 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-512 round trip",
"ECDSA P-256 with SHA-1 verification failure due to altered signature",
"ECDSA P-256 with SHA-384 verification failure due to altered signature",
"ECDSA P-256 with SHA-512 verification failure due to altered signature",
"ECDSA P-384 with SHA-1 verification failure due to altered signature",
"ECDSA P-384 with SHA-256 verification failure due to altered signature",
"ECDSA P-384 with SHA-512 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to altered signature",
"ECDSA P-256 with SHA-256 verification failure due to wrong hash",
"ECDSA P-256 with SHA-384 verification failure due to wrong hash",
"ECDSA P-256 with SHA-512 verification failure due to wrong hash",
"ECDSA P-384 with SHA-1 verification failure due to wrong hash",
"ECDSA P-384 with SHA-256 verification failure due to wrong hash",
"ECDSA P-384 with SHA-384 verification failure due to wrong hash",
"ECDSA P-384 with SHA-512 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to bad hash name",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to bad hash name",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to bad hash name",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to bad hash name",
"ECDSA P-256 with SHA-1 verification failure due to shortened signature",
"ECDSA P-256 with SHA-384 verification failure due to shortened signature",
"ECDSA P-256 with SHA-512 verification failure due to shortened signature",
"ECDSA P-384 with SHA-1 verification failure due to shortened signature",
"ECDSA P-384 with SHA-256 verification failure due to shortened signature",
"ECDSA P-384 with SHA-512 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to shortened signature",
"ECDSA P-256 with SHA-1 verification failure due to altered plaintext",
"ECDSA P-256 with SHA-384 verification failure due to altered plaintext",
"ECDSA P-256 with SHA-512 verification failure due to altered plaintext",
"ECDSA P-384 with SHA-1 verification failure due to altered plaintext",
"ECDSA P-384 with SHA-256 verification failure due to altered plaintext",
"ECDSA P-384 with SHA-512 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to altered plaintext",
"ECDSA P-256 with SHA-1 - The signature was truncated by 1 byte verification",
"ECDSA P-256 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-384 verification",
"ECDSA P-256 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification",
"ECDSA P-256 with SHA-1 - Signature has excess padding verification",
"ECDSA P-256 with SHA-1 - The signature is empty verification",
"ECDSA P-256 with SHA-1 - The signature is all zeroes verification",
"ECDSA P-256 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification",
"ECDSA P-256 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-384 verification",
"ECDSA P-256 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification",
"ECDSA P-256 with SHA-384 - The signature was truncated by 1 byte verification",
"ECDSA P-256 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification",
"ECDSA P-256 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification",
"ECDSA P-256 with SHA-384 - Signature has excess padding verification",
"ECDSA P-256 with SHA-384 - The signature is empty verification",
"ECDSA P-256 with SHA-384 - The signature is all zeroes verification",
"ECDSA P-256 with SHA-512 - The signature was truncated by 1 byte verification",
"ECDSA P-256 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification",
"ECDSA P-256 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-384 verification",
"ECDSA P-256 with SHA-512 - Signature has excess padding verification",
"ECDSA P-256 with SHA-512 - The signature is empty verification",
"ECDSA P-256 with SHA-512 - The signature is all zeroes verification",
"ECDSA P-384 with SHA-1 - The signature was truncated by 1 byte verification",
"ECDSA P-384 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-256 verification",
"ECDSA P-384 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification",
"ECDSA P-384 with SHA-1 - Signature has excess padding verification",
"ECDSA P-384 with SHA-1 - The signature is empty verification",
"ECDSA P-384 with SHA-1 - The signature is all zeroes verification",
"ECDSA P-384 with SHA-256 - The signature was truncated by 1 byte verification",
"ECDSA P-384 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification",
"ECDSA P-384 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification",
"ECDSA P-384 with SHA-256 - Signature has excess padding verification",
"ECDSA P-384 with SHA-256 - The signature is empty verification",
"ECDSA P-384 with SHA-256 - The signature is all zeroes verification",
"ECDSA P-384 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification",
"ECDSA P-384 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-256 verification",
"ECDSA P-384 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification",
"ECDSA P-384 with SHA-512 - The signature was truncated by 1 byte verification",
"ECDSA P-384 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification",
"ECDSA P-384 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-256 verification",
"ECDSA P-384 with SHA-512 - Signature has excess padding verification",
"ECDSA P-384 with SHA-512 - The signature is empty verification",
"ECDSA P-384 with SHA-512 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-256 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-384 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-512 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-1 verifying with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-256 verifying with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-384 verifying with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-512 verifying with wrong algorithm name"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"ecdsa.https.any.worker.html": [
"ECDSA P-256 with SHA-1 verification",
"ECDSA P-256 with SHA-384 verification",
"ECDSA P-256 with SHA-512 verification",
"ECDSA P-384 with SHA-1 verification",
"ECDSA P-384 with SHA-256 verification",
"ECDSA P-384 with SHA-512 verification",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification",
"ECDSA P-256 with SHA-1 verification with altered signature after call",
"ECDSA P-256 with SHA-384 verification with altered signature after call",
"ECDSA P-256 with SHA-512 verification with altered signature after call",
"ECDSA P-384 with SHA-1 verification with altered signature after call",
"ECDSA P-384 with SHA-256 verification with altered signature after call",
"ECDSA P-384 with SHA-512 verification with altered signature after call",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification with altered signature after call",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification with altered signature after call",
"ECDSA P-256 with SHA-1 with altered plaintext after call",
"ECDSA P-256 with SHA-384 with altered plaintext after call",
"ECDSA P-256 with SHA-512 with altered plaintext after call",
"ECDSA P-384 with SHA-1 with altered plaintext after call",
"ECDSA P-384 with SHA-256 with altered plaintext after call",
"ECDSA P-384 with SHA-512 with altered plaintext after call",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-256 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-384 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-512 with altered plaintext after call",
"importVectorKeys step: ECDSA P-521 with SHA-1 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-256 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-384 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-512 using privateKey to verify",
"importVectorKeys step: ECDSA P-521 with SHA-1 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-256 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-384 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-512 using publicKey to sign",
"importVectorKeys step: ECDSA P-521 with SHA-1 no verify usage",
"importVectorKeys step: ECDSA P-521 with SHA-256 no verify usage",
"importVectorKeys step: ECDSA P-521 with SHA-384 no verify usage",
"importVectorKeys step: ECDSA P-521 with SHA-512 no verify usage",
"ECDSA P-256 with SHA-1 round trip",
"ECDSA P-256 with SHA-384 round trip",
"ECDSA P-256 with SHA-512 round trip",
"ECDSA P-384 with SHA-1 round trip",
"ECDSA P-384 with SHA-256 round trip",
"ECDSA P-384 with SHA-512 round trip",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-256 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-384 round trip",
"importVectorKeys step: ECDSA P-521 with SHA-512 round trip",
"ECDSA P-256 with SHA-1 verification failure due to altered signature",
"ECDSA P-256 with SHA-384 verification failure due to altered signature",
"ECDSA P-256 with SHA-512 verification failure due to altered signature",
"ECDSA P-384 with SHA-1 verification failure due to altered signature",
"ECDSA P-384 with SHA-256 verification failure due to altered signature",
"ECDSA P-384 with SHA-512 verification failure due to altered signature",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to altered signature",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to altered signature",
"ECDSA P-256 with SHA-256 verification failure due to wrong hash",
"ECDSA P-256 with SHA-384 verification failure due to wrong hash",
"ECDSA P-256 with SHA-512 verification failure due to wrong hash",
"ECDSA P-384 with SHA-1 verification failure due to wrong hash",
"ECDSA P-384 with SHA-256 verification failure due to wrong hash",
"ECDSA P-384 with SHA-384 verification failure due to wrong hash",
"ECDSA P-384 with SHA-512 verification failure due to wrong hash",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to wrong hash",
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to bad hash name",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to bad hash name",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to bad hash name",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to bad hash name",
"ECDSA P-256 with SHA-1 verification failure due to shortened signature",
"ECDSA P-256 with SHA-384 verification failure due to shortened signature",
"ECDSA P-256 with SHA-512 verification failure due to shortened signature",
"ECDSA P-384 with SHA-1 verification failure due to shortened signature",
"ECDSA P-384 with SHA-256 verification failure due to shortened signature",
"ECDSA P-384 with SHA-512 verification failure due to shortened signature",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to shortened signature",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to shortened signature",
"ECDSA P-256 with SHA-1 verification failure due to altered plaintext",
"ECDSA P-256 with SHA-384 verification failure due to altered plaintext",
"ECDSA P-256 with SHA-512 verification failure due to altered plaintext",
"ECDSA P-384 with SHA-1 verification failure due to altered plaintext",
"ECDSA P-384 with SHA-256 verification failure due to altered plaintext",
"ECDSA P-384 with SHA-512 verification failure due to altered plaintext",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-256 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-384 verification failure due to altered plaintext",
"importVectorKeys step: ECDSA P-521 with SHA-512 verification failure due to altered plaintext",
"ECDSA P-256 with SHA-1 - The signature was truncated by 1 byte verification",
"ECDSA P-256 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-384 verification",
"ECDSA P-256 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification",
"ECDSA P-256 with SHA-1 - Signature has excess padding verification",
"ECDSA P-256 with SHA-1 - The signature is empty verification",
"ECDSA P-256 with SHA-1 - The signature is all zeroes verification",
"ECDSA P-256 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification",
"ECDSA P-256 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-384 verification",
"ECDSA P-256 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification",
"ECDSA P-256 with SHA-384 - The signature was truncated by 1 byte verification",
"ECDSA P-256 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification",
"ECDSA P-256 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification",
"ECDSA P-256 with SHA-384 - Signature has excess padding verification",
"ECDSA P-256 with SHA-384 - The signature is empty verification",
"ECDSA P-256 with SHA-384 - The signature is all zeroes verification",
"ECDSA P-256 with SHA-512 - The signature was truncated by 1 byte verification",
"ECDSA P-256 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification",
"ECDSA P-256 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-384 verification",
"ECDSA P-256 with SHA-512 - Signature has excess padding verification",
"ECDSA P-256 with SHA-512 - The signature is empty verification",
"ECDSA P-256 with SHA-512 - The signature is all zeroes verification",
"ECDSA P-384 with SHA-1 - The signature was truncated by 1 byte verification",
"ECDSA P-384 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-256 verification",
"ECDSA P-384 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification",
"ECDSA P-384 with SHA-1 - Signature has excess padding verification",
"ECDSA P-384 with SHA-1 - The signature is empty verification",
"ECDSA P-384 with SHA-1 - The signature is all zeroes verification",
"ECDSA P-384 with SHA-256 - The signature was truncated by 1 byte verification",
"ECDSA P-384 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification",
"ECDSA P-384 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification",
"ECDSA P-384 with SHA-256 - Signature has excess padding verification",
"ECDSA P-384 with SHA-256 - The signature is empty verification",
"ECDSA P-384 with SHA-256 - The signature is all zeroes verification",
"ECDSA P-384 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification",
"ECDSA P-384 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-256 verification",
"ECDSA P-384 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification",
"ECDSA P-384 with SHA-512 - The signature was truncated by 1 byte verification",
"ECDSA P-384 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification",
"ECDSA P-384 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-256 verification",
"ECDSA P-384 with SHA-512 - Signature has excess padding verification",
"ECDSA P-384 with SHA-512 - The signature is empty verification",
"ECDSA P-384 with SHA-512 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature was made using SHA-1, however verification is being done using SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-1 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature was made using SHA-256, however verification is being done using SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-256 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature was made using SHA-384, however verification is being done using SHA-512 verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-384 - The signature is all zeroes verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was truncated by 1 byte verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-1 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-256 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature was made using SHA-512, however verification is being done using SHA-384 verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - Signature has excess padding verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature is empty verification",
"importVectorKeys step: ECDSA P-521 with SHA-512 - The signature is all zeroes verification",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"importVectorKeys step: ECDSA P-521 with SHA-1 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-256 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-384 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-512 signing with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-1 verifying with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-256 verifying with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-384 verifying with wrong algorithm name",
"importVectorKeys step: ECDSA P-521 with SHA-512 verifying with wrong algorithm name"
],
"hmac.https.any.html": true,
"hmac.https.any.worker.html": true,
"rsa_pkcs.https.any.html": true,
"rsa_pkcs.https.any.worker.html": true,
"rsa_pss.https.any.html": [
"RSA-PSS with SHA-1 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-256 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-384 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-512 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-1, salted verification failure with wrong saltLength",
"RSA-PSS with SHA-256, salted verification failure with wrong saltLength",
"RSA-PSS with SHA-384, salted verification failure with wrong saltLength",
"RSA-PSS with SHA-512, salted verification failure with wrong saltLength"
],
"rsa_pss.https.any.worker.html": [
"RSA-PSS with SHA-1 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-256 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-384 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-512 and no salt verification failure with wrong saltLength",
"RSA-PSS with SHA-1, salted verification failure with wrong saltLength",
"RSA-PSS with SHA-256, salted verification failure with wrong saltLength",
"RSA-PSS with SHA-384, salted verification failure with wrong saltLength",
"RSA-PSS with SHA-512, salted verification failure with wrong saltLength"
],
2022-09-22 05:07:50 -04:00
"eddsa.https.any.html": [
"Sign and verify using generated Ed448 keys.",
2022-09-22 05:07:50 -04:00
"importVectorKeys step: EdDSA Ed448 verification",
"importVectorKeys step: EdDSA Ed448 verification with altered signature after call",
"importVectorKeys step: EdDSA Ed448 with altered data after call",
"importVectorKeys step: EdDSA Ed448 using privateKey to verify",
"importVectorKeys step: EdDSA Ed448 using publicKey to sign",
"importVectorKeys step: EdDSA Ed448 no verify usage",
"importVectorKeys step: EdDSA Ed448 round trip",
"importVectorKeys step: EdDSA Ed448 verification failure due to altered signature",
"importVectorKeys step: EdDSA Ed448 verification failure due to shortened signature",
"importVectorKeys step: EdDSA Ed448 verification failure due to altered data",
"importVectorKeys step: EdDSA Ed448 signing with wrong algorithm name",
"importVectorKeys step: EdDSA Ed448 verifying with wrong algorithm name"
],
"eddsa.https.any.worker.html": [
"Sign and verify using generated Ed448 keys.",
2022-09-22 05:07:50 -04:00
"importVectorKeys step: EdDSA Ed448 verification",
"importVectorKeys step: EdDSA Ed448 verification with altered signature after call",
"importVectorKeys step: EdDSA Ed448 with altered data after call",
"importVectorKeys step: EdDSA Ed448 using privateKey to verify",
"importVectorKeys step: EdDSA Ed448 using publicKey to sign",
"importVectorKeys step: EdDSA Ed448 no verify usage",
"importVectorKeys step: EdDSA Ed448 round trip",
"importVectorKeys step: EdDSA Ed448 verification failure due to altered signature",
"importVectorKeys step: EdDSA Ed448 verification failure due to shortened signature",
"importVectorKeys step: EdDSA Ed448 verification failure due to altered data",
"importVectorKeys step: EdDSA Ed448 signing with wrong algorithm name",
"importVectorKeys step: EdDSA Ed448 verifying with wrong algorithm name"
]
},
"wrapKey_unwrapKey": {
"wrapKey_unwrapKey.https.any.worker.html": {
"ignore": true
},
"wrapKey_unwrapKey.https.any.html": {
"ignore": true
}
2022-09-22 05:07:50 -04:00
},
"algorithm-discards-context.https.window.html": false
},
"console": {
2021-05-09 10:32:30 -04:00
"console-is-a-namespace.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"console-is-a-namespace.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"console-label-conversion.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"console-label-conversion.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"console-namespace-object-class-string.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"console-namespace-object-class-string.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"console-tests-historical.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"console-tests-historical.any.worker.html": true,
"idlharness.any.html": true,
"idlharness.any.worker.html": true,
"idlharness-shadowrealm.window.html": false
},
"dom": {
"abort": {
"AbortSignal.any.html": true,
"AbortSignal.any.worker.html": true,
"event.any.html": true,
"event.any.worker.html": true,
"abort-signal-any.tentative.any.html": false,
"abort-signal-any.tentative.any.worker.html": false
},
"events": {
"AddEventListenerOptions-once.any.html": true,
"AddEventListenerOptions-once.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"AddEventListenerOptions-passive.any.html": [
"returnValue should be ignored if-and-only-if the passive option is true"
2021-09-25 09:27:34 -04:00
],
"AddEventListenerOptions-passive.any.worker.html": [
"returnValue should be ignored if-and-only-if the passive option is true"
2022-05-13 07:34:53 -04:00
],
"AddEventListenerOptions-signal.any.html": true,
"AddEventListenerOptions-signal.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"Event-isTrusted.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Event-isTrusted.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"EventTarget-add-remove-listener.any.html": true,
"EventTarget-add-remove-listener.any.worker.html": true,
"EventTarget-addEventListener.any.html": true,
"EventTarget-addEventListener.any.worker.html": true,
"EventTarget-removeEventListener.any.html": true,
"EventTarget-removeEventListener.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"EventTarget-constructible.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"EventTarget-constructible.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"Event-constructors.any.html": [
"Event constructors 3",
"Event constructors 4"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"Event-constructors.any.worker.html": [
"Event constructors 3",
"Event constructors 4"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"event-global.worker.html": true,
"Event-dispatch-listener-order.window.html": false,
"EventListener-addEventListener.sub.window.html": false,
"event-global-extra.window.html": false,
"event-global-set-before-handleEvent-lookup.window.html": false,
"legacy-pre-activation-behavior.window.html": false,
"relatedTarget.window.html": false
2022-04-18 15:17:19 -04:00
},
"idlharness-shadowrealm.window.html": false,
"idlharness.any.worker.html": [
"Event interface: attribute srcElement",
"Event interface: operation composedPath()",
"Event interface: constant NONE on interface object",
"Event interface: constant NONE on interface prototype object",
"Event interface: constant CAPTURING_PHASE on interface object",
"Event interface: constant CAPTURING_PHASE on interface prototype object",
"Event interface: constant AT_TARGET on interface object",
"Event interface: constant AT_TARGET on interface prototype object",
"Event interface: constant BUBBLING_PHASE on interface object",
"Event interface: constant BUBBLING_PHASE on interface prototype object",
"Event interface: operation stopPropagation()",
"Event interface: attribute cancelBubble",
"Event interface: operation stopImmediatePropagation()",
"Event interface: attribute returnValue",
"Event interface: operation preventDefault()",
"Event interface: attribute defaultPrevented",
"Event interface: operation initEvent(DOMString, optional boolean, optional boolean)",
"Event interface: new Event(\"foo\") must have own property \"isTrusted\"",
"Event interface: new Event(\"foo\") must inherit property \"initEvent(DOMString, optional boolean, optional boolean)\" with the proper type",
"Event interface: calling initEvent(DOMString, optional boolean, optional boolean) on new Event(\"foo\") with too few arguments must throw TypeError",
"CustomEvent interface: operation initCustomEvent(DOMString, optional boolean, optional boolean, optional any)",
"CustomEvent interface: new CustomEvent(\"foo\") must inherit property \"initCustomEvent(DOMString, optional boolean, optional boolean, optional any)\" with the proper type",
"CustomEvent interface: calling initCustomEvent(DOMString, optional boolean, optional boolean, optional any) on new CustomEvent(\"foo\") with too few arguments must throw TypeError",
"Event interface: new CustomEvent(\"foo\") must have own property \"isTrusted\"",
"Event interface: new CustomEvent(\"foo\") must inherit property \"initEvent(DOMString, optional boolean, optional boolean)\" with the proper type",
"Event interface: calling initEvent(DOMString, optional boolean, optional boolean) on new CustomEvent(\"foo\") with too few arguments must throw TypeError",
"EventTarget interface: operation addEventListener(DOMString, EventListener?, optional (AddEventListenerOptions or boolean))",
"EventTarget interface: operation removeEventListener(DOMString, EventListener?, optional (EventListenerOptions or boolean))",
"AbortController interface: operation abort(optional any)",
"AbortSignal interface: operation abort(optional any)",
"AbortSignal interface: operation timeout(unsigned long long)",
"AbortSignal interface: attribute onabort"
]
},
"encoding": {
2021-05-09 10:32:30 -04:00
"api-basics.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"api-basics.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"api-invalid-label.any.html?1-1000": true,
"api-invalid-label.any.html?1001-2000": true,
"api-invalid-label.any.html?2001-3000": true,
"api-invalid-label.any.html?3001-last": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"api-invalid-label.any.worker.html?1-1000": true,
"api-invalid-label.any.worker.html?1001-2000": true,
"api-invalid-label.any.worker.html?2001-3000": true,
"api-invalid-label.any.worker.html?3001-last": true,
2021-05-09 10:32:30 -04:00
"api-replacement-encodings.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"api-replacement-encodings.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"api-surrogates-utf8.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"api-surrogates-utf8.any.worker.html": true,
"encodeInto.any.html": true,
"encodeInto.any.worker.html": true,
"idlharness.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.worker.html": true,
"iso-2022-jp-decoder.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"iso-2022-jp-decoder.any.worker.html": true,
"legacy-mb-schinese": {
"gb18030": {
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"gb18030-decoder.any.html": true,
"gb18030-decoder.any.worker.html": true
},
"gbk": {
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"gbk-decoder.any.html": true,
"gbk-decoder.any.worker.html": true
}
},
2021-05-09 10:32:30 -04:00
"replacement-encodings.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"replacement-encodings.any.worker.html": false,
"streams": {
"backpressure.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"backpressure.any.worker.html": true,
"decode-attributes.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"decode-attributes.any.worker.html": true,
"decode-bad-chunks.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"decode-bad-chunks.any.worker.html": true,
"decode-ignore-bom.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"decode-ignore-bom.any.worker.html": true,
"decode-incomplete-input.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"decode-incomplete-input.any.worker.html": true,
"decode-non-utf8.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"decode-non-utf8.any.worker.html": true,
"decode-split-character.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"decode-split-character.any.worker.html": true,
"decode-utf8.any.html": true,
"decode-utf8.any.worker.html": true,
"encode-bad-chunks.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"encode-bad-chunks.any.worker.html": true,
"encode-utf8.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"encode-utf8.any.worker.html": true,
"readable-writable-properties.any.html": true,
"readable-writable-properties.any.worker.html": true,
"realms.window.html": false,
"invalid-realm.window.html": false
},
"textdecoder-arguments.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-arguments.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"textdecoder-byte-order-marks.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-byte-order-marks.any.worker.html": true,
"textdecoder-copy.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-copy.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"textdecoder-fatal-single-byte.any.html?1-1000": true,
"textdecoder-fatal-single-byte.any.html?1001-2000": true,
"textdecoder-fatal-single-byte.any.html?2001-3000": true,
"textdecoder-fatal-single-byte.any.html?3001-4000": true,
"textdecoder-fatal-single-byte.any.html?4001-5000": true,
"textdecoder-fatal-single-byte.any.html?5001-6000": true,
"textdecoder-fatal-single-byte.any.html?6001-7000": true,
"textdecoder-fatal-single-byte.any.html?7001-last": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-fatal-single-byte.any.worker.html?1-1000": true,
"textdecoder-fatal-single-byte.any.worker.html?1001-2000": true,
"textdecoder-fatal-single-byte.any.worker.html?2001-3000": true,
"textdecoder-fatal-single-byte.any.worker.html?3001-4000": true,
"textdecoder-fatal-single-byte.any.worker.html?4001-5000": true,
"textdecoder-fatal-single-byte.any.worker.html?5001-6000": true,
"textdecoder-fatal-single-byte.any.worker.html?6001-7000": true,
"textdecoder-fatal-single-byte.any.worker.html?7001-last": true,
"textdecoder-fatal-streaming.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-fatal-streaming.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"textdecoder-fatal.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-fatal.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"textdecoder-ignorebom.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-ignorebom.any.worker.html": true,
"textdecoder-labels.any.html": true,
"textdecoder-labels.any.worker.html": true,
"textdecoder-streaming.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-streaming.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"textdecoder-utf16-surrogates.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-utf16-surrogates.any.worker.html": true,
"textencoder-constructor-non-utf.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textencoder-constructor-non-utf.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"textencoder-utf16-surrogates.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textencoder-utf16-surrogates.any.worker.html": true,
"unsupported-encodings.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"unsupported-encodings.any.worker.html": false,
2021-07-03 15:34:48 -04:00
"single-byte-decoder.window.html?TextDecoder": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"textdecoder-eof.any.html": true,
2022-04-18 15:17:19 -04:00
"textdecoder-eof.any.worker.html": true,
"idlharness-shadowrealm.window.html": false,
"single-byte-decoder.window.html?XMLHttpRequest": false,
"single-byte-decoder.window.html?document": false,
"unsupported-labels.window.html": false
},
"hr-time": {
2021-05-09 10:32:30 -04:00
"monotonic-clock.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"monotonic-clock.any.worker.html": true,
"basic.any.html": true,
"basic.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"idlharness.any.html": [
"Window interface: attribute performance"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.worker.html": [
"WorkerGlobalScope interface: attribute performance",
"WorkerGlobalScope interface: self must inherit property \"performance\" with the proper type"
],
"window-worker-timeOrigin.window.html": true,
2022-04-18 15:17:19 -04:00
"idlharness-shadowrealm.window.html": false
},
"streams": {
"idlharness.any.html": true,
"idlharness.any.worker.html": true,
"piping": {
"abort.any.html": true,
"abort.any.worker.html": true,
"close-propagation-backward.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"close-propagation-backward.any.worker.html": true,
"close-propagation-forward.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"close-propagation-forward.any.worker.html": true,
"error-propagation-backward.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"error-propagation-backward.any.worker.html": true,
"error-propagation-forward.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"error-propagation-forward.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"flow-control.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"flow-control.any.worker.html": true,
"general.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"general.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"multiple-propagation.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"multiple-propagation.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"pipe-through.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"pipe-through.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"then-interception.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"then-interception.any.worker.html": true,
"throwing-options.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"throwing-options.any.worker.html": true,
"transform-streams.any.html": true,
"transform-streams.any.worker.html": true
},
2021-05-09 10:32:30 -04:00
"queuing-strategies.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"queuing-strategies.any.worker.html": true,
"readable-byte-streams": {
"bad-buffers-and-views.any.html": true,
"bad-buffers-and-views.any.worker.html": true,
"construct-byob-request.any.html": true,
"construct-byob-request.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"general.any.html": [
"ReadableStream with byte source: Respond to multiple pull() by separate enqueue()",
"ReadableStream with byte source: enqueue() discards auto-allocated BYOB request"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"general.any.worker.html": [
"ReadableStream with byte source: Respond to multiple pull() by separate enqueue()",
"ReadableStream with byte source: enqueue() discards auto-allocated BYOB request"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"non-transferable-buffers.any.html": true,
"non-transferable-buffers.any.worker.html": true,
2021-07-19 07:46:02 -04:00
"enqueue-with-detached-buffer.window.html": false,
"tee.any.html": true,
"tee.any.worker.html": true,
"respond-after-enqueue.any.html": true,
"respond-after-enqueue.any.worker.html": true,
"enqueue-with-detached-buffer.any.html": true,
"enqueue-with-detached-buffer.any.worker.html": true
},
"readable-streams": {
"async-iterator.any.html": [
"next() that succeeds; return()",
"next() that succeeds; return() [no awaiting]"
],
2021-05-09 10:32:30 -04:00
"bad-strategies.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"bad-strategies.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"bad-underlying-sources.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"bad-underlying-sources.any.worker.html": true,
"cancel.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"cancel.any.worker.html": true,
"constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"count-queuing-strategy-integration.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"count-queuing-strategy-integration.any.worker.html": true,
"default-reader.any.html": true,
"default-reader.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"floating-point-total-queue-size.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"floating-point-total-queue-size.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"garbage-collection.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"garbage-collection.any.worker.html": true,
"general.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"general.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"patched-global.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"patched-global.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"reentrant-strategies.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"reentrant-strategies.any.worker.html": true,
"tee.any.html": true,
"tee.any.worker.html": true,
"templated.any.html": true,
"templated.any.worker.html": true,
"async-iterator.any.worker.html": [
"next() that succeeds; return()",
"next() that succeeds; return() [no awaiting]"
],
"cross-realm-crash.window.html": false
},
"transform-streams": {
2021-05-09 10:32:30 -04:00
"backpressure.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"backpressure.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"errors.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"errors.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"flush.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"flush.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"general.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"general.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"lipfuzz.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"lipfuzz.any.worker.html": true,
"patched-global.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"patched-global.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"properties.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"properties.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"reentrant-strategies.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"reentrant-strategies.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"strategies.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"strategies.any.worker.html": true,
"terminate.any.html": true,
"terminate.any.worker.html": true
},
"writable-streams": {
"aborting.any.html": true,
"aborting.any.worker.html": true,
"bad-strategies.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"bad-strategies.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"bad-underlying-sinks.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"bad-underlying-sinks.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"byte-length-queuing-strategy.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"byte-length-queuing-strategy.any.worker.html": true,
"close.any.html": [
"when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"close.any.worker.html": [
"when close is called on a WritableStream in waiting state, ready should be fulfilled immediately even if close takes a long time"
],
"constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"count-queuing-strategy.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"count-queuing-strategy.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"error.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"error.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"floating-point-total-queue-size.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"floating-point-total-queue-size.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"general.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"general.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"properties.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"properties.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"reentrant-strategy.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"reentrant-strategy.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"start.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"start.any.worker.html": true,
"write.any.html": true,
"write.any.worker.html": true
},
"queuing-strategies-size-function-per-global.window.html": false,
"transferable": {
"deserialize-error.window.html": false,
"transfer-with-messageport.window.html": false
2022-04-18 15:17:19 -04:00
},
"idlharness-shadowrealm.window.html": false
},
"user-timing": {
2021-05-09 10:32:30 -04:00
"buffered-flag.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"buffered-flag.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"case-sensitivity.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"case-sensitivity.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"clear_all_marks.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"clear_all_marks.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"clear_all_measures.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"clear_all_measures.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"clear_non_existent_mark.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"clear_non_existent_mark.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"clear_non_existent_measure.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"clear_non_existent_measure.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"clear_one_mark.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"clear_one_mark.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"clear_one_measure.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"clear_one_measure.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"entry_type.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"entry_type.any.worker.html": true,
"idlharness.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"mark-entry-constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"mark-entry-constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"mark-errors.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"mark-errors.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"mark-l3.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"mark-l3.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"mark-measure-return-objects.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"mark-measure-return-objects.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"mark.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"mark.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"measure-l3.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"measure-l3.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"measure-with-dict.any.html": [
"measure entries' detail and start/end are customizable"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"measure-with-dict.any.worker.html": [
"measure entries' detail and start/end are customizable"
],
2021-05-09 10:32:30 -04:00
"measure_syntax_err.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"measure_syntax_err.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"structured-serialize-detail.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"structured-serialize-detail.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"supported-usertiming-types.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"supported-usertiming-types.any.worker.html": false,
"user_timing_exists.any.html": true,
"user_timing_exists.any.worker.html": true,
"invoke_with_timing_attributes.worker.html": true,
"performance-measure-invalid.worker.html": false,
"idlharness-shadowrealm.window.html": false
},
"wasm": {
"jsapi": {
"constructor": {
2021-05-09 10:32:30 -04:00
"compile.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"compile.any.worker.html": true,
"instantiate-bad-imports.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"instantiate-bad-imports.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"instantiate.any.html": [
"Synchronous options handling: Buffer argument"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"instantiate.any.worker.html": [
"Synchronous options handling: Buffer argument"
],
2021-05-09 10:32:30 -04:00
"multi-value.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"multi-value.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"toStringTag.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"toStringTag.any.worker.html": true,
"validate.any.html": true,
"validate.any.worker.html": true
},
"global": {
"constructor.any.html": true,
"constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"toString.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"toString.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"type.tentative.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"type.tentative.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"value-get-set.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"value-get-set.any.worker.html": true,
"valueOf.any.html": true,
"valueOf.any.worker.html": true
},
"idlharness.any.html": true,
"idlharness.any.worker.html": true,
"instance": {
"constructor-bad-imports.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor-bad-imports.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"constructor-caching.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor-caching.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
"exports.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"exports.any.worker.html": true,
"toString.any.html": true,
"toString.any.worker.html": true
},
"interface.any.html": true,
"interface.any.worker.html": true,
"memory": {
"buffer.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"buffer.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"grow.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"grow.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"toString.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"toString.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"type.tentative.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"type.tentative.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"constructor-shared.tentative.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor-shared.tentative.any.worker.html": true,
"constructor-types.tentative.any.html": false,
"constructor-types.tentative.any.worker.html": false
},
"module": {
2021-05-09 10:32:30 -04:00
"constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"customSections.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"customSections.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"exports.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"exports.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"imports.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"imports.any.worker.html": true,
"toString.any.html": true,
"toString.any.worker.html": true
},
"prototypes.any.html": true,
"prototypes.any.worker.html": true,
"table": {
"constructor.any.html": true,
"constructor.any.worker.html": true,
"get-set.any.html": true,
"get-set.any.worker.html": true,
"grow.any.html": true,
"grow.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"length.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"length.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"toString.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"toString.any.worker.html": true,
"constructor-types.tentative.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor-types.tentative.any.worker.html": false,
"type.tentative.any.html": false,
"type.tentative.any.worker.html": false
2021-07-19 07:46:02 -04:00
},
"exception": {
"basic.tentative.any.html": true,
"basic.tentative.any.worker.html": true,
2021-10-12 07:30:39 -04:00
"constructor.tentative.any.html": true,
"constructor.tentative.any.worker.html": true,
2022-01-19 06:31:32 -05:00
"getArg.tentative.any.html": [
"Getting out-of-range argument"
2022-01-19 06:31:32 -05:00
],
"getArg.tentative.any.worker.html": [
"Getting out-of-range argument"
2022-01-19 06:31:32 -05:00
],
2021-10-12 07:30:39 -04:00
"is.tentative.any.html": true,
"is.tentative.any.worker.html": true,
"toString.tentative.any.html": true,
"toString.tentative.any.worker.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"type.tentative.any.html": false,
"type.tentative.any.worker.html": false,
"identity.tentative.any.html": true,
"identity.tentative.any.worker.html": true
2021-07-19 07:46:02 -04:00
},
"tag": {
2021-10-12 07:30:39 -04:00
"constructor.tentative.any.html": true,
"constructor.tentative.any.worker.html": true,
"toString.tentative.any.html": true,
"toString.tentative.any.worker.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"type.tentative.any.html": false,
"type.tentative.any.worker.html": false
},
"function": {
"call.tentative.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"call.tentative.any.worker.html": false,
"constructor.tentative.any.html": false,
"constructor.tentative.any.worker.html": false,
"table.tentative.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"table.tentative.any.worker.html": false,
"type.tentative.any.html": false,
"type.tentative.any.worker.html": false
}
},
"serialization": {
"module": {
2021-05-09 10:32:30 -04:00
"serialization-via-idb.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"serialization-via-idb.any.worker.html": false,
2021-09-07 17:50:22 -04:00
"serialization-via-notifications-api.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"serialization-via-notifications-api.any.worker.html": false,
"nested-worker-success.any.worker.html": true
2021-07-19 07:46:02 -04:00
},
"arraybuffer": {
"transfer.window.html": false
}
},
"webapi": {
"abort.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"abort.any.worker.html": true,
"body.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"body.any.worker.html": true,
"contenttype.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"contenttype.any.worker.html": true,
"empty-body.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"empty-body.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"historical.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"historical.any.worker.html": false,
"idlharness.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.worker.html": true,
"instantiateStreaming-bad-imports.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"instantiateStreaming-bad-imports.any.worker.html": true,
"instantiateStreaming.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"instantiateStreaming.any.worker.html": true,
"invalid-args.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"invalid-args.any.worker.html": true,
"invalid-code.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"invalid-code.any.worker.html": true,
"modified-contenttype.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"modified-contenttype.any.worker.html": true,
"origin.sub.any.html": [
"Opaque response: compileStreaming",
"Opaque response: instantiateStreaming"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"origin.sub.any.worker.html": [
"Opaque response: compileStreaming",
"Opaque response: instantiateStreaming"
],
"rejected-arg.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"rejected-arg.any.worker.html": true,
"status.any.html": true,
"status.any.worker.html": true
2021-09-07 17:50:22 -04:00
},
"create_multiple_memory.worker.html": true
},
2021-09-25 09:27:34 -04:00
"webidl": {
"ecmascript-binding": {
"es-exceptions": {
2021-05-09 10:32:30 -04:00
"DOMException-constants.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"DOMException-constants.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"DOMException-constructor-and-prototype.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"DOMException-constructor-and-prototype.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"DOMException-constructor-behavior.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"DOMException-constructor-behavior.any.worker.html": true,
"DOMException-custom-bindings.any.html": true,
"DOMException-custom-bindings.any.worker.html": true
},
"class-string-interface.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"class-string-interface.any.worker.html": true,
"class-string-iterator-prototype-object.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"class-string-iterator-prototype-object.any.worker.html": true,
"class-string-named-properties-object.window.html": false,
"global-immutable-prototype.any.html": [
"Setting to a different prototype"
],
"global-immutable-prototype.any.worker.html": {
"ignore": true
},
"global-object-implicit-this-value.any.html": [
"Global object's getter throws when called on incompatible object",
"Global object's setter throws when called on incompatible object",
"Global object's operation throws when called on incompatible object",
"Global object's getter works when called on null / undefined",
"Global object's setter works when called on null / undefined"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"global-object-implicit-this-value.any.worker.html": [
"Global object's getter throws when called on incompatible object",
"Global object's setter throws when called on incompatible object",
"Global object's operation throws when called on incompatible object",
"Global object's getter works when called on null / undefined",
"Global object's setter works when called on null / undefined"
],
"legacy-factor-function-subclass.window.html": false,
"no-regexp-special-casing.any.html": [
"Conversion to a sequence works"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"no-regexp-special-casing.any.worker.html": [
"Conversion to a sequence works"
],
"builtin-function-properties.any.html": true,
"builtin-function-properties.any.worker.html": true,
"observable-array-no-leak-of-internals.window.html": false,
"observable-array-ownkeys.window.html": false
},
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.html": true,
"idlharness.any.worker.html": true,
"idlharness-shadowrealm.window.html": false
2021-01-27 16:37:15 -05:00
},
"url": {
2021-05-09 10:32:30 -04:00
"historical.any.html": [
"<a> and <area>.searchParams should be undefined",
"URL: no structured serialize/deserialize support",
"URLSearchParams: no structured serialize/deserialize support"
],
"historical.any.worker.html": [
"URL: no structured serialize/deserialize support",
"URLSearchParams: no structured serialize/deserialize support"
2021-01-27 16:37:15 -05:00
],
"idlharness.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"toascii.window.html": [
"aa-- (using <a>.host)",
"aa-- (using <a>.hostname)",
"aa-- (using <area>.host)",
"aa-- (using <area>.hostname)",
"a†-- (using <a>.host)",
"a†-- (using <a>.hostname)",
"a†-- (using <area>.host)",
"a†-- (using <area>.hostname)",
"ab--c (using <a>.host)",
"ab--c (using <a>.hostname)",
"ab--c (using <area>.host)",
"ab--c (using <area>.hostname)",
"-x (using <a>.host)",
"-x (using <a>.hostname)",
"-x (using <area>.host)",
"-x (using <area>.hostname)",
"-† (using <a>.host)",
"-† (using <a>.hostname)",
"-† (using <area>.host)",
"-† (using <area>.hostname)",
2021-12-06 10:03:09 -05:00
"-x.xn--zca (using <a>.host)",
"-x.xn--zca (using <a>.hostname)",
"-x.xn--zca (using <area>.host)",
"-x.xn--zca (using <area>.hostname)",
"-x.ß (using <a>.host)",
"-x.ß (using <a>.hostname)",
"-x.ß (using <area>.host)",
"-x.ß (using <area>.hostname)",
"x-.xn--zca (using <a>.host)",
"x-.xn--zca (using <a>.hostname)",
"x-.xn--zca (using <area>.host)",
"x-.xn--zca (using <area>.hostname)",
"x-.ß (using <a>.host)",
"x-.ß (using <a>.hostname)",
"x-.ß (using <area>.host)",
"x-.ß (using <area>.hostname)",
"x..xn--zca (using <a>.host)",
"x..xn--zca (using <a>.hostname)",
"x..xn--zca (using <area>.host)",
"x..xn--zca (using <area>.hostname)",
"x..ß (using <a>.host)",
"x..ß (using <a>.hostname)",
"x..ß (using <area>.host)",
"x..ß (using <area>.hostname)",
2021-09-25 09:27:34 -04:00
"xn--a (using <a>)",
"xn--a (using <a>.host)",
"xn--a (using <a>.hostname)",
"xn--a (using <area>)",
"xn--a (using <area>.host)",
"xn--a (using <area>.hostname)",
2021-12-06 10:03:09 -05:00
"xn--a.xn--zca (using <a>)",
"xn--a.xn--zca (using <a>.host)",
"xn--a.xn--zca (using <a>.hostname)",
"xn--a.xn--zca (using <area>)",
"xn--a.xn--zca (using <area>.host)",
"xn--a.xn--zca (using <area>.hostname)",
"xn--a.ß (using <a>)",
"xn--a.ß (using <a>.host)",
"xn--a.ß (using <a>.hostname)",
"xn--a.ß (using <area>)",
"xn--a.ß (using <area>.host)",
"xn--a.ß (using <area>.hostname)",
"xn--ls8h= (using <a>)",
"xn--ls8h= (using <a>.host)",
"xn--ls8h= (using <a>.hostname)",
"xn--ls8h= (using <area>)",
"xn--ls8h= (using <area>.host)",
"xn--ls8h= (using <area>.hostname)",
2021-12-06 10:03:09 -05:00
"xn--tešla (using <a>)",
"xn--tešla (using <a>.host)",
"xn--tešla (using <a>.hostname)",
"xn--tešla (using <area>)",
"xn--tešla (using <area>.host)",
"xn--tešla (using <area>.hostname)",
"xn--zca.xn--zca (using <a>.host)",
"xn--zca.xn--zca (using <a>.hostname)",
"xn--zca.xn--zca (using <area>.host)",
"xn--zca.xn--zca (using <area>.hostname)",
"xn--zca.ß (using <a>.host)",
"xn--zca.ß (using <a>.hostname)",
"xn--zca.ß (using <area>.host)",
"xn--zca.ß (using <area>.hostname)",
"ab--c.xn--zca (using <a>.host)",
"ab--c.xn--zca (using <a>.hostname)",
"ab--c.xn--zca (using <area>.host)",
"ab--c.xn--zca (using <area>.hostname)",
"ab--c.ß (using <a>.host)",
"ab--c.ß (using <a>.hostname)",
"ab--c.ß (using <area>.host)",
"ab--c.ß (using <area>.hostname)",
2021-09-25 09:27:34 -04:00
".example (using URL)",
".example (using URL.host)",
".example (using URL.hostname)",
".example (using <a>)",
".example (using <a>.host)",
".example (using <a>.hostname)",
".example (using <area>)",
".example (using <area>.host)",
".example (using <area>.hostname)",
"xn--1ug.example (using URL)",
"xn--1ug.example (using URL.host)",
"xn--1ug.example (using URL.hostname)",
"xn--1ug.example (using <a>)",
"xn--1ug.example (using <a>.host)",
"xn--1ug.example (using <a>.hostname)",
"xn--1ug.example (using <area>)",
"xn--1ug.example (using <area>.host)",
"xn--1ug.example (using <area>.hostname)",
"يa (using <a>)",
"يa (using <a>.host)",
"يa (using <a>.hostname)",
"يa (using <area>)",
"يa (using <area>.host)",
"يa (using <area>.hostname)",
"xn--a-yoc (using <a>)",
"xn--a-yoc (using <a>.host)",
"xn--a-yoc (using <a>.hostname)",
"xn--a-yoc (using <area>)",
"xn--a-yoc (using <area>.host)",
"xn--a-yoc (using <area>.hostname)",
"ශ්‍රී (using <a>.host)",
"ශ්‍රී (using <a>.hostname)",
"ශ්‍රී (using <area>.host)",
"ශ්‍රී (using <area>.hostname)",
"نامه‌ای (using <a>.host)",
"نامه‌ای (using <a>.hostname)",
"نامه‌ای (using <area>.host)",
"نامه‌ای (using <area>.hostname)",
"<22>.com (using <a>)",
"<22>.com (using <a>.host)",
"<22>.com (using <a>.hostname)",
"<22>.com (using <area>)",
"<22>.com (using <area>.host)",
"<22>.com (using <area>.hostname)",
"xn--zn7c.com (using <a>)",
"xn--zn7c.com (using <a>.host)",
"xn--zn7c.com (using <a>.hostname)",
"xn--zn7c.com (using <area>)",
"xn--zn7c.com (using <area>.host)",
"xn--zn7c.com (using <area>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901x (using <a>.host)",
"x01234567890123456789012345678901234567890123456789012345678901x (using <a>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901x (using <area>.host)",
"x01234567890123456789012345678901234567890123456789012345678901x (using <area>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901† (using <a>.host)",
"x01234567890123456789012345678901234567890123456789012345678901† (using <a>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901† (using <area>.host)",
"x01234567890123456789012345678901234567890123456789012345678901† (using <area>.hostname)",
2021-12-06 10:03:09 -05:00
"x01234567890123456789012345678901234567890123456789012345678901x.xn--zca (using <a>.host)",
"x01234567890123456789012345678901234567890123456789012345678901x.xn--zca (using <a>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901x.xn--zca (using <area>.host)",
"x01234567890123456789012345678901234567890123456789012345678901x.xn--zca (using <area>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901x.ß (using <a>.host)",
"x01234567890123456789012345678901234567890123456789012345678901x.ß (using <a>.hostname)",
"x01234567890123456789012345678901234567890123456789012345678901x.ß (using <area>.host)",
"x01234567890123456789012345678901234567890123456789012345678901x.ß (using <area>.hostname)",
2021-09-25 09:27:34 -04:00
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.x (using <a>.host)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.x (using <a>.hostname)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.x (using <area>.host)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.x (using <area>.hostname)",
2021-12-06 10:03:09 -05:00
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.xn--zca (using <a>.host)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.xn--zca (using <a>.hostname)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.xn--zca (using <area>.host)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.xn--zca (using <area>.hostname)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.ß (using <a>.host)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.ß (using <a>.hostname)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.ß (using <area>.host)",
"01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.01234567890123456789012345678901234567890123456789.0123456789012345678901234567890123456789012345678.ß (using <area>.hostname)",
2021-09-25 09:27:34 -04:00
"a­b (using <a>.host)",
"a­b (using <a>.hostname)",
"a­b (using <area>.host)",
"a­b (using <area>.hostname)",
"≠ (using <a>.host)",
"≠ (using <a>.hostname)",
"≠ (using <area>.host)",
"≠ (using <area>.hostname)",
"≮ (using <a>.host)",
"≮ (using <a>.hostname)",
"≮ (using <area>.host)",
"≮ (using <area>.hostname)",
"≯ (using <a>.host)",
"≯ (using <a>.hostname)",
"≯ (using <area>.host)",
"≯ (using <area>.hostname)"
2021-09-25 09:27:34 -04:00
],
2021-05-09 10:32:30 -04:00
"url-constructor.any.html": [
2021-01-27 16:37:15 -05:00
"Parsing: </> against <file://h/C:/a/b>",
"Parsing: <file:\\\\//> against <about:blank>",
"Parsing: <file:\\\\\\\\> against <about:blank>",
"Parsing: <file:\\\\\\\\?fox> against <about:blank>",
"Parsing: <file:\\\\\\\\#guppy> against <about:blank>",
"Parsing: <file://spider///> against <about:blank>",
"Parsing: <file:\\\\localhost//> against <about:blank>",
"Parsing: <file://\\/localhost//cat> against <about:blank>",
"Parsing: <file://localhost//a//../..//> against <about:blank>",
"Parsing: </////mouse> against <file:///elephant>",
"Parsing: <\\/localhost//pig> against <file://lion/>",
"Parsing: <//localhost//pig> against <file://lion/>",
"Parsing: </..//localhost//pig> against <file://lion/>",
2021-01-27 16:37:15 -05:00
"Parsing: <C|> against <file://host/dir/file>",
"Parsing: <C|> against <file://host/D:/dir1/dir2/file>",
"Parsing: <C|#> against <file://host/dir/file>",
"Parsing: <C|?> against <file://host/dir/file>",
"Parsing: <C|/> against <file://host/dir/file>",
"Parsing: <C|\n/> against <file://host/dir/file>",
"Parsing: <C|\\> against <file://host/dir/file>",
"Parsing: </c:/foo/bar> against <file://host/path>",
"Parsing: <file://example.net/C:/> against <about:blank>",
"Parsing: <file://1.2.3.4/C:/> against <about:blank>",
"Parsing: <file://[1::8]/C:/> against <about:blank>",
"Parsing: <C|/> against <file://host/>",
"Parsing: </C:/> against <file://host/>",
"Parsing: <file:C:/> against <file://host/>",
"Parsing: <file:/C:/> against <file://host/>",
2021-01-27 16:37:15 -05:00
"Parsing: <file://localhost//a//../..//foo> against <about:blank>",
"Parsing: <file://localhost////foo> against <about:blank>",
"Parsing: <file:////foo> against <about:blank>",
"Parsing: <file:////one/two> against <file:///>",
"Parsing: <////one/two> against <file:///>",
"Parsing: <file:///.//> against <file:////>",
2021-01-27 16:37:15 -05:00
"Parsing: <file:.//p> against <about:blank>",
"Parsing: <file:/.//p> against <about:blank>",
2021-01-27 16:37:15 -05:00
"Parsing: <non-spec:/.//> against <about:blank>",
"Parsing: <non-spec:/..//> against <about:blank>",
"Parsing: <non-spec:/a/..//> against <about:blank>",
"Parsing: <non-spec:/.//path> against <about:blank>",
"Parsing: <non-spec:/..//path> against <about:blank>",
"Parsing: <non-spec:/a/..//path> against <about:blank>",
"Parsing: </.//path> against <non-spec:/p>",
"Parsing: </..//path> against <non-spec:/p>",
"Parsing: <..//path> against <non-spec:/p>",
"Parsing: <a/..//path> against <non-spec:/p>",
"Parsing: <> against <non-spec:/..//p>",
"Parsing: <path> against <non-spec:/..//p>"
2021-01-27 16:37:15 -05:00
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"url-constructor.any.worker.html": [
"Parsing: </> against <file://h/C:/a/b>",
"Parsing: <file:\\\\//> against <about:blank>",
"Parsing: <file:\\\\\\\\> against <about:blank>",
"Parsing: <file:\\\\\\\\?fox> against <about:blank>",
"Parsing: <file:\\\\\\\\#guppy> against <about:blank>",
"Parsing: <file://spider///> against <about:blank>",
"Parsing: <file:\\\\localhost//> against <about:blank>",
"Parsing: <file://\\/localhost//cat> against <about:blank>",
"Parsing: <file://localhost//a//../..//> against <about:blank>",
"Parsing: </////mouse> against <file:///elephant>",
"Parsing: <\\/localhost//pig> against <file://lion/>",
"Parsing: <//localhost//pig> against <file://lion/>",
"Parsing: </..//localhost//pig> against <file://lion/>",
"Parsing: <C|> against <file://host/dir/file>",
"Parsing: <C|> against <file://host/D:/dir1/dir2/file>",
"Parsing: <C|#> against <file://host/dir/file>",
"Parsing: <C|?> against <file://host/dir/file>",
"Parsing: <C|/> against <file://host/dir/file>",
"Parsing: <C|\n/> against <file://host/dir/file>",
"Parsing: <C|\\> against <file://host/dir/file>",
"Parsing: </c:/foo/bar> against <file://host/path>",
"Parsing: <file://example.net/C:/> against <about:blank>",
"Parsing: <file://1.2.3.4/C:/> against <about:blank>",
"Parsing: <file://[1::8]/C:/> against <about:blank>",
"Parsing: <C|/> against <file://host/>",
"Parsing: </C:/> against <file://host/>",
"Parsing: <file:C:/> against <file://host/>",
"Parsing: <file:/C:/> against <file://host/>",
"Parsing: <file://localhost//a//../..//foo> against <about:blank>",
"Parsing: <file://localhost////foo> against <about:blank>",
"Parsing: <file:////foo> against <about:blank>",
"Parsing: <file:////one/two> against <file:///>",
"Parsing: <////one/two> against <file:///>",
"Parsing: <file:///.//> against <file:////>",
"Parsing: <file:.//p> against <about:blank>",
"Parsing: <file:/.//p> against <about:blank>",
"Parsing: <non-spec:/.//> against <about:blank>",
"Parsing: <non-spec:/..//> against <about:blank>",
"Parsing: <non-spec:/a/..//> against <about:blank>",
"Parsing: <non-spec:/.//path> against <about:blank>",
"Parsing: <non-spec:/..//path> against <about:blank>",
"Parsing: <non-spec:/a/..//path> against <about:blank>",
"Parsing: </.//path> against <non-spec:/p>",
"Parsing: </..//path> against <non-spec:/p>",
"Parsing: <..//path> against <non-spec:/p>",
"Parsing: <a/..//path> against <non-spec:/p>",
"Parsing: <> against <non-spec:/..//p>",
"Parsing: <path> against <non-spec:/..//p>"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"url-origin.any.html": true,
"url-origin.any.worker.html": true,
"url-searchparams.any.html": true,
"url-searchparams.any.worker.html": true,
"url-setters-stripping.any.html": [
"Setting protocol with leading U+0000 (https:)",
"Setting protocol with U+0000 before inserted colon (https:)",
"Setting port with leading U+0000 (https:)",
"Setting pathname with trailing U+0000 (https:)",
"Setting protocol with leading U+001F (https:)",
"Setting protocol with U+001F before inserted colon (https:)",
2022-04-18 15:17:19 -04:00
"Setting port with leading U+001F (https:)",
"Setting pathname with trailing U+001F (https:)",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Setting protocol with leading U+0000 (wpt++:)",
"Setting protocol with U+0000 before inserted colon (wpt++:)",
"Setting port with leading U+0000 (wpt++:)",
"Setting pathname with trailing U+0000 (wpt++:)",
"Setting protocol with leading U+001F (wpt++:)",
"Setting protocol with U+001F before inserted colon (wpt++:)",
"Setting port with leading U+001F (wpt++:)",
"Setting pathname with trailing U+001F (wpt++:)"
],
"url-setters-stripping.any.worker.html": [
2021-01-27 16:37:15 -05:00
"Setting protocol with leading U+0000 (https:)",
"Setting protocol with U+0000 before inserted colon (https:)",
"Setting port with leading U+0000 (https:)",
"Setting pathname with trailing U+0000 (https:)",
2021-01-27 16:37:15 -05:00
"Setting protocol with leading U+001F (https:)",
"Setting protocol with U+001F before inserted colon (https:)",
2022-04-18 15:17:19 -04:00
"Setting port with leading U+001F (https:)",
"Setting pathname with trailing U+001F (https:)",
2021-01-27 16:37:15 -05:00
"Setting protocol with leading U+0000 (wpt++:)",
"Setting protocol with U+0000 before inserted colon (wpt++:)",
"Setting port with leading U+0000 (wpt++:)",
2021-01-27 16:37:15 -05:00
"Setting pathname with trailing U+0000 (wpt++:)",
"Setting protocol with leading U+001F (wpt++:)",
"Setting protocol with U+001F before inserted colon (wpt++:)",
"Setting port with leading U+001F (wpt++:)",
2021-01-27 16:37:15 -05:00
"Setting pathname with trailing U+001F (wpt++:)"
],
2021-05-09 10:32:30 -04:00
"url-tojson.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"url-tojson.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"urlencoded-parser.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlencoded-parser.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"urlsearchparams-append.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-append.any.worker.html": true,
"urlsearchparams-constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-constructor.any.worker.html": true,
"urlsearchparams-delete.any.html": [
"Changing the query of a URL with an opaque path can impact the path"
],
"urlsearchparams-delete.any.worker.html": [
"Changing the query of a URL with an opaque path can impact the path"
],
2021-05-09 10:32:30 -04:00
"urlsearchparams-foreach.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-foreach.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"urlsearchparams-get.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-get.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"urlsearchparams-getall.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-getall.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"urlsearchparams-has.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-has.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"urlsearchparams-set.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-set.any.worker.html": true,
"urlsearchparams-size.any.html": true,
"urlsearchparams-sort.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-sort.any.worker.html": true,
"urlsearchparams-stringifier.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"urlsearchparams-stringifier.any.worker.html": true,
"url-setters.any.html": [
"URL: Setting <http://example.net/path>.hostname = 'example.com:8080' : delimiter invalidates entire value",
"URL: Setting <http://example.net:8080/path>.hostname = 'example.com:' : delimiter invalidates entire value",
"URL: Setting <non-spec:/.//p>.hostname = 'h' Drop /. from path",
"URL: Setting <non-spec:/.//p>.hostname = ''",
2021-07-03 15:34:48 -04:00
"URL: Setting <foo://somehost/some/path>.pathname = '' Non-special URLs can have their paths erased",
"URL: Setting <foo:///some/path>.pathname = '' Non-special URLs with an empty host can have their paths erased",
"URL: Setting <file://monkey/>.pathname = '\\\\' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//\\/' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//monkey/..//' File URLs and (back)slashes",
"URL: Setting <non-spec:/>.pathname = '/.//p' Serialize /. in path",
"URL: Setting <non-spec:/>.pathname = '/..//p'",
"URL: Setting <non-spec:/>.pathname = '//p'",
"URL: Setting <non-spec:/.//>.pathname = 'p' Drop /. from path"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"url-setters.any.worker.html": [
"URL: Setting <http://example.net/path>.hostname = 'example.com:8080' : delimiter invalidates entire value",
"URL: Setting <http://example.net:8080/path>.hostname = 'example.com:' : delimiter invalidates entire value",
"URL: Setting <non-spec:/.//p>.hostname = 'h' Drop /. from path",
"URL: Setting <non-spec:/.//p>.hostname = ''",
"URL: Setting <foo://somehost/some/path>.pathname = '' Non-special URLs can have their paths erased",
"URL: Setting <foo:///some/path>.pathname = '' Non-special URLs with an empty host can have their paths erased",
"URL: Setting <file://monkey/>.pathname = '\\\\' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//\\/' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//monkey/..//' File URLs and (back)slashes",
"URL: Setting <non-spec:/>.pathname = '/.//p' Serialize /. in path",
"URL: Setting <non-spec:/>.pathname = '/..//p'",
"URL: Setting <non-spec:/>.pathname = '//p'",
"URL: Setting <non-spec:/.//>.pathname = 'p' Drop /. from path"
2022-04-18 15:17:19 -04:00
],
"idlharness-shadowrealm.window.html": false,
"percent-encoding.window.html": [
"Input † with encoding big5",
"Input † with encoding euc-kr",
"Input † with encoding utf-8",
"Input † with encoding windows-1252",
"Input \u000eA with encoding big5",
"Input \u000eA with encoding iso-2022-jp",
"Input \u000eA with encoding utf-8",
"Input ‾\\ with encoding iso-2022-jp",
"Input ‾\\ with encoding utf-8",
"Input  with encoding gb18030",
"Input  with encoding utf-8",
"Input with encoding shift_jis",
"Input with encoding utf-8",
"Input á| with encoding utf-8",
"Input \ud800 with encoding utf-8",
"Input \ud800 with encoding windows-1252"
2023-03-22 10:43:20 -04:00
],
"url-setters-a-area.window.html": {
"ignore": true
},
"IdnaTestV2.window.html": [
"ToASCII(\"ab\") C1",
"ToASCII(\"AB\") C1",
"ToASCII(\"Ab\") C1",
"ToASCII(\"xn--ab-j1t\") C1",
"ToASCII(\"ab\") C2",
"ToASCII(\"AB\") C2",
"ToASCII(\"Ab\") C2",
"ToASCII(\"xn--ab-m1t\") C2",
"ToASCII(\"1.aßbcßßßßdςσßßßßßßßßeßßßßßßßßßßxßßßßßßßßßßyßßßßßßßß̂ßz\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.ASSBCSSSSSSSSDΣΣSSSSSSSSSSSSSSSSESSSSSSSSSSSSSSSSSSSSXSSSSSSSSSSSSSSSSSSSSYSSSSSSSSSSSSSSSŜSSZ\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.ASSBCSSSSSSSSDΣΣSSSSSSSSSSSSSSSSESSSSSSSSSSSSSSSSSSSSXSSSSSSSSSSSSSSSSSSSSYSSSSSSSSSSSSSSSŜSSZ\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.assbcssssssssdσσssssssssssssssssessssssssssssssssssssxssssssssssssssssssssysssssssssssssssŝssz\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.assbcssssssssdσσssssssssssssssssessssssssssssssssssssxssssssssssssssssssssysssssssssssssssŝssz\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.Assbcssssssssdσσssssssssssssssssessssssssssssssssssssxssssssssssssssssssssysssssssssssssssŝssz\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.Assbcssssssssdσσssssssssssssssssessssssssssssssssssssxssssssssssssssssssssysssssssssssssssŝssz\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.xn--assbcssssssssdssssssssssssssssessssssssssssssssssssxssssssssssssssssssssysssssssssssssssssz-pxq1419aa69989dba9gc\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.Aßbcßßßßdςσßßßßßßßßeßßßßßßßßßßxßßßßßßßßßßyßßßßßßßß̂ßz\") C1; C2; A4_2 (ignored)",
"ToASCII(\"1.xn--abcdexyz-qyacaaabaaaaaaabaaaaaaaaabaaaaaaaaabaaaaaaaa010ze2isb1140zba8cc\") C1; C2; A4_2 (ignored)",
"ToASCII(\"xn--bß\") C1; C2",
"ToASCII(\"XN--BSS\") C1; C2",
"ToASCII(\"xn--bss\") C1; C2",
"ToASCII(\"Xn--Bss\") C1; C2",
"ToASCII(\"xn--xn--bss-7z6ccid\") C1; C2",
"ToASCII(\"Xn--Bß\") C1; C2",
"ToASCII(\"xn--xn--b-pqa5796ccahd\") C1; C2",
"ToASCII(\"ஹ‍\") C2",
"ToASCII(\"xn--dmc225h\") C2",
"ToASCII(\"\") C2",
"ToASCII(\"xn--1ug\") C2",
"ToASCII(\"ஹ‌\") C1",
"ToASCII(\"xn--dmc025h\") C1",
"ToASCII(\"\") C1",
"ToASCII(\"xn--0ug\") C1",
"ToASCII(\"ۯ‌ۯ\") C1",
"ToASCII(\"xn--cmba004q\") C1",
"ToASCII(\"ß۫。‍\") C2",
"ToASCII(\"SS۫。\") C2",
"ToASCII(\"ss۫。\") C2",
"ToASCII(\"Ss۫。\") C2",
"ToASCII(\"xn--ss-59d.xn--1ug\") C2",
"ToASCII(\"xn--zca012a.xn--1ug\") C2",
"ToASCII(\"‌긃.榶-\") C1; V3 (ignored)",
"ToASCII(\"‌긃.榶-\") C1; V3 (ignored)",
"ToASCII(\"xn--0ug3307c.xn----d87b\") C1; V3 (ignored)",
"ToASCII(\"Å둄-\") C1; V3 (ignored)",
"ToASCII(\"Å둄-\") C1; V3 (ignored)",
"ToASCII(\"Å둄-.\") C1; V3 (ignored)",
"ToASCII(\"Å둄-.\") C1; V3 (ignored)",
"ToASCII(\"å둄-.\") C1; V3 (ignored)",
"ToASCII(\"å둄-.\") C1; V3 (ignored)",
"ToASCII(\"xn----1fa1788k.xn--0ug\") C1; V3 (ignored)",
"ToASCII(\"å둄-\") C1; V3 (ignored)",
"ToASCII(\"å둄-\") C1; V3 (ignored)",
"ToASCII(\"ꡦᡑ1.。𐋣-\") C2; V3 (ignored); A4_2 (ignored)",
"ToASCII(\"xn--1-o7j663bdl7m..xn----381i\") C2; V3 (ignored); A4_2 (ignored)",
"ToASCII(\"1.䰹‍-。웈\") C2; V3 (ignored)",
"ToASCII(\"1.䰹‍-。웈\") C2; V3 (ignored)",
"ToASCII(\"1.xn----tgnz80r.xn--kp5b\") C2; V3 (ignored)",
"ToASCII(\"-3.‍ヌᢕ\") C2; V3 (ignored)",
"ToASCII(\"-3.xn--fbf739aq5o\") C2; V3 (ignored)",
"ToASCII(\"ς-。‌𝟭-\") C1; V3 (ignored)",
"ToASCII(\"ς-。1-\") C1; V3 (ignored)",
"ToASCII(\"Σ-。1-\") C1; V3 (ignored)",
"ToASCII(\"σ-。1-\") C1; V3 (ignored)",
"ToASCII(\"xn----zmb.xn--1--i1t\") C1; V3 (ignored)",
"ToASCII(\"xn----xmb.xn--1--i1t\") C1; V3 (ignored)",
"ToASCII(\"Σ-。‌𝟭-\") C1; V3 (ignored)",
"ToASCII(\"σ-。‌𝟭-\") C1; V3 (ignored)",
"ToASCII(\"ᡯ⚉姶🄉.۷‍🎪‍\") C2; P1; V6",
"ToASCII(\"𝟵隁⯮.᠍‌\") C1",
"ToASCII(\"9隁⯮.\") C1",
"ToASCII(\"xn--9-mfs8024b.xn--0ug\") C1",
"ToASCII(\"ß‌꫶ᢥ.⊶ⴡⴖ\") C1",
"ToASCII(\"ss꫶ᢥ.⊶ⴡⴖ\") C1",
"ToASCII(\"xn--ss-4ep585bkm5p.xn--ifh802b6a\") C1",
"ToASCII(\"xn--zca682johfi89m.xn--ifh802b6a\") C1",
"ToASCII(\"ß‌꫶ᢥ.⊶ⴡⴖ\") C1",
"ToASCII(\"ss꫶ᢥ⊶ⴡⴖ\") C1",
"ToASCII(\"-。‍\") C2; V3 (ignored)",
"ToASCII(\"-。‍\") C2; V3 (ignored)",
"ToASCII(\"-.xn--1ug\") C2; V3 (ignored)",
"ToASCII(\"ς‍-.ⴣ𦟙\") C2; V3 (ignored)",
"ToASCII(\"σ-.ⴣ𦟙\") C2; V3 (ignored)",
"ToASCII(\"xn----zmb048s.xn--rlj2573p\") C2; V3 (ignored)",
"ToASCII(\"xn----xmb348s.xn--rlj2573p\") C2; V3 (ignored)",
"ToASCII(\"鱊。‌\") C1",
"ToASCII(\"xn--rt6a.xn--0ug\") C1",
"ToASCII(\"‌ⴚ。ς\") C1",
"ToASCII(\"‌ⴚ。σ\") C1",
"ToASCII(\"xn--0ug262c.xn--4xa\") C1",
"ToASCII(\"xn--0ug262c.xn--3xa\") C1",
"ToASCII(\"‌ⴚ。ς\") C1",
"ToASCII(\"‌ⴚ。σ\") C1",
"ToASCII(\"‍⾕。‌꥓̐ꡎ\") C1; C2",
"ToASCII(\"‍⾕。‌꥓̐ꡎ\") C1; C2",
"ToASCII(\"‍谷。‌꥓̐ꡎ\") C1; C2",
"ToASCII(\"xn--1ug0273b.xn--0sa359l6n7g13a\") C1; C2",
"ToASCII(\"‍。‌\") C1; C2",
"ToASCII(\"xn--1ug.xn--0ug\") C1; C2",
"ToASCII(\"‌。。\") C1; A4_2 (ignored)",
"ToASCII(\"xn--0ug..\") C1; A4_2 (ignored)",
"ToASCII(\"ᡲ-𝟹.ß--\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-3.ß--\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-3.SS--\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-3.ss--\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-3.Ss--\") C1; V3 (ignored)",
"ToASCII(\"xn---3-p9o.xn--ss---276a\") C1; V3 (ignored)",
"ToASCII(\"xn---3-p9o.xn-----fia9303a\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-𝟹.SS--\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-𝟹.ss--\") C1; V3 (ignored)",
"ToASCII(\"ᡲ-𝟹.Ss--\") C1; V3 (ignored)",
"ToASCII(\"𝟙。‍𝟸‍⁷\") C2",
"ToASCII(\"1。27\") C2",
"ToASCII(\"1.xn--27-l1tb\") C2",
"ToASCII(\".ßⴉ-\") C1; V3 (ignored)",
"ToASCII(\".ssⴉ-\") C1; V3 (ignored)",
"ToASCII(\".Ssⴉ-\") C1; V3 (ignored)",
"ToASCII(\"xn--0ug.xn--ss--bi1b\") C1; V3 (ignored)",
"ToASCII(\"xn--0ug.xn----pfa2305a\") C1; V3 (ignored)",
"ToASCII(\"ⴏ󠅋-.‍ⴉ\") C2; V3 (ignored)",
"ToASCII(\"xn----3vs.xn--1ug532c\") C2; V3 (ignored)",
"ToASCII(\"ⴏ󠅋-.‍ⴉ\") C2; V3 (ignored)",
"ToASCII(\"。ⴖͦ.\") C1; A4_2 (ignored)",
"ToASCII(\".xn--hva754s.xn--0ug\") C1; A4_2 (ignored)",
"ToASCII(\"‍攌꯭。ᢖ-ⴘ\") C2",
"ToASCII(\"xn--1ug592ykp6b.xn----mck373i\") C2",
"ToASCII(\"‌ꖨ.16.3툒۳\") C1",
"ToASCII(\"‌ꖨ.16.3툒۳\") C1",
"ToASCII(\"xn--0ug2473c.16.xn--3-nyc0117m\") C1",
"ToASCII(\"𝟏𝨙⸖.\") C2",
"ToASCII(\"1𝨙⸖.\") C2",
"ToASCII(\"xn--1-5bt6845n.xn--1ug\") C2",
"ToASCII(\"-.ⴞ𐋷\") C2; V3 (ignored)",
"ToASCII(\"xn----ugn.xn--mlj8559d\") C2; V3 (ignored)",
"ToASCII(\"嬃𝍌.‍ୄ\") C2",
"ToASCII(\"嬃𝍌.‍ୄ\") C2",
"ToASCII(\"xn--b6s0078f.xn--0ic557h\") C2",
"ToASCII(\".F\") C2",
"ToASCII(\".f\") C2",
"ToASCII(\"xn--1ug.f\") C2",
"ToASCII(\"‍㨲。ß\") C2",
"ToASCII(\"‍㨲。ß\") C2",
"ToASCII(\"㨲。SS\") C2",
"ToASCII(\"㨲。ss\") C2",
"ToASCII(\"㨲。Ss\") C2",
"ToASCII(\"xn--1ug914h.ss\") C2",
"ToASCII(\"xn--1ug914h.xn--zca\") C2",
"ToASCII(\"㨲。SS\") C2",
"ToASCII(\"㨲。ss\") C2",
"ToASCII(\"㨲。Ss\") C2",
"ToASCII(\"璼𝨭。‌󠇟\") C1",
"ToASCII(\"璼𝨭。‌󠇟\") C1",
"ToASCII(\"xn--gky8837e.xn--0ug\") C1",
"ToASCII(\".\") C1",
"ToASCII(\"xn--0ug.xn--0ug\") C1",
"ToASCII(\"𝟠4󠇗𝈻𐋵\") C2",
"ToASCII(\"84󠇗𝈻.‍𐋵⛧‍\") C2",
"ToASCII(\"xn--84-s850a.xn--1uga573cfq1w\") C2",
"ToASCII(\"‍‌󠆪。ß𑓃\") C1; C2",
"ToASCII(\"‍‌󠆪。ß𑓃\") C1; C2",
"ToASCII(\"󠆪。SS𑓃\") C1; C2",
"ToASCII(\"󠆪。ss𑓃\") C1; C2",
"ToASCII(\"󠆪。Ss𑓃\") C1; C2",
"ToASCII(\"xn--0ugb.xn--ss-bh7o\") C1; C2",
"ToASCII(\"xn--0ugb.xn--zca0732l\") C1; C2",
"ToASCII(\"󠆪。SS𑓃\") C1; C2",
"ToASCII(\"󠆪。ss𑓃\") C1; C2",
"ToASCII(\"󠆪。Ss𑓃\") C1; C2",
"ToASCII(\"。‌ヶ䒩.ꡪ\") C1; A4_2 (ignored)",
"ToASCII(\".xn--0ug287dj0o.xn--gd9a\") C1; A4_2 (ignored)",
"ToASCII(\"梉。‌\") C1",
"ToASCII(\"xn--7zv.xn--0ug\") C1",
"ToASCII(\"𐋷。‍\") C2",
"ToASCII(\"xn--r97c.xn--1ug\") C2"
],
"javascript-urls.window.html": false,
"url-constructor.any.html?exclude=(file|javascript|mailto)": [
"Parsing: <non-spec:/.//> against <about:blank>",
"Parsing: <non-spec:/..//> against <about:blank>",
"Parsing: <non-spec:/a/..//> against <about:blank>",
"Parsing: <non-spec:/.//path> against <about:blank>",
"Parsing: <non-spec:/..//path> against <about:blank>",
"Parsing: <non-spec:/a/..//path> against <about:blank>",
"Parsing: </.//path> against <non-spec:/p>",
"Parsing: </..//path> against <non-spec:/p>",
"Parsing: <..//path> against <non-spec:/p>",
"Parsing: <a/..//path> against <non-spec:/p>",
"Parsing: <> against <non-spec:/..//p>",
"Parsing: <path> against <non-spec:/..//p>"
],
"url-constructor.any.html?include=file": [
"Parsing: </> against <file://h/C:/a/b>",
"Parsing: <file:\\\\//> against <about:blank>",
"Parsing: <file:\\\\\\\\> against <about:blank>",
"Parsing: <file:\\\\\\\\?fox> against <about:blank>",
"Parsing: <file:\\\\\\\\#guppy> against <about:blank>",
"Parsing: <file://spider///> against <about:blank>",
"Parsing: <file:\\\\localhost//> against <about:blank>",
"Parsing: <file://\\/localhost//cat> against <about:blank>",
"Parsing: <file://localhost//a//../..//> against <about:blank>",
"Parsing: </////mouse> against <file:///elephant>",
"Parsing: <\\/localhost//pig> against <file://lion/>",
"Parsing: <//localhost//pig> against <file://lion/>",
"Parsing: </..//localhost//pig> against <file://lion/>",
"Parsing: <C|> against <file://host/dir/file>",
"Parsing: <C|> against <file://host/D:/dir1/dir2/file>",
"Parsing: <C|#> against <file://host/dir/file>",
"Parsing: <C|?> against <file://host/dir/file>",
"Parsing: <C|/> against <file://host/dir/file>",
"Parsing: <C|\n/> against <file://host/dir/file>",
"Parsing: <C|\\> against <file://host/dir/file>",
"Parsing: </c:/foo/bar> against <file://host/path>",
"Parsing: <file://example.net/C:/> against <about:blank>",
"Parsing: <file://1.2.3.4/C:/> against <about:blank>",
"Parsing: <file://[1::8]/C:/> against <about:blank>",
"Parsing: <C|/> against <file://host/>",
"Parsing: </C:/> against <file://host/>",
"Parsing: <file:C:/> against <file://host/>",
"Parsing: <file:/C:/> against <file://host/>",
"Parsing: <file://localhost//a//../..//foo> against <about:blank>",
"Parsing: <file://localhost////foo> against <about:blank>",
"Parsing: <file:////foo> against <about:blank>",
"Parsing: <file:////one/two> against <file:///>",
"Parsing: <////one/two> against <file:///>",
"Parsing: <file:///.//> against <file:////>",
"Parsing: <file:.//p> against <about:blank>",
"Parsing: <file:/.//p> against <about:blank>"
],
"url-constructor.any.html?include=javascript": true,
"url-constructor.any.html?include=mailto": true,
"url-constructor.any.worker.html?exclude=(file|javascript|mailto)": [
"Parsing: <non-spec:/.//> against <about:blank>",
"Parsing: <non-spec:/..//> against <about:blank>",
"Parsing: <non-spec:/a/..//> against <about:blank>",
"Parsing: <non-spec:/.//path> against <about:blank>",
"Parsing: <non-spec:/..//path> against <about:blank>",
"Parsing: <non-spec:/a/..//path> against <about:blank>",
"Parsing: </.//path> against <non-spec:/p>",
"Parsing: </..//path> against <non-spec:/p>",
"Parsing: <..//path> against <non-spec:/p>",
"Parsing: <a/..//path> against <non-spec:/p>",
"Parsing: <> against <non-spec:/..//p>",
"Parsing: <path> against <non-spec:/..//p>"
],
"url-constructor.any.worker.html?include=file": [
"Parsing: </> against <file://h/C:/a/b>",
"Parsing: <file:\\\\//> against <about:blank>",
"Parsing: <file:\\\\\\\\> against <about:blank>",
"Parsing: <file:\\\\\\\\?fox> against <about:blank>",
"Parsing: <file:\\\\\\\\#guppy> against <about:blank>",
"Parsing: <file://spider///> against <about:blank>",
"Parsing: <file:\\\\localhost//> against <about:blank>",
"Parsing: <file://\\/localhost//cat> against <about:blank>",
"Parsing: <file://localhost//a//../..//> against <about:blank>",
"Parsing: </////mouse> against <file:///elephant>",
"Parsing: <\\/localhost//pig> against <file://lion/>",
"Parsing: <//localhost//pig> against <file://lion/>",
"Parsing: </..//localhost//pig> against <file://lion/>",
"Parsing: <C|> against <file://host/dir/file>",
"Parsing: <C|> against <file://host/D:/dir1/dir2/file>",
"Parsing: <C|#> against <file://host/dir/file>",
"Parsing: <C|?> against <file://host/dir/file>",
"Parsing: <C|/> against <file://host/dir/file>",
"Parsing: <C|\n/> against <file://host/dir/file>",
"Parsing: <C|\\> against <file://host/dir/file>",
"Parsing: </c:/foo/bar> against <file://host/path>",
"Parsing: <file://example.net/C:/> against <about:blank>",
"Parsing: <file://1.2.3.4/C:/> against <about:blank>",
"Parsing: <file://[1::8]/C:/> against <about:blank>",
"Parsing: <C|/> against <file://host/>",
"Parsing: </C:/> against <file://host/>",
"Parsing: <file:C:/> against <file://host/>",
"Parsing: <file:/C:/> against <file://host/>",
"Parsing: <file://localhost//a//../..//foo> against <about:blank>",
"Parsing: <file://localhost////foo> against <about:blank>",
"Parsing: <file:////foo> against <about:blank>",
"Parsing: <file:////one/two> against <file:///>",
"Parsing: <////one/two> against <file:///>",
"Parsing: <file:///.//> against <file:////>",
"Parsing: <file:.//p> against <about:blank>",
"Parsing: <file:/.//p> against <about:blank>"
],
"url-constructor.any.worker.html?include=javascript": true,
"url-constructor.any.worker.html?include=mailto": true,
"url-setters-a-area.window.html?exclude=(file|javascript|mailto)": {
"ignore": true
},
"url-setters-a-area.window.html?include=file": {
"ignore": true
},
"url-setters-a-area.window.html?include=javascript": {
"ignore": true
},
"url-setters-a-area.window.html?include=mailto": {
"ignore": true
},
"url-setters.any.html?exclude=(file|javascript|mailto)": [
"URL: Setting <http://test/>.protocol = 'https\u0000' Non-tab/newline C0 controls result in no-op",
"URL: Setting <http://test/>.protocol = 'https\f'",
"URL: Setting <http://test/>.protocol = 'https\u000e'",
"URL: Setting <http://test/>.protocol = 'https '",
"URL: Setting <http://example.net/path>.hostname = 'example.com:8080' : delimiter invalidates entire value",
"URL: Setting <http://example.net:8080/path>.hostname = 'example.com:' : delimiter invalidates entire value",
"URL: Setting <non-spec:/.//p>.hostname = 'h' Drop /. from path",
"URL: Setting <non-spec:/.//p>.hostname = ''",
"URL: Setting <http://example.net:8080/path>.port = 'randomstring' Setting port to a string that doesn't parse as a number",
"URL: Setting <foo://somehost/some/path>.pathname = '' Non-special URLs can have their paths erased",
"URL: Setting <foo:///some/path>.pathname = '' Non-special URLs with an empty host can have their paths erased",
"URL: Setting <non-spec:/>.pathname = '/.//p' Serialize /. in path",
"URL: Setting <non-spec:/>.pathname = '/..//p'",
"URL: Setting <non-spec:/>.pathname = '//p'",
"URL: Setting <non-spec:/.//>.pathname = 'p' Drop /. from path",
"URL: Setting <data:/nospace>.pathname = 'space ' Non-special URLs with non-opaque paths percent-encode U+0020",
"URL: Setting <sc:/nospace>.pathname = 'space '",
"URL: Setting <data:space ?query>.search = '' Drop trailing spaces from trailing opaque paths",
"URL: Setting <sc:space ?query>.search = ''",
"URL: Setting <data:space #fragment>.hash = '' Drop trailing spaces from trailing opaque paths",
"URL: Setting <sc:space #fragment>.hash = ''"
],
"url-setters.any.html?include=file": [
"URL: Setting <file://monkey/>.pathname = '\\\\' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//\\/' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//monkey/..//' File URLs and (back)slashes"
],
"url-setters.any.html?include=javascript": true,
"url-setters.any.html?include=mailto": true,
"url-setters.any.worker.html?exclude=(file|javascript|mailto)": [
"URL: Setting <http://test/>.protocol = 'https\u0000' Non-tab/newline C0 controls result in no-op",
"URL: Setting <http://test/>.protocol = 'https\f'",
"URL: Setting <http://test/>.protocol = 'https\u000e'",
"URL: Setting <http://test/>.protocol = 'https '",
"URL: Setting <http://example.net/path>.hostname = 'example.com:8080' : delimiter invalidates entire value",
"URL: Setting <http://example.net:8080/path>.hostname = 'example.com:' : delimiter invalidates entire value",
"URL: Setting <non-spec:/.//p>.hostname = 'h' Drop /. from path",
"URL: Setting <non-spec:/.//p>.hostname = ''",
"URL: Setting <http://example.net:8080/path>.port = 'randomstring' Setting port to a string that doesn't parse as a number",
"URL: Setting <foo://somehost/some/path>.pathname = '' Non-special URLs can have their paths erased",
"URL: Setting <foo:///some/path>.pathname = '' Non-special URLs with an empty host can have their paths erased",
"URL: Setting <non-spec:/>.pathname = '/.//p' Serialize /. in path",
"URL: Setting <non-spec:/>.pathname = '/..//p'",
"URL: Setting <non-spec:/>.pathname = '//p'",
"URL: Setting <non-spec:/.//>.pathname = 'p' Drop /. from path",
"URL: Setting <data:/nospace>.pathname = 'space ' Non-special URLs with non-opaque paths percent-encode U+0020",
"URL: Setting <sc:/nospace>.pathname = 'space '",
"URL: Setting <data:space ?query>.search = '' Drop trailing spaces from trailing opaque paths",
"URL: Setting <sc:space ?query>.search = ''",
"URL: Setting <data:space #fragment>.hash = '' Drop trailing spaces from trailing opaque paths",
"URL: Setting <sc:space #fragment>.hash = ''"
],
"url-setters.any.worker.html?include=file": [
"URL: Setting <file://monkey/>.pathname = '\\\\' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//\\/' File URLs and (back)slashes",
"URL: Setting <file:///unicorn>.pathname = '//monkey/..//' File URLs and (back)slashes"
],
"url-setters.any.worker.html?include=javascript": true,
"url-setters.any.worker.html?include=mailto": true,
2023-04-04 07:34:12 -04:00
"url-statics-canparse.any.html": true,
"url-statics-canparse.any.worker.html": true,
"urlsearchparams-size.any.worker.html": true
},
"fetch": {
"api": {
"request": {
2021-05-09 10:32:30 -04:00
"request-init-002.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-init-002.any.worker.html": true,
2022-09-22 05:07:50 -04:00
"request-init-stream.any.html": [
"It is error to omit .duplex when the body is a ReadableStream.",
"It is error to set .duplex = 'full' when the body is null.",
"It is error to set .duplex = 'full' when the body is a string.",
"It is error to set .duplex = 'full' when the body is a Uint8Array.",
"It is error to set .duplex = 'full' when the body is a Blob.",
"It is error to set .duplex = 'full' when the body is a ReadableStream."
],
"request-init-stream.any.worker.html": [
"It is error to omit .duplex when the body is a ReadableStream.",
"It is error to set .duplex = 'full' when the body is null.",
"It is error to set .duplex = 'full' when the body is a string.",
"It is error to set .duplex = 'full' when the body is a Uint8Array.",
"It is error to set .duplex = 'full' when the body is a Blob.",
"It is error to set .duplex = 'full' when the body is a ReadableStream."
],
2021-05-09 10:32:30 -04:00
"request-consume-empty.any.html": [
"Consume empty FormData request body as text"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-consume-empty.any.worker.html": [
"Consume empty FormData request body as text"
],
2021-08-09 12:49:31 -04:00
"request-consume.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-consume.any.worker.html": true,
2021-08-09 12:49:31 -04:00
"request-disturbed.any.html": [
"Input request used for creating new request became disturbed even if body is not used"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-disturbed.any.worker.html": [
"Input request used for creating new request became disturbed even if body is not used"
],
2021-08-09 12:49:31 -04:00
"request-error.any.html": [
"RequestInit's window is not null",
"Input URL has credentials",
"RequestInit's mode is navigate",
"RequestInit's referrer is invalid",
"RequestInit's mode is no-cors and method is not simple",
"RequestInit's cache mode is only-if-cached and mode is not same-origin",
"Request with cache mode: only-if-cached and fetch mode cors",
"Request with cache mode: only-if-cached and fetch mode no-cors",
"Bad referrerPolicy init parameter value",
"Bad mode init parameter value",
"Bad credentials init parameter value",
"Bad cache init parameter value"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-error.any.worker.html": [
"RequestInit's window is not null",
"Input URL has credentials",
"RequestInit's mode is navigate",
"RequestInit's referrer is invalid",
"RequestInit's mode is no-cors and method is not simple",
"RequestInit's cache mode is only-if-cached and mode is not same-origin",
"Request with cache mode: only-if-cached and fetch mode cors",
"Request with cache mode: only-if-cached and fetch mode no-cors",
"Bad referrerPolicy init parameter value",
"Bad mode init parameter value",
"Bad credentials init parameter value",
"Bad cache init parameter value"
],
2021-08-09 12:49:31 -04:00
"request-headers.any.html": [
"Adding invalid request header \"Accept-Charset: KO\"",
"Adding invalid request header \"accept-charset: KO\"",
"Adding invalid request header \"ACCEPT-ENCODING: KO\"",
"Adding invalid request header \"Accept-Encoding: KO\"",
"Adding invalid request header \"Access-Control-Request-Headers: KO\"",
"Adding invalid request header \"Access-Control-Request-Method: KO\"",
"Adding invalid request header \"Access-Control-Request-Private-Network: KO\"",
2021-08-09 12:49:31 -04:00
"Adding invalid request header \"Connection: KO\"",
"Adding invalid request header \"Content-Length: KO\"",
"Adding invalid request header \"Cookie: KO\"",
"Adding invalid request header \"Cookie2: KO\"",
"Adding invalid request header \"Date: KO\"",
"Adding invalid request header \"DNT: KO\"",
"Adding invalid request header \"Expect: KO\"",
"Adding invalid request header \"Host: KO\"",
"Adding invalid request header \"Keep-Alive: KO\"",
"Adding invalid request header \"Origin: KO\"",
"Adding invalid request header \"Referer: KO\"",
2022-09-22 05:07:50 -04:00
"Adding invalid request header \"Set-Cookie: KO\"",
2021-08-09 12:49:31 -04:00
"Adding invalid request header \"TE: KO\"",
"Adding invalid request header \"Trailer: KO\"",
"Adding invalid request header \"Transfer-Encoding: KO\"",
"Adding invalid request header \"Upgrade: KO\"",
"Adding invalid request header \"Via: KO\"",
"Adding invalid request header \"Proxy-: KO\"",
"Adding invalid request header \"proxy-a: KO\"",
"Adding invalid request header \"Sec-: KO\"",
"Adding invalid request header \"sec-b: KO\"",
"Adding invalid no-cors request header \"Content-Type: KO\"",
"Adding invalid no-cors request header \"Potato: KO\"",
"Adding invalid no-cors request header \"proxy: KO\"",
"Adding invalid no-cors request header \"proxya: KO\"",
"Adding invalid no-cors request header \"sec: KO\"",
"Adding invalid no-cors request header \"secb: KO\"",
"Adding invalid no-cors request header \"Empty-Value: \"",
2021-08-09 12:49:31 -04:00
"Check that request constructor is filtering headers provided as init parameter",
"Check that no-cors request constructor is filtering headers provided as init parameter",
"Check that no-cors request constructor is filtering headers provided as part of request parameter"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-headers.any.worker.html": [
"Adding invalid request header \"Accept-Charset: KO\"",
"Adding invalid request header \"accept-charset: KO\"",
"Adding invalid request header \"ACCEPT-ENCODING: KO\"",
"Adding invalid request header \"Accept-Encoding: KO\"",
"Adding invalid request header \"Access-Control-Request-Headers: KO\"",
"Adding invalid request header \"Access-Control-Request-Method: KO\"",
"Adding invalid request header \"Access-Control-Request-Private-Network: KO\"",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Adding invalid request header \"Connection: KO\"",
"Adding invalid request header \"Content-Length: KO\"",
"Adding invalid request header \"Cookie: KO\"",
"Adding invalid request header \"Cookie2: KO\"",
"Adding invalid request header \"Date: KO\"",
"Adding invalid request header \"DNT: KO\"",
"Adding invalid request header \"Expect: KO\"",
"Adding invalid request header \"Host: KO\"",
"Adding invalid request header \"Keep-Alive: KO\"",
"Adding invalid request header \"Origin: KO\"",
"Adding invalid request header \"Referer: KO\"",
2022-09-22 05:07:50 -04:00
"Adding invalid request header \"Set-Cookie: KO\"",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Adding invalid request header \"TE: KO\"",
"Adding invalid request header \"Trailer: KO\"",
"Adding invalid request header \"Transfer-Encoding: KO\"",
"Adding invalid request header \"Upgrade: KO\"",
"Adding invalid request header \"Via: KO\"",
"Adding invalid request header \"Proxy-: KO\"",
"Adding invalid request header \"proxy-a: KO\"",
"Adding invalid request header \"Sec-: KO\"",
"Adding invalid request header \"sec-b: KO\"",
"Adding invalid no-cors request header \"Content-Type: KO\"",
"Adding invalid no-cors request header \"Potato: KO\"",
"Adding invalid no-cors request header \"proxy: KO\"",
"Adding invalid no-cors request header \"proxya: KO\"",
"Adding invalid no-cors request header \"sec: KO\"",
"Adding invalid no-cors request header \"secb: KO\"",
"Adding invalid no-cors request header \"Empty-Value: \"",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Check that request constructor is filtering headers provided as init parameter",
"Check that no-cors request constructor is filtering headers provided as init parameter",
"Check that no-cors request constructor is filtering headers provided as part of request parameter"
],
2021-08-09 12:49:31 -04:00
"request-init-contenttype.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-init-contenttype.any.worker.html": true,
2021-08-09 12:49:31 -04:00
"request-structure.any.html": [
"Check destination attribute",
"Check referrer attribute",
"Check referrerPolicy attribute",
"Check mode attribute",
"Check credentials attribute",
"Check cache attribute",
"Check integrity attribute",
"Check isReloadNavigation attribute",
"Check isHistoryNavigation attribute",
"Check duplex attribute"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"request-structure.any.worker.html": [
"Check destination attribute",
"Check referrer attribute",
"Check referrerPolicy attribute",
"Check mode attribute",
"Check credentials attribute",
"Check cache attribute",
"Check integrity attribute",
"Check isReloadNavigation attribute",
"Check isHistoryNavigation attribute",
"Check duplex attribute"
],
"forbidden-method.any.html": true,
"forbidden-method.any.worker.html": true,
"request-bad-port.any.html": false,
"request-bad-port.any.worker.html": false,
"request-cache-default-conditional.any.html": true,
"request-cache-default-conditional.any.worker.html": true,
"request-cache-default.any.html": [
"RequestCache \"default\" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Etag and fresh response",
"RequestCache \"default\" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Last-Modified and fresh response"
],
"request-cache-default.any.worker.html": [
"RequestCache \"default\" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Etag and fresh response",
"RequestCache \"default\" mode checks the cache for previously cached content and avoids going to the network if a fresh response exists with Last-Modified and fresh response"
],
"request-cache-force-cache.any.html": [
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for stale responses with Etag and stale response",
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for stale responses with Last-Modified and stale response",
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Etag and fresh response",
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Last-Modified and fresh response",
"RequestCache \"force-cache\" stores the response in the cache if it goes to the network with Etag and fresh response",
"RequestCache \"force-cache\" stores the response in the cache if it goes to the network with Last-Modified and fresh response"
],
"request-cache-force-cache.any.worker.html": [
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for stale responses with Etag and stale response",
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for stale responses with Last-Modified and stale response",
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Etag and fresh response",
"RequestCache \"force-cache\" mode checks the cache for previously cached content and avoid revalidation for fresh responses with Last-Modified and fresh response",
"RequestCache \"force-cache\" stores the response in the cache if it goes to the network with Etag and fresh response",
"RequestCache \"force-cache\" stores the response in the cache if it goes to the network with Last-Modified and fresh response"
],
"request-cache-no-cache.any.html": true,
"request-cache-no-cache.any.worker.html": true,
"request-cache-no-store.any.html": true,
"request-cache-no-store.any.worker.html": true,
"request-cache-only-if-cached.any.html": false,
"request-cache-only-if-cached.any.worker.html": false,
"request-cache-reload.any.html": [
"RequestCache \"reload\" mode does store the response in the cache with Etag and fresh response",
"RequestCache \"reload\" mode does store the response in the cache with Last-Modified and fresh response",
"RequestCache \"reload\" mode does store the response in the cache even if a previous response is already stored with Etag and fresh response",
"RequestCache \"reload\" mode does store the response in the cache even if a previous response is already stored with Last-Modified and fresh response"
],
"request-cache-reload.any.worker.html": [
"RequestCache \"reload\" mode does store the response in the cache with Etag and fresh response",
"RequestCache \"reload\" mode does store the response in the cache with Last-Modified and fresh response",
"RequestCache \"reload\" mode does store the response in the cache even if a previous response is already stored with Etag and fresh response",
"RequestCache \"reload\" mode does store the response in the cache even if a previous response is already stored with Last-Modified and fresh response"
],
"request-init-priority.any.html": [
"new Request() throws a TypeError if any of RequestInit's members' values are invalid",
"fetch() with an invalid priority returns a rejected promise with a TypeError"
],
"request-init-priority.any.worker.html": [
"new Request() throws a TypeError if any of RequestInit's members' values are invalid",
"fetch() with an invalid priority returns a rejected promise with a TypeError"
],
"request-keepalive.any.html": false,
"request-keepalive.any.worker.html": false
},
"headers": {
"header-values-normalize.any.html": [
"XMLHttpRequest with value %00",
"XMLHttpRequest with value %01",
"XMLHttpRequest with value %02",
"XMLHttpRequest with value %03",
"XMLHttpRequest with value %04",
"XMLHttpRequest with value %05",
"XMLHttpRequest with value %06",
"XMLHttpRequest with value %07",
"XMLHttpRequest with value %08",
"XMLHttpRequest with value %09",
"XMLHttpRequest with value %0A",
"XMLHttpRequest with value %0D",
"XMLHttpRequest with value %0E",
"XMLHttpRequest with value %0F",
"XMLHttpRequest with value %10",
"XMLHttpRequest with value %11",
"XMLHttpRequest with value %12",
"XMLHttpRequest with value %13",
"XMLHttpRequest with value %14",
"XMLHttpRequest with value %15",
"XMLHttpRequest with value %16",
"XMLHttpRequest with value %17",
"XMLHttpRequest with value %18",
"XMLHttpRequest with value %19",
"XMLHttpRequest with value %1A",
"XMLHttpRequest with value %1B",
"XMLHttpRequest with value %1C",
"XMLHttpRequest with value %1D",
"XMLHttpRequest with value %1E",
"XMLHttpRequest with value %1F",
"XMLHttpRequest with value %20",
"fetch() with value %01",
"fetch() with value %02",
"fetch() with value %03",
"fetch() with value %04",
"fetch() with value %05",
"fetch() with value %06",
"fetch() with value %07",
"fetch() with value %08",
"fetch() with value %0E",
"fetch() with value %0F",
"fetch() with value %10",
"fetch() with value %11",
"fetch() with value %12",
"fetch() with value %13",
"fetch() with value %14",
"fetch() with value %15",
"fetch() with value %16",
"fetch() with value %17",
"fetch() with value %18",
"fetch() with value %19",
"fetch() with value %1A",
"fetch() with value %1B",
"fetch() with value %1C",
"fetch() with value %1D",
"fetch() with value %1E",
"fetch() with value %1F"
],
"header-values-normalize.any.worker.html": [
"fetch() with value %01",
"fetch() with value %02",
"fetch() with value %03",
"fetch() with value %04",
"fetch() with value %05",
"fetch() with value %06",
"fetch() with value %07",
"fetch() with value %08",
"fetch() with value %0E",
"fetch() with value %0F",
"fetch() with value %10",
"fetch() with value %11",
"fetch() with value %12",
"fetch() with value %13",
"fetch() with value %14",
"fetch() with value %15",
"fetch() with value %16",
"fetch() with value %17",
"fetch() with value %18",
"fetch() with value %19",
"fetch() with value %1A",
"fetch() with value %1B",
"fetch() with value %1C",
"fetch() with value %1D",
"fetch() with value %1E",
"fetch() with value %1F"
],
"header-values.any.html": [
"XMLHttpRequest with value x%00x needs to throw",
"XMLHttpRequest with value x%0Ax needs to throw",
"XMLHttpRequest with value x%0Dx needs to throw",
"XMLHttpRequest with all valid values",
"fetch() with all valid values"
],
"header-values.any.worker.html": [
"fetch() with all valid values"
],
2021-05-09 10:32:30 -04:00
"headers-basic.any.html": true,
"headers-casing.any.html": true,
"headers-combine.any.html": true,
"headers-errors.any.html": true,
"headers-normalize.any.html": true,
"headers-record.any.html": true,
"headers-structure.any.html": true,
"headers-basic.any.worker.html": true,
"headers-casing.any.worker.html": true,
"headers-combine.any.worker.html": true,
"headers-errors.any.worker.html": true,
"headers-no-cors.any.html": [
"\"no-cors\" Headers object cannot have accept set to sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have accept-language set to sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have content-language set to sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have accept set to , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have accept-language set to , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have content-language set to , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have content-type set to text/plain;ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, text/plain",
"\"no-cors\" Headers object cannot have accept/\" as header",
"\"no-cors\" Headers object cannot have accept/012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 as header",
"\"no-cors\" Headers object cannot have accept-language/\u0001 as header",
"\"no-cors\" Headers object cannot have accept-language/@ as header",
"\"no-cors\" Headers object cannot have authorization/basics as header",
"\"no-cors\" Headers object cannot have content-language/\u0001 as header",
"\"no-cors\" Headers object cannot have content-language/@ as header",
"\"no-cors\" Headers object cannot have content-type/text/html as header",
"\"no-cors\" Headers object cannot have content-type/text/plain; long=0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 as header",
"\"no-cors\" Headers object cannot have range/bytes 0- as header",
"\"no-cors\" Headers object cannot have test/hi as header",
"\"no-cors\" Headers object cannot have dpr/2 as header",
"\"no-cors\" Headers object cannot have rtt/1.0 as header",
"\"no-cors\" Headers object cannot have downlink/-1.0 as header",
"\"no-cors\" Headers object cannot have ect/6g as header",
"\"no-cors\" Headers object cannot have save-data/on as header",
"\"no-cors\" Headers object cannot have viewport-width/100 as header",
"\"no-cors\" Headers object cannot have width/100 as header",
"\"no-cors\" Headers object cannot have unknown/doesitmatter as header"
],
"headers-no-cors.any.worker.html": [
"\"no-cors\" Headers object cannot have accept set to sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have accept-language set to sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have content-language set to sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have accept set to , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have accept-language set to , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have content-language set to , sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss",
"\"no-cors\" Headers object cannot have content-type set to text/plain;ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss, text/plain",
"\"no-cors\" Headers object cannot have accept/\" as header",
"\"no-cors\" Headers object cannot have accept/012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 as header",
"\"no-cors\" Headers object cannot have accept-language/\u0001 as header",
"\"no-cors\" Headers object cannot have accept-language/@ as header",
"\"no-cors\" Headers object cannot have authorization/basics as header",
"\"no-cors\" Headers object cannot have content-language/\u0001 as header",
"\"no-cors\" Headers object cannot have content-language/@ as header",
"\"no-cors\" Headers object cannot have content-type/text/html as header",
"\"no-cors\" Headers object cannot have content-type/text/plain; long=0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 as header",
"\"no-cors\" Headers object cannot have range/bytes 0- as header",
"\"no-cors\" Headers object cannot have test/hi as header",
"\"no-cors\" Headers object cannot have dpr/2 as header",
"\"no-cors\" Headers object cannot have rtt/1.0 as header",
"\"no-cors\" Headers object cannot have downlink/-1.0 as header",
"\"no-cors\" Headers object cannot have ect/6g as header",
"\"no-cors\" Headers object cannot have save-data/on as header",
"\"no-cors\" Headers object cannot have viewport-width/100 as header",
"\"no-cors\" Headers object cannot have width/100 as header",
"\"no-cors\" Headers object cannot have unknown/doesitmatter as header"
],
"headers-normalize.any.worker.html": true,
"headers-record.any.worker.html": true,
"headers-structure.any.worker.html": true,
"header-setcookie.any.html": [
"Headers.prototype.getSetCookie with no headers present",
"Headers.prototype.getSetCookie with one header",
"Headers.prototype.getSetCookie with one header created from an object",
"Headers.prototype.getSetCookie with multiple headers",
"Headers.prototype.getSetCookie with an empty header",
"Headers.prototype.getSetCookie with two equal headers",
"Headers.prototype.getSetCookie ignores set-cookie2 headers",
"Headers.prototype.getSetCookie preserves header ordering",
"Set-Cookie is a forbidden response header"
],
"header-setcookie.any.worker.html": [
"Headers.prototype.getSetCookie with no headers present",
"Headers.prototype.getSetCookie with one header",
"Headers.prototype.getSetCookie with one header created from an object",
"Headers.prototype.getSetCookie with multiple headers",
"Headers.prototype.getSetCookie with an empty header",
"Headers.prototype.getSetCookie with two equal headers",
"Headers.prototype.getSetCookie ignores set-cookie2 headers",
"Headers.prototype.getSetCookie preserves header ordering",
"Set-Cookie is a forbidden response header"
]
},
"basic": {
2021-05-09 10:32:30 -04:00
"request-head.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-head.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"request-headers-case.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-headers-case.any.worker.html": false,
"request-headers-nonascii.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-headers-nonascii.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"request-headers.any.html": [
"Fetch with PUT without body",
"Fetch with PUT with body",
"Fetch with POST without body",
"Fetch with POST with text body",
"Fetch with POST with FormData body",
"Fetch with POST with URLSearchParams body",
"Fetch with POST with Blob body",
"Fetch with POST with ArrayBuffer body",
"Fetch with POST with Uint8Array body",
"Fetch with POST with Int8Array body",
"Fetch with POST with Float32Array body",
"Fetch with POST with Float64Array body",
"Fetch with POST with DataView body",
"Fetch with POST with Blob body with mime type",
"Fetch with Chicken",
"Fetch with Chicken with body",
"Fetch with POST and mode \"same-origin\" needs an Origin header",
"Fetch with POST and mode \"no-cors\" needs an Origin header",
"Fetch with PUT and mode \"same-origin\" needs an Origin header",
"Fetch with TacO and mode \"same-origin\" needs an Origin header",
"Fetch with TacO and mode \"cors\" needs an Origin header"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-headers.any.worker.html": [
"Fetch with PUT without body",
"Fetch with PUT with body",
"Fetch with POST without body",
"Fetch with POST with text body",
"Fetch with POST with FormData body",
"Fetch with POST with URLSearchParams body",
"Fetch with POST with Blob body",
"Fetch with POST with ArrayBuffer body",
"Fetch with POST with Uint8Array body",
"Fetch with POST with Int8Array body",
"Fetch with POST with Float32Array body",
"Fetch with POST with Float64Array body",
"Fetch with POST with DataView body",
"Fetch with POST with Blob body with mime type",
"Fetch with Chicken",
"Fetch with Chicken with body",
"Fetch with POST and mode \"same-origin\" needs an Origin header",
"Fetch with POST and mode \"no-cors\" needs an Origin header",
"Fetch with PUT and mode \"same-origin\" needs an Origin header",
"Fetch with TacO and mode \"same-origin\" needs an Origin header",
"Fetch with TacO and mode \"cors\" needs an Origin header"
],
2021-05-09 10:32:30 -04:00
"text-utf8.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"text-utf8.any.worker.html": true,
"accept-header.any.html": true,
"accept-header.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"conditional-get.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"conditional-get.any.worker.html": false,
"error-after-response.any.html": {
"ignore": true
},
2021-05-09 10:32:30 -04:00
"header-value-combining.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"header-value-combining.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"header-value-null-byte.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"header-value-null-byte.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"historical.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"historical.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"http-response-code.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"http-response-code.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"request-upload.any.html": [
"Fetch with POST with ReadableStream containing String",
"Fetch with POST with ReadableStream containing null",
"Fetch with POST with ReadableStream containing number",
"Fetch with POST with ReadableStream containing ArrayBuffer",
"Fetch with POST with ReadableStream containing Blob",
"Fetch with POST with text body on 421 response should be retried once on new connection."
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"request-upload.any.worker.html": [
"Fetch with POST with ReadableStream containing String",
"Fetch with POST with ReadableStream containing null",
"Fetch with POST with ReadableStream containing number",
"Fetch with POST with ReadableStream containing ArrayBuffer",
"Fetch with POST with ReadableStream containing Blob",
"Fetch with POST with text body on 421 response should be retried once on new connection."
],
"response-null-body.any.worker.html": {
"ignore": true
},
2021-05-09 10:32:30 -04:00
"response-url.sub.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-url.sub.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"scheme-about.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"scheme-about.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"scheme-blob.sub.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"scheme-blob.sub.any.worker.html": true,
"scheme-data.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"scheme-data.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"scheme-others.sub.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"scheme-others.sub.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"stream-response.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"stream-response.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"stream-safe-creation.any.html": [
"throwing Object.prototype.start accessor should not affect stream creation by 'fetch'",
"Object.prototype.start accessor returning invalid value should not affect stream creation by 'fetch'"
2021-08-09 12:49:31 -04:00
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"stream-safe-creation.any.worker.html": [
"throwing Object.prototype.start accessor should not affect stream creation by 'fetch'",
"Object.prototype.start accessor returning invalid value should not affect stream creation by 'fetch'"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
2021-08-09 12:49:31 -04:00
"integrity.sub.any.html": [
"Invalid integrity",
"Multiple integrities: invalid stronger than valid",
"Multiple integrities: both are invalid",
"CORS invalid integrity",
"Empty string integrity for opaque response",
"SHA-* integrity for opaque response"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"integrity.sub.any.worker.html": [
"Invalid integrity",
"Multiple integrities: invalid stronger than valid",
"Multiple integrities: both are invalid",
"CORS invalid integrity",
"Empty string integrity for opaque response",
"SHA-* integrity for opaque response"
],
"error-after-response.any.worker.html": false,
"keepalive.any.html": false,
"mediasource.window.html": false,
"mode-no-cors.sub.any.html": {
"ignore": true
},
"mode-no-cors.sub.any.worker.html": {
"ignore": true
},
"mode-same-origin.any.html": [
"Fetch https://web-platform.test:8443/fetch/api/resources/top.txt with same-origin mode",
"Fetch http://www1.web-platform.test:8000/fetch/api/resources/top.txt with same-origin mode",
"Fetch /fetch/api/basic/../resources/redirect.py?location=https://web-platform.test:8443/fetch/api/resources/top.txt with same-origin mode",
"Fetch /fetch/api/basic/../resources/redirect.py?location=http://www1.web-platform.test:8000/fetch/api/resources/top.txt with same-origin mode"
],
"mode-same-origin.any.worker.html": [
"Fetch https://web-platform.test:8443/fetch/api/resources/top.txt with same-origin mode",
"Fetch http://www1.web-platform.test:8000/fetch/api/resources/top.txt with same-origin mode",
"Fetch /fetch/api/basic/../resources/redirect.py?location=https://web-platform.test:8443/fetch/api/resources/top.txt with same-origin mode",
"Fetch /fetch/api/basic/../resources/redirect.py?location=http://www1.web-platform.test:8000/fetch/api/resources/top.txt with same-origin mode"
],
"referrer.any.html": false,
"referrer.any.worker.html": false,
"request-forbidden-headers.any.html": [
"Accept-Charset is a forbidden request header",
"Accept-Encoding is a forbidden request header",
"Access-Control-Request-Headers is a forbidden request header",
"Access-Control-Request-Method is a forbidden request header",
"Access-Control-Request-Private-Network is a forbidden request header",
"Connection is a forbidden request header",
"Cookie is a forbidden request header",
"Cookie2 is a forbidden request header",
"Date is a forbidden request header",
"DNT is a forbidden request header",
"Expect is a forbidden request header",
"Keep-Alive is a forbidden request header",
"Origin is a forbidden request header",
"Referer is a forbidden request header",
"TE is a forbidden request header",
"Trailer is a forbidden request header",
"Upgrade is a forbidden request header",
"Via is a forbidden request header",
"Proxy- is a forbidden request header",
"Proxy-Test is a forbidden request header",
"Sec- is a forbidden request header",
"Sec-Test is a forbidden request header",
"header x-http-method-override is forbidden to use value TRACE",
"header x-http-method is forbidden to use value TRACE",
"header x-method-override is forbidden to use value TRACE",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value TRACE",
"header X-HTTP-METHOD is forbidden to use value TRACE",
"header X-METHOD-OVERRIDE is forbidden to use value TRACE",
"header x-http-method-override is forbidden to use value TRACK",
"header x-http-method is forbidden to use value TRACK",
"header x-method-override is forbidden to use value TRACK",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value TRACK",
"header X-HTTP-METHOD is forbidden to use value TRACK",
"header X-METHOD-OVERRIDE is forbidden to use value TRACK",
"header x-http-method-override is forbidden to use value CONNECT",
"header x-http-method is forbidden to use value CONNECT",
"header x-method-override is forbidden to use value CONNECT",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value CONNECT",
"header X-HTTP-METHOD is forbidden to use value CONNECT",
"header X-METHOD-OVERRIDE is forbidden to use value CONNECT",
"header x-http-method-override is forbidden to use value trace",
"header x-http-method is forbidden to use value trace",
"header x-method-override is forbidden to use value trace",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value trace",
"header X-HTTP-METHOD is forbidden to use value trace",
"header X-METHOD-OVERRIDE is forbidden to use value trace",
"header x-http-method-override is forbidden to use value track",
"header x-http-method is forbidden to use value track",
"header x-method-override is forbidden to use value track",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value track",
"header X-HTTP-METHOD is forbidden to use value track",
"header X-METHOD-OVERRIDE is forbidden to use value track",
"header x-http-method-override is forbidden to use value connect",
"header x-http-method is forbidden to use value connect",
"header x-method-override is forbidden to use value connect",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value connect",
"header X-HTTP-METHOD is forbidden to use value connect",
"header X-METHOD-OVERRIDE is forbidden to use value connect",
"header x-http-method-override is forbidden to use value trace,",
"header x-http-method is forbidden to use value trace,",
"header x-method-override is forbidden to use value trace,",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value trace,",
"header X-HTTP-METHOD is forbidden to use value trace,",
"header X-METHOD-OVERRIDE is forbidden to use value trace,"
],
"request-forbidden-headers.any.worker.html": [
"Accept-Charset is a forbidden request header",
"Accept-Encoding is a forbidden request header",
"Access-Control-Request-Headers is a forbidden request header",
"Access-Control-Request-Method is a forbidden request header",
"Access-Control-Request-Private-Network is a forbidden request header",
"Connection is a forbidden request header",
"Cookie is a forbidden request header",
"Cookie2 is a forbidden request header",
"Date is a forbidden request header",
"DNT is a forbidden request header",
"Expect is a forbidden request header",
"Keep-Alive is a forbidden request header",
"Origin is a forbidden request header",
"Referer is a forbidden request header",
"TE is a forbidden request header",
"Trailer is a forbidden request header",
"Upgrade is a forbidden request header",
"Via is a forbidden request header",
"Proxy- is a forbidden request header",
"Proxy-Test is a forbidden request header",
"Sec- is a forbidden request header",
"Sec-Test is a forbidden request header",
"header x-http-method-override is forbidden to use value TRACE",
"header x-http-method is forbidden to use value TRACE",
"header x-method-override is forbidden to use value TRACE",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value TRACE",
"header X-HTTP-METHOD is forbidden to use value TRACE",
"header X-METHOD-OVERRIDE is forbidden to use value TRACE",
"header x-http-method-override is forbidden to use value TRACK",
"header x-http-method is forbidden to use value TRACK",
"header x-method-override is forbidden to use value TRACK",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value TRACK",
"header X-HTTP-METHOD is forbidden to use value TRACK",
"header X-METHOD-OVERRIDE is forbidden to use value TRACK",
"header x-http-method-override is forbidden to use value CONNECT",
"header x-http-method is forbidden to use value CONNECT",
"header x-method-override is forbidden to use value CONNECT",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value CONNECT",
"header X-HTTP-METHOD is forbidden to use value CONNECT",
"header X-METHOD-OVERRIDE is forbidden to use value CONNECT",
"header x-http-method-override is forbidden to use value trace",
"header x-http-method is forbidden to use value trace",
"header x-method-override is forbidden to use value trace",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value trace",
"header X-HTTP-METHOD is forbidden to use value trace",
"header X-METHOD-OVERRIDE is forbidden to use value trace",
"header x-http-method-override is forbidden to use value track",
"header x-http-method is forbidden to use value track",
"header x-method-override is forbidden to use value track",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value track",
"header X-HTTP-METHOD is forbidden to use value track",
"header X-METHOD-OVERRIDE is forbidden to use value track",
"header x-http-method-override is forbidden to use value connect",
"header x-http-method is forbidden to use value connect",
"header x-method-override is forbidden to use value connect",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value connect",
"header X-HTTP-METHOD is forbidden to use value connect",
"header X-METHOD-OVERRIDE is forbidden to use value connect",
"header x-http-method-override is forbidden to use value trace,",
"header x-http-method is forbidden to use value trace,",
"header x-method-override is forbidden to use value trace,",
"header X-HTTP-METHOD-OVERRIDE is forbidden to use value trace,",
"header X-HTTP-METHOD is forbidden to use value trace,",
"header X-METHOD-OVERRIDE is forbidden to use value trace,"
],
"request-referrer.any.html": false,
"request-referrer.any.worker.html": false,
"response-null-body.any.html": true
},
"response": {
2021-05-09 10:32:30 -04:00
"json.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"json.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-init-001.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-init-001.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-init-002.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-init-002.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-static-error.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-static-error.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-static-redirect.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-static-redirect.any.worker.html": true,
"response-stream-bad-chunk.any.html": true,
"response-stream-bad-chunk.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-1.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-1.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-2.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-2.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-3.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-3.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-4.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-4.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-5.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-5.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-6.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-6.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-disturbed-by-pipe.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-disturbed-by-pipe.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-stream-with-broken-then.any.html": [
"Attempt to inject {done: false, value: bye} via Object.prototype.then.",
"Attempt to inject value: undefined via Object.prototype.then.",
"Attempt to inject undefined via Object.prototype.then.",
"Attempt to inject 8.2 via Object.prototype.then.",
"intercepting arraybuffer to text conversion via Object.prototype.then should not be possible"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-stream-with-broken-then.any.worker.html": [
"Attempt to inject {done: false, value: bye} via Object.prototype.then.",
"Attempt to inject value: undefined via Object.prototype.then.",
"Attempt to inject undefined via Object.prototype.then.",
"Attempt to inject 8.2 via Object.prototype.then.",
"intercepting arraybuffer to text conversion via Object.prototype.then should not be possible"
],
2021-05-09 10:32:30 -04:00
"response-error-from-stream.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-error-from-stream.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-error.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-error.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-from-stream.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-from-stream.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-cancel-stream.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-cancel-stream.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"response-clone.any.html": [
"Check response clone use structureClone for teed ReadableStreams (Int8Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Int16Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Int32Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (ArrayBufferchunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint8Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint8ClampedArraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint16Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint32Arraychunk)",
2021-07-03 15:34:48 -04:00
"Check response clone use structureClone for teed ReadableStreams (BigInt64Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (BigUint64Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Float32Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Float64Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (DataViewchunk)"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-clone.any.worker.html": [
"Check response clone use structureClone for teed ReadableStreams (Int8Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Int16Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Int32Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (ArrayBufferchunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint8Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint8ClampedArraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint16Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Uint32Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (BigInt64Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (BigUint64Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Float32Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (Float64Arraychunk)",
"Check response clone use structureClone for teed ReadableStreams (DataViewchunk)"
],
2021-05-09 10:32:30 -04:00
"response-consume-empty.any.html": [
"Consume empty FormData response body as text"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-consume-empty.any.worker.html": [
"Consume empty FormData response body as text"
],
"response-consume-stream.any.html": false,
"response-consume-stream.any.worker.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"response-init-contenttype.any.html": true,
"response-init-contenttype.any.worker.html": true,
"response-static-json.any.html": true,
"response-static-json.any.worker.html": true,
"response-clone-iframe.window.html": false
},
"body": {
"formdata.any.html": true,
"formdata.any.worker.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"mime-type.any.html": true,
"mime-type.any.worker.html": true
},
"redirect": {
2021-05-09 10:32:30 -04:00
"redirect-count.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"redirect-count.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"redirect-empty-location.any.html": [
"redirect response with empty Location, manual mode"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"redirect-empty-location.any.worker.html": [
"redirect response with empty Location, manual mode"
],
2021-09-25 09:27:34 -04:00
"redirect-location-escape.tentative.any.html": [
"Redirect to unescaped UTF-8",
"Redirect to escaped and unescaped UTF-8",
"Escaping produces double-percent",
"Redirect to invalid UTF-8"
],
"redirect-location-escape.tentative.any.worker.html": [
"Redirect to unescaped UTF-8",
"Redirect to escaped and unescaped UTF-8",
"Escaping produces double-percent",
"Redirect to invalid UTF-8"
],
2021-05-09 10:32:30 -04:00
"redirect-location.any.html": [
"Redirect 301 in \"manual\" mode without location",
"Redirect 301 in \"manual\" mode with invalid location",
"Redirect 301 in \"manual\" mode with data location",
"Redirect 302 in \"manual\" mode without location",
"Redirect 302 in \"manual\" mode with invalid location",
"Redirect 302 in \"manual\" mode with data location",
"Redirect 303 in \"manual\" mode without location",
"Redirect 303 in \"manual\" mode with invalid location",
"Redirect 303 in \"manual\" mode with data location",
"Redirect 307 in \"manual\" mode without location",
"Redirect 307 in \"manual\" mode with invalid location",
"Redirect 307 in \"manual\" mode with data location",
"Redirect 308 in \"manual\" mode without location",
"Redirect 308 in \"manual\" mode with invalid location",
"Redirect 308 in \"manual\" mode with data location"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"redirect-location.any.worker.html": [
"Redirect 301 in \"manual\" mode without location",
"Redirect 301 in \"manual\" mode with invalid location",
"Redirect 301 in \"manual\" mode with data location",
"Redirect 302 in \"manual\" mode without location",
"Redirect 302 in \"manual\" mode with invalid location",
"Redirect 302 in \"manual\" mode with data location",
"Redirect 303 in \"manual\" mode without location",
"Redirect 303 in \"manual\" mode with invalid location",
"Redirect 303 in \"manual\" mode with data location",
"Redirect 307 in \"manual\" mode without location",
"Redirect 307 in \"manual\" mode with invalid location",
"Redirect 307 in \"manual\" mode with data location",
"Redirect 308 in \"manual\" mode without location",
"Redirect 308 in \"manual\" mode with invalid location",
"Redirect 308 in \"manual\" mode with data location"
],
2021-05-09 10:32:30 -04:00
"redirect-method.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"redirect-method.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"redirect-schemes.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"redirect-schemes.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"redirect-to-dataurl.any.html": true,
"redirect-to-dataurl.any.worker.html": true,
"redirect-back-to-original-origin.any.html": false,
"redirect-back-to-original-origin.any.worker.html": false,
"redirect-keepalive.any.html": false,
"redirect-mode.any.html": [
"same-origin redirect 301 in manual redirect and cors mode",
"same-origin redirect 301 in manual redirect and no-cors mode",
"same-origin redirect 302 in manual redirect and cors mode",
"same-origin redirect 302 in manual redirect and no-cors mode",
"same-origin redirect 303 in manual redirect and cors mode",
"same-origin redirect 303 in manual redirect and no-cors mode",
"same-origin redirect 307 in manual redirect and cors mode",
"same-origin redirect 307 in manual redirect and no-cors mode",
"same-origin redirect 308 in manual redirect and cors mode",
"same-origin redirect 308 in manual redirect and no-cors mode",
"cross-origin redirect 301 in manual redirect and cors mode",
"cross-origin redirect 301 in manual redirect and no-cors mode",
"cross-origin redirect 301 in follow redirect and no-cors mode",
"cross-origin redirect 302 in manual redirect and cors mode",
"cross-origin redirect 302 in manual redirect and no-cors mode",
"cross-origin redirect 302 in follow redirect and no-cors mode",
"cross-origin redirect 303 in manual redirect and cors mode",
"cross-origin redirect 303 in manual redirect and no-cors mode",
"cross-origin redirect 303 in follow redirect and no-cors mode",
"cross-origin redirect 307 in manual redirect and cors mode",
"cross-origin redirect 307 in manual redirect and no-cors mode",
"cross-origin redirect 307 in follow redirect and no-cors mode",
"cross-origin redirect 308 in manual redirect and cors mode",
"cross-origin redirect 308 in manual redirect and no-cors mode",
"cross-origin redirect 308 in follow redirect and no-cors mode",
"manual redirect with a CORS error should be rejected"
],
"redirect-mode.any.worker.html": [
"same-origin redirect 301 in manual redirect and cors mode",
"same-origin redirect 301 in manual redirect and no-cors mode",
"same-origin redirect 302 in manual redirect and cors mode",
"same-origin redirect 302 in manual redirect and no-cors mode",
"same-origin redirect 303 in manual redirect and cors mode",
"same-origin redirect 303 in manual redirect and no-cors mode",
"same-origin redirect 307 in manual redirect and cors mode",
"same-origin redirect 307 in manual redirect and no-cors mode",
"same-origin redirect 308 in manual redirect and cors mode",
"same-origin redirect 308 in manual redirect and no-cors mode",
"cross-origin redirect 301 in manual redirect and cors mode",
"cross-origin redirect 301 in manual redirect and no-cors mode",
"cross-origin redirect 301 in follow redirect and no-cors mode",
"cross-origin redirect 302 in manual redirect and cors mode",
"cross-origin redirect 302 in manual redirect and no-cors mode",
"cross-origin redirect 302 in follow redirect and no-cors mode",
"cross-origin redirect 303 in manual redirect and cors mode",
"cross-origin redirect 303 in manual redirect and no-cors mode",
"cross-origin redirect 303 in follow redirect and no-cors mode",
"cross-origin redirect 307 in manual redirect and cors mode",
"cross-origin redirect 307 in manual redirect and no-cors mode",
"cross-origin redirect 307 in follow redirect and no-cors mode",
"cross-origin redirect 308 in manual redirect and cors mode",
"cross-origin redirect 308 in manual redirect and no-cors mode",
"cross-origin redirect 308 in follow redirect and no-cors mode",
"manual redirect with a CORS error should be rejected"
],
"redirect-origin.any.html": [
"Same origin to other origin redirection 301",
"Other origin to other origin redirection 301",
"Other origin to same origin redirection 301",
"Same origin to other origin redirection[POST] 301",
"Other origin to other origin redirection[POST] 301",
"Other origin to same origin redirection[POST] 301",
"Same origin to other origin redirection 302",
"Other origin to other origin redirection 302",
"Other origin to same origin redirection 302",
"Same origin to other origin redirection[POST] 302",
"Other origin to other origin redirection[POST] 302",
"Other origin to same origin redirection[POST] 302",
"Same origin to other origin redirection 303",
"Other origin to other origin redirection 303",
"Other origin to same origin redirection 303",
"Same origin to other origin redirection[POST] 303",
"Other origin to other origin redirection[POST] 303",
"Other origin to same origin redirection[POST] 303",
"Same origin to other origin redirection 307",
"Other origin to other origin redirection 307",
"Other origin to same origin redirection 307",
"Same origin to other origin redirection[POST] 307",
"Other origin to other origin redirection[POST] 307",
"Other origin to same origin redirection[POST] 307",
"Same origin to other origin redirection 308",
"Other origin to other origin redirection 308",
"Other origin to same origin redirection 308",
"Same origin to other origin redirection[POST] 308",
"Other origin to other origin redirection[POST] 308",
"Other origin to same origin redirection[POST] 308"
],
"redirect-origin.any.worker.html": [
"Same origin to other origin redirection 301",
"Other origin to other origin redirection 301",
"Other origin to same origin redirection 301",
"Same origin to other origin redirection[POST] 301",
"Other origin to other origin redirection[POST] 301",
"Other origin to same origin redirection[POST] 301",
"Same origin to other origin redirection 302",
"Other origin to other origin redirection 302",
"Other origin to same origin redirection 302",
"Same origin to other origin redirection[POST] 302",
"Other origin to other origin redirection[POST] 302",
"Other origin to same origin redirection[POST] 302",
"Same origin to other origin redirection 303",
"Other origin to other origin redirection 303",
"Other origin to same origin redirection 303",
"Same origin to other origin redirection[POST] 303",
"Other origin to other origin redirection[POST] 303",
"Other origin to same origin redirection[POST] 303",
"Same origin to other origin redirection 307",
"Other origin to other origin redirection 307",
"Other origin to same origin redirection 307",
"Same origin to other origin redirection[POST] 307",
"Other origin to other origin redirection[POST] 307",
"Other origin to same origin redirection[POST] 307",
"Same origin to other origin redirection 308",
"Other origin to other origin redirection 308",
"Other origin to same origin redirection 308",
"Same origin to other origin redirection[POST] 308",
"Other origin to other origin redirection[POST] 308",
"Other origin to same origin redirection[POST] 308"
],
"redirect-referrer-override.any.html": [
"Same origin redirection, no-referrer-when-downgrade init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, origin-when-cross-origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, origin-when-cross-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, same-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, strict-origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, strict-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, unsafe-url redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, unsafe-url redirect header ",
"Same origin redirection, origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, origin init, origin redirect header ",
"Cross origin redirection, origin init, origin redirect header ",
"Same origin redirection, origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, origin init, same-origin redirect header ",
"Same origin redirection, origin init, strict-origin redirect header ",
"Cross origin redirection, origin init, strict-origin redirect header ",
"Same origin redirection, origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, origin init, unsafe-url redirect header ",
"Cross origin redirection, origin init, unsafe-url redirect header ",
"Same origin redirection, origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, origin-when-cross-origin init, origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, same-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, strict-origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, strict-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, unsafe-url redirect header ",
"Cross origin redirection, origin-when-cross-origin init, unsafe-url redirect header ",
"Same origin redirection, same-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, same-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, same-origin init, origin redirect header ",
"Cross origin redirection, same-origin init, origin redirect header ",
"Same origin redirection, same-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, same-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, same-origin init, same-origin redirect header ",
"Same origin redirection, same-origin init, strict-origin redirect header ",
"Cross origin redirection, same-origin init, strict-origin redirect header ",
"Same origin redirection, same-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, same-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, same-origin init, unsafe-url redirect header ",
"Cross origin redirection, same-origin init, unsafe-url redirect header ",
"Same origin redirection, strict-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, strict-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, strict-origin init, origin redirect header ",
"Cross origin redirection, strict-origin init, origin redirect header ",
"Same origin redirection, strict-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin init, same-origin redirect header ",
"Same origin redirection, strict-origin init, strict-origin redirect header ",
"Cross origin redirection, strict-origin init, strict-origin redirect header ",
"Same origin redirection, strict-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin init, unsafe-url redirect header ",
"Cross origin redirection, strict-origin init, unsafe-url redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, same-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, strict-origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, strict-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, unsafe-url redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, unsafe-url redirect header ",
"Same origin redirection, unsafe-url init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, unsafe-url init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, unsafe-url init, origin redirect header ",
"Cross origin redirection, unsafe-url init, origin redirect header ",
"Same origin redirection, unsafe-url init, origin-when-cross-origin redirect header ",
"Cross origin redirection, unsafe-url init, origin-when-cross-origin redirect header ",
"Same origin redirection, unsafe-url init, same-origin redirect header ",
"Same origin redirection, unsafe-url init, strict-origin redirect header ",
"Cross origin redirection, unsafe-url init, strict-origin redirect header ",
"Same origin redirection, unsafe-url init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, unsafe-url init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, unsafe-url init, unsafe-url redirect header ",
"Cross origin redirection, unsafe-url init, unsafe-url redirect header "
],
"redirect-referrer-override.any.worker.html": [
"Same origin redirection, no-referrer-when-downgrade init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, origin-when-cross-origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, origin-when-cross-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, same-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, strict-origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, strict-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, no-referrer-when-downgrade init, unsafe-url redirect header ",
"Cross origin redirection, no-referrer-when-downgrade init, unsafe-url redirect header ",
"Same origin redirection, origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, origin init, origin redirect header ",
"Cross origin redirection, origin init, origin redirect header ",
"Same origin redirection, origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, origin init, same-origin redirect header ",
"Same origin redirection, origin init, strict-origin redirect header ",
"Cross origin redirection, origin init, strict-origin redirect header ",
"Same origin redirection, origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, origin init, unsafe-url redirect header ",
"Cross origin redirection, origin init, unsafe-url redirect header ",
"Same origin redirection, origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, origin-when-cross-origin init, origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, same-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, strict-origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, strict-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, origin-when-cross-origin init, unsafe-url redirect header ",
"Cross origin redirection, origin-when-cross-origin init, unsafe-url redirect header ",
"Same origin redirection, same-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, same-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, same-origin init, origin redirect header ",
"Cross origin redirection, same-origin init, origin redirect header ",
"Same origin redirection, same-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, same-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, same-origin init, same-origin redirect header ",
"Same origin redirection, same-origin init, strict-origin redirect header ",
"Cross origin redirection, same-origin init, strict-origin redirect header ",
"Same origin redirection, same-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, same-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, same-origin init, unsafe-url redirect header ",
"Cross origin redirection, same-origin init, unsafe-url redirect header ",
"Same origin redirection, strict-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, strict-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, strict-origin init, origin redirect header ",
"Cross origin redirection, strict-origin init, origin redirect header ",
"Same origin redirection, strict-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin init, same-origin redirect header ",
"Same origin redirection, strict-origin init, strict-origin redirect header ",
"Cross origin redirection, strict-origin init, strict-origin redirect header ",
"Same origin redirection, strict-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin init, unsafe-url redirect header ",
"Cross origin redirection, strict-origin init, unsafe-url redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, same-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, strict-origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, strict-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, strict-origin-when-cross-origin init, unsafe-url redirect header ",
"Cross origin redirection, strict-origin-when-cross-origin init, unsafe-url redirect header ",
"Same origin redirection, unsafe-url init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, unsafe-url init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, unsafe-url init, origin redirect header ",
"Cross origin redirection, unsafe-url init, origin redirect header ",
"Same origin redirection, unsafe-url init, origin-when-cross-origin redirect header ",
"Cross origin redirection, unsafe-url init, origin-when-cross-origin redirect header ",
"Same origin redirection, unsafe-url init, same-origin redirect header ",
"Same origin redirection, unsafe-url init, strict-origin redirect header ",
"Cross origin redirection, unsafe-url init, strict-origin redirect header ",
"Same origin redirection, unsafe-url init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, unsafe-url init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, unsafe-url init, unsafe-url redirect header ",
"Cross origin redirection, unsafe-url init, unsafe-url redirect header "
],
"redirect-referrer.any.html": [
"Same origin redirection, empty init, unsafe-url redirect header ",
"Same origin redirection, empty init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, empty init, same-origin redirect header ",
"Same origin redirection, empty init, origin redirect header ",
"Same origin redirection, empty init, origin-when-cross-origin redirect header ",
"Same origin redirection, empty init, strict-origin redirect header ",
"Same origin redirection, empty init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, empty redirect header, unsafe-url init ",
"Same origin redirection, empty redirect header, no-referrer-when-downgrade init ",
"Same origin redirection, empty redirect header, same-origin init ",
"Same origin redirection, empty redirect header, origin init ",
"Same origin redirection, empty redirect header, origin-when-cross-origin init ",
"Same origin redirection, empty redirect header, strict-origin init ",
"Same origin redirection, empty redirect header, strict-origin-when-cross-origin init ",
"Cross origin redirection, empty init, unsafe-url redirect header ",
"Cross origin redirection, empty init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, empty init, origin redirect header ",
"Cross origin redirection, empty init, origin-when-cross-origin redirect header ",
"Cross origin redirection, empty init, strict-origin redirect header ",
"Cross origin redirection, empty init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, empty redirect header, unsafe-url init ",
"Cross origin redirection, empty redirect header, no-referrer-when-downgrade init ",
"Cross origin redirection, empty redirect header, origin init ",
"Cross origin redirection, empty redirect header, origin-when-cross-origin init ",
"Cross origin redirection, empty redirect header, strict-origin init ",
"Cross origin redirection, empty redirect header, strict-origin-when-cross-origin init "
],
"redirect-referrer.any.worker.html": [
"Same origin redirection, empty init, unsafe-url redirect header ",
"Same origin redirection, empty init, no-referrer-when-downgrade redirect header ",
"Same origin redirection, empty init, same-origin redirect header ",
"Same origin redirection, empty init, origin redirect header ",
"Same origin redirection, empty init, origin-when-cross-origin redirect header ",
"Same origin redirection, empty init, strict-origin redirect header ",
"Same origin redirection, empty init, strict-origin-when-cross-origin redirect header ",
"Same origin redirection, empty redirect header, unsafe-url init ",
"Same origin redirection, empty redirect header, no-referrer-when-downgrade init ",
"Same origin redirection, empty redirect header, same-origin init ",
"Same origin redirection, empty redirect header, origin init ",
"Same origin redirection, empty redirect header, origin-when-cross-origin init ",
"Same origin redirection, empty redirect header, strict-origin init ",
"Same origin redirection, empty redirect header, strict-origin-when-cross-origin init ",
"Cross origin redirection, empty init, unsafe-url redirect header ",
"Cross origin redirection, empty init, no-referrer-when-downgrade redirect header ",
"Cross origin redirection, empty init, origin redirect header ",
"Cross origin redirection, empty init, origin-when-cross-origin redirect header ",
"Cross origin redirection, empty init, strict-origin redirect header ",
"Cross origin redirection, empty init, strict-origin-when-cross-origin redirect header ",
"Cross origin redirection, empty redirect header, unsafe-url init ",
"Cross origin redirection, empty redirect header, no-referrer-when-downgrade init ",
"Cross origin redirection, empty redirect header, origin init ",
"Cross origin redirection, empty redirect header, origin-when-cross-origin init ",
"Cross origin redirection, empty redirect header, strict-origin init ",
"Cross origin redirection, empty redirect header, strict-origin-when-cross-origin init "
]
},
2021-05-09 10:32:30 -04:00
"idlharness.any.html": [
"Request interface: attribute destination",
"Request interface: attribute referrer",
"Request interface: attribute referrerPolicy",
"Request interface: attribute mode",
"Request interface: attribute credentials",
"Request interface: attribute cache",
"Request interface: attribute integrity",
"Request interface: attribute keepalive",
"Request interface: attribute isReloadNavigation",
"Request interface: attribute isHistoryNavigation",
"Request interface: attribute duplex",
"Request interface: attribute body",
"Request interface: attribute bodyUsed",
"Request interface: new Request('about:blank') must inherit property \"destination\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"referrer\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"referrerPolicy\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"mode\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"credentials\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"cache\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"integrity\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"keepalive\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"isReloadNavigation\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"isHistoryNavigation\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"duplex\" with the proper type",
"Response interface: attribute body",
"Response interface: attribute bodyUsed",
"Response interface: calling redirect(USVString, optional unsigned short) on new Response() with too few arguments must throw TypeError",
"Window interface: operation fetch(RequestInfo, optional RequestInit)"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"idlharness.any.worker.html": [
"Request interface: attribute destination",
"Request interface: attribute referrer",
"Request interface: attribute referrerPolicy",
"Request interface: attribute mode",
"Request interface: attribute credentials",
"Request interface: attribute cache",
"Request interface: attribute integrity",
"Request interface: attribute keepalive",
"Request interface: attribute isReloadNavigation",
"Request interface: attribute isHistoryNavigation",
"Request interface: attribute duplex",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Request interface: attribute body",
"Request interface: attribute bodyUsed",
"Request interface: new Request('about:blank') must inherit property \"destination\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"referrer\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"referrerPolicy\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"mode\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"credentials\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"cache\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"integrity\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"keepalive\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"isReloadNavigation\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"isHistoryNavigation\" with the proper type",
"Request interface: new Request('about:blank') must inherit property \"duplex\" with the proper type",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Response interface: attribute body",
"Response interface: attribute bodyUsed",
"Response interface: calling redirect(USVString, optional unsigned short) on new Response() with too few arguments must throw TypeError",
"WorkerGlobalScope interface: operation fetch(RequestInfo, optional RequestInit)",
"WorkerGlobalScope interface: self must inherit property \"fetch(RequestInfo, optional RequestInit)\" with the proper type",
"WorkerGlobalScope interface: calling fetch(RequestInfo, optional RequestInit) on self with too few arguments must throw TypeError"
],
"abort": {
"request.any.html": true,
"request.any.worker.html": true,
"general.any.html": true,
"general.any.worker.html": true,
2022-04-18 15:17:19 -04:00
"cache.https.any.html": false,
"cache.https.any.worker.html": false
},
"cors": {
"cors-basic.any.html": false,
"cors-basic.any.worker.html": false,
"cors-cookies-redirect.any.html": [
"Testing credentials after cross-origin redirection with CORS and no preflight",
"Testing credentials after cross-origin redirection with CORS and preflight"
],
"cors-cookies-redirect.any.worker.html": [
"Testing credentials after cross-origin redirection with CORS and no preflight",
"Testing credentials after cross-origin redirection with CORS and preflight"
],
"cors-cookies.any.html": [
"Include mode: 1 cookie"
],
"cors-cookies.any.worker.html": [
"Include mode: 1 cookie"
],
"cors-expose-star.sub.any.html": false,
"cors-expose-star.sub.any.worker.html": false,
"cors-filtering.sub.any.html": false,
"cors-filtering.sub.any.worker.html": false,
"cors-multiple-origins.sub.any.html": false,
"cors-multiple-origins.sub.any.worker.html": false,
"cors-no-preflight.any.html": true,
"cors-no-preflight.any.worker.html": true,
"cors-origin.any.html": [
"Cross domain different subdomain [origin KO]",
"Same domain different port [origin KO]",
"Cross domain different port [origin KO]",
"Cross domain different protocol [origin KO]",
"Same domain different protocol different port [origin KO]",
"Cross domain [POST] [origin KO]",
"Cross domain [HEAD] [origin KO]",
"CORS preflight [PUT] [origin KO]",
"Allowed origin: \"\" [origin KO]"
],
"cors-origin.any.worker.html": [
"Cross domain different subdomain [origin KO]",
"Same domain different port [origin KO]",
"Cross domain different port [origin KO]",
"Cross domain different protocol [origin KO]",
"Same domain different protocol different port [origin KO]",
"Cross domain [POST] [origin KO]",
"Cross domain [HEAD] [origin KO]",
"CORS preflight [PUT] [origin KO]",
"Allowed origin: \"\" [origin KO]"
],
"cors-preflight-cache.any.html": false,
"cors-preflight-cache.any.worker.html": false,
"cors-preflight-not-cors-safelisted.any.html": [
"Need CORS-preflight for accept/\" header",
"Need CORS-preflight for accept/012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 header",
"Need CORS-preflight for accept-language/\u0001 header",
"Need CORS-preflight for accept-language/@ header",
"Need CORS-preflight for authorization/basics header",
"Need CORS-preflight for content-language/\u0001 header",
"Need CORS-preflight for content-language/@ header",
"Need CORS-preflight for content-type/text/html header",
"Need CORS-preflight for content-type/text/plain; long=0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 header",
"Need CORS-preflight for range/bytes 0- header",
"Need CORS-preflight for test/hi header"
],
"cors-preflight-not-cors-safelisted.any.worker.html": [
"Need CORS-preflight for accept/\" header",
"Need CORS-preflight for accept/012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678 header",
"Need CORS-preflight for accept-language/\u0001 header",
"Need CORS-preflight for accept-language/@ header",
"Need CORS-preflight for authorization/basics header",
"Need CORS-preflight for content-language/\u0001 header",
"Need CORS-preflight for content-language/@ header",
"Need CORS-preflight for content-type/text/html header",
"Need CORS-preflight for content-type/text/plain; long=0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901 header",
"Need CORS-preflight for range/bytes 0- header",
"Need CORS-preflight for test/hi header"
],
"cors-preflight-redirect.any.html": false,
"cors-preflight-redirect.any.worker.html": false,
"cors-preflight-referrer.any.html": false,
"cors-preflight-referrer.any.worker.html": false,
"cors-preflight-response-validation.any.html": false,
"cors-preflight-response-validation.any.worker.html": false,
"cors-preflight-star.any.html": false,
"cors-preflight-star.any.worker.html": false,
"cors-preflight-status.any.html": false,
"cors-preflight-status.any.worker.html": false,
"cors-preflight.any.html": [
"CORS [DELETE], server allows",
"CORS [DELETE], server refuses",
"CORS [PUT], server allows",
"CORS [PUT], server allows, check preflight has user agent",
"CORS [PUT], server refuses",
"CORS [PATCH], server allows",
"CORS [PATCH], server refuses",
"CORS [patcH], server allows",
"CORS [patcH], server refuses",
"CORS [NEW], server allows",
"CORS [NEW], server refuses",
"CORS [chicken], server allows",
"CORS [chicken], server refuses",
"CORS [GET] [x-test-header: allowed], server allows",
"CORS [GET] [x-test-header: refused], server refuses",
"CORS [GET] [several headers], server allows",
"CORS [GET] [several headers], server refuses",
"CORS [PUT] [several headers], server allows",
"CORS [PUT] [several headers], server refuses",
"CORS [PUT] [only safe headers], server allows",
"\"authorization\" should not be covered by the wildcard symbol"
],
"cors-preflight.any.worker.html": [
"CORS [DELETE], server allows",
"CORS [DELETE], server refuses",
"CORS [PUT], server allows",
"CORS [PUT], server allows, check preflight has user agent",
"CORS [PUT], server refuses",
"CORS [PATCH], server allows",
"CORS [PATCH], server refuses",
"CORS [patcH], server allows",
"CORS [patcH], server refuses",
"CORS [NEW], server allows",
"CORS [NEW], server refuses",
"CORS [chicken], server allows",
"CORS [chicken], server refuses",
"CORS [GET] [x-test-header: allowed], server allows",
"CORS [GET] [x-test-header: refused], server refuses",
"CORS [GET] [several headers], server allows",
"CORS [GET] [several headers], server refuses",
"CORS [PUT] [several headers], server allows",
"CORS [PUT] [several headers], server refuses",
"CORS [PUT] [only safe headers], server allows",
"\"authorization\" should not be covered by the wildcard symbol"
],
"cors-redirect-credentials.any.html": [
"Redirect 301 from same origin to remote with user and password",
"Redirect 301 from same origin to remote with user",
"Redirect 301 from same origin to remote with password",
"Redirect 301 from remote to same origin with user and password",
"Redirect 301 from remote to same origin with user",
"Redirect 301 from remote to same origin with password",
"Redirect 301 from remote to same remote with user and password",
"Redirect 301 from remote to same remote with user",
"Redirect 301 from remote to same remote with password",
"Redirect 301 from remote to another remote with user and password",
"Redirect 301 from remote to another remote with user",
"Redirect 301 from remote to another remote with password",
"Redirect 302 from same origin to remote with user and password",
"Redirect 302 from same origin to remote with user",
"Redirect 302 from same origin to remote with password",
"Redirect 302 from remote to same origin with user and password",
"Redirect 302 from remote to same origin with user",
"Redirect 302 from remote to same origin with password",
"Redirect 302 from remote to same remote with user and password",
"Redirect 302 from remote to same remote with user",
"Redirect 302 from remote to same remote with password",
"Redirect 302 from remote to another remote with user and password",
"Redirect 302 from remote to another remote with user",
"Redirect 302 from remote to another remote with password",
"Redirect 303 from same origin to remote with user and password",
"Redirect 303 from same origin to remote with user",
"Redirect 303 from same origin to remote with password",
"Redirect 303 from remote to same origin with user and password",
"Redirect 303 from remote to same origin with user",
"Redirect 303 from remote to same origin with password",
"Redirect 303 from remote to same remote with user and password",
"Redirect 303 from remote to same remote with user",
"Redirect 303 from remote to same remote with password",
"Redirect 303 from remote to another remote with user and password",
"Redirect 303 from remote to another remote with user",
"Redirect 303 from remote to another remote with password",
"Redirect 307 from same origin to remote with user and password",
"Redirect 307 from same origin to remote with user",
"Redirect 307 from same origin to remote with password",
"Redirect 307 from remote to same origin with user and password",
"Redirect 307 from remote to same origin with user",
"Redirect 307 from remote to same origin with password",
"Redirect 307 from remote to same remote with user and password",
"Redirect 307 from remote to same remote with user",
"Redirect 307 from remote to same remote with password",
"Redirect 307 from remote to another remote with user and password",
"Redirect 307 from remote to another remote with user",
"Redirect 307 from remote to another remote with password",
"Redirect 308 from same origin to remote with user and password",
"Redirect 308 from same origin to remote with user",
"Redirect 308 from same origin to remote with password",
"Redirect 308 from remote to same origin with user and password",
"Redirect 308 from remote to same origin with user",
"Redirect 308 from remote to same origin with password",
"Redirect 308 from remote to same remote with user and password",
"Redirect 308 from remote to same remote with user",
"Redirect 308 from remote to same remote with password",
"Redirect 308 from remote to another remote with user and password",
"Redirect 308 from remote to another remote with user",
"Redirect 308 from remote to another remote with password"
],
"cors-redirect-credentials.any.worker.html": [
"Redirect 301 from same origin to remote with user and password",
"Redirect 301 from same origin to remote with user",
"Redirect 301 from same origin to remote with password",
"Redirect 301 from remote to same origin with user and password",
"Redirect 301 from remote to same origin with user",
"Redirect 301 from remote to same origin with password",
"Redirect 301 from remote to same remote with user and password",
"Redirect 301 from remote to same remote with user",
"Redirect 301 from remote to same remote with password",
"Redirect 301 from remote to another remote with user and password",
"Redirect 301 from remote to another remote with user",
"Redirect 301 from remote to another remote with password",
"Redirect 302 from same origin to remote with user and password",
"Redirect 302 from same origin to remote with user",
"Redirect 302 from same origin to remote with password",
"Redirect 302 from remote to same origin with user and password",
"Redirect 302 from remote to same origin with user",
"Redirect 302 from remote to same origin with password",
"Redirect 302 from remote to same remote with user and password",
"Redirect 302 from remote to same remote with user",
"Redirect 302 from remote to same remote with password",
"Redirect 302 from remote to another remote with user and password",
"Redirect 302 from remote to another remote with user",
"Redirect 302 from remote to another remote with password",
"Redirect 303 from same origin to remote with user and password",
"Redirect 303 from same origin to remote with user",
"Redirect 303 from same origin to remote with password",
"Redirect 303 from remote to same origin with user and password",
"Redirect 303 from remote to same origin with user",
"Redirect 303 from remote to same origin with password",
"Redirect 303 from remote to same remote with user and password",
"Redirect 303 from remote to same remote with user",
"Redirect 303 from remote to same remote with password",
"Redirect 303 from remote to another remote with user and password",
"Redirect 303 from remote to another remote with user",
"Redirect 303 from remote to another remote with password",
"Redirect 307 from same origin to remote with user and password",
"Redirect 307 from same origin to remote with user",
"Redirect 307 from same origin to remote with password",
"Redirect 307 from remote to same origin with user and password",
"Redirect 307 from remote to same origin with user",
"Redirect 307 from remote to same origin with password",
"Redirect 307 from remote to same remote with user and password",
"Redirect 307 from remote to same remote with user",
"Redirect 307 from remote to same remote with password",
"Redirect 307 from remote to another remote with user and password",
"Redirect 307 from remote to another remote with user",
"Redirect 307 from remote to another remote with password",
"Redirect 308 from same origin to remote with user and password",
"Redirect 308 from same origin to remote with user",
"Redirect 308 from same origin to remote with password",
"Redirect 308 from remote to same origin with user and password",
"Redirect 308 from remote to same origin with user",
"Redirect 308 from remote to same origin with password",
"Redirect 308 from remote to same remote with user and password",
"Redirect 308 from remote to same remote with user",
"Redirect 308 from remote to same remote with password",
"Redirect 308 from remote to another remote with user and password",
"Redirect 308 from remote to another remote with user",
"Redirect 308 from remote to another remote with password"
],
"cors-redirect-preflight.any.html": false,
"cors-redirect-preflight.any.worker.html": false,
"cors-redirect.any.html": false,
"cors-redirect.any.worker.html": false
},
"credentials": {
"authentication-basic.any.html": true,
"authentication-basic.any.worker.html": true,
"authentication-redirection.any.html": [
"getAuthorizationHeaderValue - cross origin redirection"
],
"authentication-redirection.any.worker.html": [
"getAuthorizationHeaderValue - cross origin redirection"
],
"cookies.any.html": [
"Include mode: 1 cookie",
"Include mode: 2 cookies",
"Same-origin mode: 1 cookie",
"Same-origin mode: 2 cookies"
],
"cookies.any.worker.html": [
"Include mode: 1 cookie",
"Include mode: 2 cookies",
"Same-origin mode: 1 cookie",
"Same-origin mode: 2 cookies"
]
}
},
2021-09-25 09:27:34 -04:00
"content-encoding": {
"bad-gzip-body.any.html": true,
"bad-gzip-body.any.worker.html": true,
"gzip-body.any.html": true,
"gzip-body.any.worker.html": true
2021-09-25 09:27:34 -04:00
},
"content-length": {
"api-and-duplicate-headers.any.html": false,
"api-and-duplicate-headers.any.worker.html": false,
"too-long.window.html": true,
"parsing.window.html": [
"Input: \"Content-Length: aaaah\\r\\nContent-Length: aaaah\". Expected: 42.",
"Input: \"Content-Length: aaaah, aaaah\". Expected: 42.",
"Input: \"Content-Length: aaaah\". Expected: 42.",
"Input: \"Content-Length: 42s\". Expected: 42.",
"Input: \"Content-Length: 30s\". Expected: 42.",
"Input: \"Content-Length: -1\". Expected: 42.",
"Input: \"Content-Length: 0x20\". Expected: 42.",
"Input: \"Content-Length: 030\\r\\nContent-Length: 30\". Expected: network error.",
"Input: \"Content-Length: 030, 30\". Expected: network error.",
"Input: \"Content-Length: \\\"30\\\"\". Expected: 42.",
"Input: \"Content-Length: \". Expected: 42."
]
2021-09-25 09:27:34 -04:00
},
"content-type": {
"multipart.window.html": true,
"multipart-malformed.any.html": false,
"multipart-malformed.any.worker.html": false,
"response.window.html": [
"<iframe>: separate response Content-Type: text/plain",
"<iframe>: combined response Content-Type: text/plain",
"<iframe>: separate response Content-Type: text/plain ",
"<iframe>: combined response Content-Type: text/plain ",
"<iframe>: separate response Content-Type: text/html text/plain",
"<iframe>: combined response Content-Type: text/html text/plain",
"<iframe>: separate response Content-Type: text/plain;charset=gbk text/html",
"<iframe>: combined response Content-Type: text/plain;charset=gbk text/html",
"<iframe>: separate response Content-Type: text/plain;charset=gbk text/html;charset=windows-1254",
"<iframe>: combined response Content-Type: text/plain;charset=gbk text/html;charset=windows-1254",
"<iframe>: separate response Content-Type: text/plain;charset=gbk text/plain",
"<iframe>: combined response Content-Type: text/plain;charset=gbk text/plain",
"<iframe>: separate response Content-Type: text/plain;charset=gbk text/plain;charset=windows-1252",
"<iframe>: combined response Content-Type: text/plain;charset=gbk text/plain;charset=windows-1252",
"<iframe>: separate response Content-Type: text/html;charset=gbk text/html;x=\",text/plain",
"<iframe>: combined response Content-Type: text/html;charset=gbk text/html;x=\",text/plain",
"<iframe>: separate response Content-Type: text/plain;charset=gbk;x=foo text/plain",
"<iframe>: combined response Content-Type: text/plain;charset=gbk;x=foo text/plain",
"<iframe>: separate response Content-Type: text/html;charset=gbk text/plain text/html",
"<iframe>: combined response Content-Type: text/html;charset=gbk text/plain text/html",
"<iframe>: separate response Content-Type: text/plain */*",
"<iframe>: combined response Content-Type: text/plain */*",
"<iframe>: separate response Content-Type: text/html */*",
"<iframe>: combined response Content-Type: text/html */*",
"<iframe>: separate response Content-Type: */* text/html",
"<iframe>: combined response Content-Type: */* text/html",
"<iframe>: separate response Content-Type: text/plain */*;charset=gbk",
"<iframe>: combined response Content-Type: text/plain */*;charset=gbk",
"<iframe>: separate response Content-Type: text/html */*;charset=gbk",
"<iframe>: combined response Content-Type: text/html */*;charset=gbk",
"<iframe>: separate response Content-Type: text/html;x=\" text/plain",
"<iframe>: combined response Content-Type: text/html;x=\" text/plain",
"<iframe>: separate response Content-Type: text/html;\" text/plain",
"<iframe>: combined response Content-Type: text/html;\" text/plain",
"<iframe>: separate response Content-Type: text/html;\" \\\" text/plain",
"<iframe>: combined response Content-Type: text/html;\" \\\" text/plain",
"<iframe>: separate response Content-Type: text/html;\" \\\" text/plain \";charset=GBK",
"<iframe>: combined response Content-Type: text/html;\" \\\" text/plain \";charset=GBK",
"<iframe>: separate response Content-Type: text/html;\" \" text/plain",
"<iframe>: combined response Content-Type: text/html;\" \" text/plain",
"fetch(): combined response Content-Type: text/html;x=\" text/plain",
"fetch(): separate response Content-Type: text/html;\" \\\" text/plain \";charset=GBK",
"fetch(): combined response Content-Type: text/html;\" \\\" text/plain \";charset=GBK",
"Request: combined response Content-Type: text/html;\" \\\" text/plain \";charset=GBK",
"Response: combined response Content-Type: text/html;\" \\\" text/plain \";charset=GBK"
],
"script.window.html": [
"separate text/javascript;charset=windows-1252",
"separate text/javascript;\";charset=windows-1252",
"separate text/javascript\f",
"separate \"text/javascript\"",
"separate text/ javascript",
"separate text /javascript",
"separate x/x text/javascript",
"combined x/x text/javascript",
"separate x/x;charset=windows-1252 text/javascript",
"combined x/x;charset=windows-1252 text/javascript",
"separate text/javascript x/x",
"combined text/javascript x/x",
"separate text/javascript; charset=windows-1252 text/javascript",
"combined text/javascript; charset=windows-1252 text/javascript",
"separate text/javascript;\" x/x",
"combined text/javascript;\" x/x",
"separate text/javascript ",
"combined text/javascript ",
"separate text/javascript error",
"combined text/javascript error",
"separate text/javascript;charset=windows-1252 x/x text/javascript",
"combined text/javascript;charset=windows-1252 x/x text/javascript",
"separate text/javascript;charset=windows-1252 error text/javascript",
"combined text/javascript;charset=windows-1252 error text/javascript",
"separate text/javascript;charset=windows-1252 text/javascript",
"combined text/javascript;charset=windows-1252 text/javascript",
"separate text/javascript;charset=windows-1252;\" \\\" x/x",
"combined text/javascript;charset=windows-1252;\" \\\" x/x",
"separate x/x;\" x/y;\\\" text/javascript;charset=windows-1252;\" text/javascript",
"combined x/x;\" x/y;\\\" text/javascript;charset=windows-1252;\" text/javascript"
]
},
"data-urls": {
2021-05-09 10:32:30 -04:00
"base64.any.html": true,
"base64.any.worker.html": true,
"processing.any.html": true,
"processing.any.worker.html": true
2021-09-25 09:27:34 -04:00
},
"h1-parsing": {
"lone-cr.window.html": [
"Parsing response with a lone CR before message-body (HTTP/1.1 200 OK\nHeader: Value\r\n\nBody)"
],
"status-code.window.html": [
"HTTP/1.1 0 OK ",
"HTTP/1.1 1 OK ",
"HTTP/1.1 99 NOT OK ",
"HTTP/1.1 077 77 ",
"HTTP/1.1 099 HELLO ",
"HTTP/1.1 200 ",
"HTTP/1.1 999 DOES IT MATTER "
],
"resources-with-0x00-in-header.window.html": false
2021-09-25 09:27:34 -04:00
},
"range": {
"general.any.html": [
"Privileged header not allowed for guard type: request-no-cors",
2022-04-18 15:17:19 -04:00
"Cross Origin Fetch with non safe range header"
2021-09-25 09:27:34 -04:00
],
"general.any.worker.html": [
"Privileged header not allowed for guard type: request-no-cors",
2022-04-18 15:17:19 -04:00
"Cross Origin Fetch with non safe range header"
2021-09-25 09:27:34 -04:00
],
"general.window.html": false,
"blob.any.html": false,
"blob.any.worker.html": false,
"data.any.html": true,
"data.any.worker.html": true,
"sw.https.window.html": false
},
"cross-origin-resource-policy": {
"fetch.any.html": [
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-scheme (HTTP to HTTPS) no-cors fetch to a same-site URL with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-origin no-cors fetch to a same-site URL with a 'Cross-Origin-Resource-Policy: same-origin' response header.",
"Valid cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header after a redirection.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' redirect response header."
],
"fetch.any.worker.html": [
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-scheme (HTTP to HTTPS) no-cors fetch to a same-site URL with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-origin no-cors fetch to a same-site URL with a 'Cross-Origin-Resource-Policy: same-origin' response header.",
"Valid cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header after a redirection.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' redirect response header."
],
"fetch.https.any.html": [
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header after a redirection.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' redirect response header."
],
"fetch.https.any.worker.html": [
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-site' response header.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' response header after a redirection.",
"Cross-origin no-cors fetch with a 'Cross-Origin-Resource-Policy: same-origin' redirect response header."
],
"scheme-restriction.any.html": false,
"scheme-restriction.any.worker.html": false,
"scheme-restriction.https.window.html": false,
"syntax.any.html": true,
"syntax.any.worker.html": true
},
"http-cache": {
"304-update.any.html": false,
"304-update.any.worker.html": false,
"cache-mode.any.html": [
"Fetch sends Cache-Control: max-age=0 when cache mode is no-cache",
"Fetch sends Cache-Control: no-cache and Pragma: no-cache when cache mode is no-store"
],
"cache-mode.any.worker.html": [
"Fetch sends Cache-Control: max-age=0 when cache mode is no-cache",
"Fetch sends Cache-Control: no-cache and Pragma: no-cache when cache mode is no-store"
],
"cc-request.any.html": [
"HTTP cache does use aged stale response when request contains Cache-Control: max-stale that permits its use",
"HTTP cache does reuse stale response with Age header when request contains Cache-Control: max-stale that permits its use",
"HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached"
],
"cc-request.any.worker.html": [
"HTTP cache does use aged stale response when request contains Cache-Control: max-stale that permits its use",
"HTTP cache does reuse stale response with Age header when request contains Cache-Control: max-stale that permits its use",
"HTTP cache generates 504 status code when nothing is in cache and request contains Cache-Control: only-if-cached"
],
"credentials.tentative.any.html": false,
"credentials.tentative.any.worker.html": false,
"freshness.any.html": [
"HTTP cache reuses a response with a future Expires",
"HTTP cache reuses a response with positive Cache-Control: max-age",
"HTTP cache reuses a response with positive Cache-Control: max-age and a past Expires",
"HTTP cache reuses a response with positive Cache-Control: max-age and an invalid Expires",
"HTTP cache stores a response with Cache-Control: no-cache, but revalidates upon use",
"HTTP cache stores a response with Cache-Control: no-cache, but revalidates upon use, even with max-age and Expires"
],
"freshness.any.worker.html": [
"HTTP cache reuses a response with a future Expires",
"HTTP cache reuses a response with positive Cache-Control: max-age",
"HTTP cache reuses a response with positive Cache-Control: max-age and a past Expires",
"HTTP cache reuses a response with positive Cache-Control: max-age and an invalid Expires",
"HTTP cache stores a response with Cache-Control: no-cache, but revalidates upon use",
"HTTP cache stores a response with Cache-Control: no-cache, but revalidates upon use, even with max-age and Expires"
],
"heuristic.any.html": [
"HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present",
"HTTP cache reuses a 200 OK response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 203 Non-Authoritative Information response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 204 No Content response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 410 Gone response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness"
],
"heuristic.any.worker.html": [
"HTTP cache reuses an unknown response with Last-Modified based upon heuristic freshness when Cache-Control: public is present",
"HTTP cache reuses a 200 OK response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 203 Non-Authoritative Information response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 204 No Content response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 404 Not Found response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 405 Method Not Allowed response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 410 Gone response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 414 URI Too Long response with Last-Modified based upon heuristic freshness",
"HTTP cache reuses a 501 Not Implemented response with Last-Modified based upon heuristic freshness"
],
"invalidate.any.html": [
"HTTP cache does not invalidate after a failed response from an unsafe request",
"HTTP cache does not invalidate Location URL after a failed response from an unsafe request",
"HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request"
],
"invalidate.any.worker.html": [
"HTTP cache does not invalidate after a failed response from an unsafe request",
"HTTP cache does not invalidate Location URL after a failed response from an unsafe request",
"HTTP cache does not invalidate Content-Location URL after a failed response from an unsafe request"
],
"partial.any.html": false,
"partial.any.worker.html": false,
"post-patch.any.html": false,
"post-patch.any.worker.html": false,
"status.any.html": [
"HTTP cache avoids going to the network if it has a fresh 200 response",
"HTTP cache avoids going to the network if it has a fresh 203 response",
"HTTP cache avoids going to the network if it has a fresh 204 response",
"HTTP cache avoids going to the network if it has a fresh 299 response",
"HTTP cache avoids going to the network if it has a fresh 400 response",
"HTTP cache avoids going to the network if it has a fresh 404 response",
"HTTP cache avoids going to the network if it has a fresh 410 response",
"HTTP cache avoids going to the network if it has a fresh 499 response",
"HTTP cache avoids going to the network if it has a fresh 500 response",
"HTTP cache avoids going to the network if it has a fresh 502 response",
"HTTP cache avoids going to the network if it has a fresh 503 response",
"HTTP cache avoids going to the network if it has a fresh 504 response",
"HTTP cache avoids going to the network if it has a fresh 599 response"
],
"status.any.worker.html": [
"HTTP cache avoids going to the network if it has a fresh 200 response",
"HTTP cache avoids going to the network if it has a fresh 203 response",
"HTTP cache avoids going to the network if it has a fresh 204 response",
"HTTP cache avoids going to the network if it has a fresh 299 response",
"HTTP cache avoids going to the network if it has a fresh 400 response",
"HTTP cache avoids going to the network if it has a fresh 404 response",
"HTTP cache avoids going to the network if it has a fresh 410 response",
"HTTP cache avoids going to the network if it has a fresh 499 response",
"HTTP cache avoids going to the network if it has a fresh 500 response",
"HTTP cache avoids going to the network if it has a fresh 502 response",
"HTTP cache avoids going to the network if it has a fresh 503 response",
"HTTP cache avoids going to the network if it has a fresh 504 response",
"HTTP cache avoids going to the network if it has a fresh 599 response"
],
"vary.any.html": [
"HTTP cache reuses Vary response when request matches",
"HTTP cache doesn't invalidate existing Vary response",
"HTTP cache doesn't pay attention to headers not listed in Vary",
"HTTP cache reuses two-way Vary response when request matches",
"HTTP cache reuses three-way Vary response when request matches",
"HTTP cache uses three-way Vary response when both request and the original request omited a variant header"
],
"vary.any.worker.html": [
"HTTP cache reuses Vary response when request matches",
"HTTP cache doesn't invalidate existing Vary response",
"HTTP cache doesn't pay attention to headers not listed in Vary",
"HTTP cache reuses two-way Vary response when request matches",
"HTTP cache reuses three-way Vary response when request matches",
"HTTP cache uses three-way Vary response when both request and the original request omited a variant header"
]
},
"local-network-access": {
"fetch-from-treat-as-public.https.window.html": false,
"fetch.https.window.html?include=baseline": false,
"fetch.https.window.html?include=from-local": false,
"fetch.https.window.html?include=from-private": false,
"fetch.https.window.html?include=from-public": false,
"fetch.window.html": false,
"iframe.tentative.https.window.html": false,
"iframe.tentative.window.html": false,
"mixed-content-fetch.tentative.https.window.html": false,
"nested-worker.https.window.html": false,
"nested-worker.window.html": false,
"preflight-cache.https.window.html": false,
"redirect.https.window.html": false,
"service-worker-background-fetch.https.window.html": false,
"service-worker-fetch.https.window.html": false,
"service-worker-update.https.window.html": false,
"service-worker.https.window.html": false,
"shared-worker-blob-fetch.https.window.html": false,
"shared-worker-blob-fetch.window.html": false,
"shared-worker-fetch.https.window.html": false,
"shared-worker-fetch.window.html": false,
"shared-worker.https.window.html": false,
"shared-worker.window.html": false,
"websocket.https.window.html": false,
"websocket.window.html": false,
"worker-blob-fetch.window.html": false,
"worker-fetch.https.window.html": false,
"worker-fetch.window.html": false,
"worker.https.window.html": false,
"worker.window.html": false,
"xhr-from-treat-as-public.https.window.html": false,
"xhr.https.window.html?include=from-local": false,
"xhr.https.window.html?include=from-private": false,
"xhr.https.window.html?include=from-public": false,
"xhr.window.html": false
},
"metadata": {
"fetch-preflight.https.sub.any.html": [
"Same-site fetch with preflight: sec-fetch-dest",
"Same-site fetch with preflight: sec-fetch-mode",
"Same-site fetch with preflight: sec-fetch-site",
"Cross-site fetch with preflight: sec-fetch-dest",
"Cross-site fetch with preflight: sec-fetch-mode",
"Cross-site fetch with preflight: sec-fetch-site"
],
"fetch-preflight.https.sub.any.worker.html": [
"Same-site fetch with preflight: sec-fetch-dest",
"Same-site fetch with preflight: sec-fetch-mode",
"Same-site fetch with preflight: sec-fetch-site",
"Cross-site fetch with preflight: sec-fetch-dest",
"Cross-site fetch with preflight: sec-fetch-mode",
"Cross-site fetch with preflight: sec-fetch-site"
],
"fetch.https.sub.any.html": [
"Same-origin fetch: sec-fetch-dest",
"Same-origin fetch: sec-fetch-mode",
"Same-origin fetch: sec-fetch-site",
"Same-site fetch: sec-fetch-dest",
"Same-site fetch: sec-fetch-mode",
"Same-site fetch: sec-fetch-site",
"Cross-site fetch: sec-fetch-dest",
"Cross-site fetch: sec-fetch-mode",
"Cross-site fetch: sec-fetch-site",
"Same-origin mode: sec-fetch-dest",
"Same-origin mode: sec-fetch-mode",
"Same-origin mode: sec-fetch-site",
"CORS mode: sec-fetch-dest",
"CORS mode: sec-fetch-mode",
"CORS mode: sec-fetch-site",
"no-CORS mode: sec-fetch-dest",
"no-CORS mode: sec-fetch-mode",
"no-CORS mode: sec-fetch-site"
],
"fetch.https.sub.any.worker.html": [
"Same-origin fetch: sec-fetch-dest",
"Same-origin fetch: sec-fetch-mode",
"Same-origin fetch: sec-fetch-site",
"Same-site fetch: sec-fetch-dest",
"Same-site fetch: sec-fetch-mode",
"Same-site fetch: sec-fetch-site",
"Cross-site fetch: sec-fetch-dest",
"Cross-site fetch: sec-fetch-mode",
"Cross-site fetch: sec-fetch-site",
"Same-origin mode: sec-fetch-dest",
"Same-origin mode: sec-fetch-mode",
"Same-origin mode: sec-fetch-site",
"CORS mode: sec-fetch-dest",
"CORS mode: sec-fetch-mode",
"CORS mode: sec-fetch-site",
"no-CORS mode: sec-fetch-dest",
"no-CORS mode: sec-fetch-mode",
"no-CORS mode: sec-fetch-site"
],
"trailing-dot.https.sub.any.html": [
"Fetching a resource from the same origin, but spelled with a trailing dot.: sec-fetch-dest",
"Fetching a resource from the same origin, but spelled with a trailing dot.: sec-fetch-mode",
"Fetching a resource from the same origin, but spelled with a trailing dot.: sec-fetch-site",
"Fetching a resource from the same site, but spelled with a trailing dot.: sec-fetch-dest",
"Fetching a resource from the same site, but spelled with a trailing dot.: sec-fetch-mode",
"Fetching a resource from the same site, but spelled with a trailing dot.: sec-fetch-site",
"Fetching a resource from a cross-site host, spelled with a trailing dot.: sec-fetch-dest",
"Fetching a resource from a cross-site host, spelled with a trailing dot.: sec-fetch-mode",
"Fetching a resource from a cross-site host, spelled with a trailing dot.: sec-fetch-site"
],
"trailing-dot.https.sub.any.worker.html": [
"Fetching a resource from the same origin, but spelled with a trailing dot.: sec-fetch-dest",
"Fetching a resource from the same origin, but spelled with a trailing dot.: sec-fetch-mode",
"Fetching a resource from the same origin, but spelled with a trailing dot.: sec-fetch-site",
"Fetching a resource from the same site, but spelled with a trailing dot.: sec-fetch-dest",
"Fetching a resource from the same site, but spelled with a trailing dot.: sec-fetch-mode",
"Fetching a resource from the same site, but spelled with a trailing dot.: sec-fetch-site",
"Fetching a resource from a cross-site host, spelled with a trailing dot.: sec-fetch-dest",
"Fetching a resource from a cross-site host, spelled with a trailing dot.: sec-fetch-mode",
"Fetching a resource from a cross-site host, spelled with a trailing dot.: sec-fetch-site"
]
},
"nosniff": {
"parsing-nosniff.window.html": [
"X-Content-Type-Options%3A%20NOSNIFF",
"x-content-type-OPTIONS%3A%20nosniff",
"X-Content-Type-Options%3A%20nosniff%2C%2C%40%23%24%23%25%25%26%5E%26%5E*()()11!",
"X-Content-Type-Options%3A%20%40%23%24%23%25%25%26%5E%26%5E*()()11!%2Cnosniff",
"X-Content-Type-Options%3A%20nosniff%0D%0AX-Content-Type-Options%3A%20no",
"X-Content-Type-Options%3A%20no%0D%0AX-Content-Type-Options%3A%20nosniff",
"X-Content-Type-Options%3A%0D%0AX-Content-Type-Options%3A%20nosniff",
"X-Content-Type-Options%3A%20nosniff%0D%0AX-Content-Type-Options%3A%20nosniff",
"X-Content-Type-Options%3A%20%2Cnosniff",
"X-Content-Type-Options%3A%20nosniff%0C",
"X-Content-Type-Options%3A%20nosniff%0B",
"X-Content-Type-Options%3A%20nosniff%0B%2Cnosniff",
"X-Content-Type-Options%3A%20'NosniFF'",
"X-Content-Type-Options%3A%20%22nosniFF%22",
"Content-Type-Options%3A%20nosniff"
]
},
"orb": {
"tentative": {
"content-range.sub.any.html": [
"ORB should block opaque range of image/png not starting at zero, that isn't subsequent"
],
"content-range.sub.any.worker.html": [
"ORB should block opaque range of image/png not starting at zero, that isn't subsequent"
],
"known-mime-type.sub.any.html": [
"ORB should block opaque font/ttf",
"ORB should block opaque text/plain",
"ORB should block opaque application/json (non-empty)",
"ORB should block opaque application/json (empty)",
"ORB should block opaque application/json which contains non ascii characters"
],
"known-mime-type.sub.any.worker.html": [
"ORB should block opaque font/ttf",
"ORB should block opaque text/plain",
"ORB should block opaque application/json (non-empty)",
"ORB should block opaque application/json (empty)",
"ORB should block opaque application/json which contains non ascii characters"
],
"nosniff.sub.any.html": [
"ORB should block opaque text/plain with nosniff",
"ORB should block opaque-response-blocklisted MIME type with nosniff",
"ORB should block opaque response with empty Content-Type and nosniff"
],
"nosniff.sub.any.worker.html": [
"ORB should block opaque text/plain with nosniff",
"ORB should block opaque-response-blocklisted MIME type with nosniff",
"ORB should block opaque response with empty Content-Type and nosniff"
],
"status.sub.any.html": false,
"status.sub.any.worker.html": false,
"unknown-mime-type.sub.any.html": true,
"unknown-mime-type.sub.any.worker.html": true
}
},
"origin": {
"assorted.window.html": [
"Origin header and 308 redirect",
"Origin header and GET navigation",
"Origin header and POST navigation",
"Origin header and POST same-origin navigation with Referrer-Policy no-referrer",
"Origin header and POST same-origin fetch no-cors mode with Referrer-Policy no-referrer",
"Origin header and POST same-origin fetch cors mode with Referrer-Policy no-referrer",
"Origin header and POST cross-origin navigation with Referrer-Policy no-referrer",
"Origin header and POST cross-origin fetch no-cors mode with Referrer-Policy no-referrer",
"Origin header and POST cross-origin fetch cors mode with Referrer-Policy no-referrer",
"Origin header and GET cross-origin fetch cors mode with Referrer-Policy no-referrer",
"Origin header and POST same-origin navigation with Referrer-Policy same-origin",
"Origin header and POST same-origin fetch no-cors mode with Referrer-Policy same-origin",
"Origin header and POST same-origin fetch cors mode with Referrer-Policy same-origin",
"Origin header and POST cross-origin navigation with Referrer-Policy same-origin",
"Origin header and POST cross-origin fetch no-cors mode with Referrer-Policy same-origin",
"Origin header and POST cross-origin fetch cors mode with Referrer-Policy same-origin",
"Origin header and GET cross-origin fetch cors mode with Referrer-Policy same-origin",
"Origin header and POST same-origin navigation with Referrer-Policy origin-when-cross-origin",
"Origin header and POST same-origin fetch no-cors mode with Referrer-Policy origin-when-cross-origin",
"Origin header and POST same-origin fetch cors mode with Referrer-Policy origin-when-cross-origin",
"Origin header and POST cross-origin navigation with Referrer-Policy origin-when-cross-origin",
"Origin header and POST cross-origin fetch no-cors mode with Referrer-Policy origin-when-cross-origin",
"Origin header and POST cross-origin fetch cors mode with Referrer-Policy origin-when-cross-origin",
"Origin header and GET cross-origin fetch cors mode with Referrer-Policy origin-when-cross-origin",
"Origin header and POST same-origin navigation with Referrer-Policy no-referrer-when-downgrade",
"Origin header and POST same-origin fetch no-cors mode with Referrer-Policy no-referrer-when-downgrade",
"Origin header and POST same-origin fetch cors mode with Referrer-Policy no-referrer-when-downgrade",
"Origin header and POST cross-origin navigation with Referrer-Policy no-referrer-when-downgrade",
"Origin header and POST cross-origin fetch no-cors mode with Referrer-Policy no-referrer-when-downgrade",
"Origin header and POST cross-origin fetch cors mode with Referrer-Policy no-referrer-when-downgrade",
"Origin header and GET cross-origin fetch cors mode with Referrer-Policy no-referrer-when-downgrade",
"Origin header and POST same-origin navigation with Referrer-Policy unsafe-url",
"Origin header and POST same-origin fetch no-cors mode with Referrer-Policy unsafe-url",
"Origin header and POST same-origin fetch cors mode with Referrer-Policy unsafe-url",
"Origin header and POST cross-origin navigation with Referrer-Policy unsafe-url",
"Origin header and POST cross-origin fetch no-cors mode with Referrer-Policy unsafe-url",
"Origin header and POST cross-origin fetch cors mode with Referrer-Policy unsafe-url",
"Origin header and GET cross-origin fetch cors mode with Referrer-Policy unsafe-url"
]
},
"redirects": {
"data.window.html": false
},
"security": {
"1xx-response.any.html": true,
"1xx-response.any.worker.html": true
},
"stale-while-revalidate": {
"fetch.any.html": false,
"fetch.any.worker.html": false
}
},
"FileAPI": {
"blob": {
2021-05-09 10:32:30 -04:00
"Blob-array-buffer.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Blob-array-buffer.any.worker.html": true,
"Blob-constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Blob-constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"Blob-slice-overflow.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Blob-slice-overflow.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"Blob-slice.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Blob-slice.any.worker.html": true,
"Blob-stream.any.html": false,
"Blob-stream.any.worker.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Blob-text.any.html": true,
"Blob-text.any.worker.html": true,
"Blob-in-worker.worker.html": true,
"Blob-constructor-dom.window.html": false
},
"file": {
2021-06-01 12:24:31 -04:00
"File-constructor.any.html": true,
"File-constructor.any.worker.html": true,
"send-file-formdata-controls.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"send-file-formdata-controls.any.worker.html": true,
"send-file-formdata-punctuation.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"send-file-formdata-punctuation.any.worker.html": true,
2021-06-01 12:24:31 -04:00
"send-file-formdata-utf-8.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"send-file-formdata-utf-8.any.worker.html": true,
"send-file-formdata.any.html": true,
"send-file-formdata.any.worker.html": true,
"Worker-read-file-constructor.worker.html": true
},
2021-05-09 10:32:30 -04:00
"fileReader.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"fileReader.any.worker.html": true,
"url": {
2021-05-09 10:32:30 -04:00
"url-format.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"url-format.any.worker.html": true,
"url-with-fetch.any.html": true,
"url-with-fetch.any.worker.html": true,
"url-charset.window.html": false,
"url-in-tags-revoke.window.html": false,
"url-in-tags.window.html": false,
"url-reload.window.html": false,
"url-with-xhr.any.html": false,
"url-with-xhr.any.worker.html": false
},
"reading-data-section": {
2021-05-09 10:32:30 -04:00
"Determining-Encoding.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Determining-Encoding.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"FileReader-event-handler-attributes.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"FileReader-event-handler-attributes.any.worker.html": true,
"FileReader-multiple-reads.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"FileReader-multiple-reads.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_abort.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_abort.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_error.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_error.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_events.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_events.any.worker.html": false,
2021-05-09 10:32:30 -04:00
"filereader_readAsArrayBuffer.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_readAsArrayBuffer.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_readAsBinaryString.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_readAsBinaryString.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_readAsDataURL.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_readAsDataURL.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_readAsText.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_readAsText.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"filereader_readystate.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"filereader_readystate.any.worker.html": true,
"filereader_result.any.html": true,
"filereader_result.any.worker.html": true
2021-08-09 12:49:31 -04:00
},
"idlharness.any.html": [
"FileList interface: existence and properties of interface object",
"FileList interface object length",
"FileList interface object name",
"FileList interface: existence and properties of interface prototype object",
"FileList interface: existence and properties of interface prototype object's \"constructor\" property",
"FileList interface: existence and properties of interface prototype object's @@unscopables property",
"FileList interface: operation item(unsigned long)",
"FileList interface: attribute length"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"idlharness.any.worker.html": [
"FileList interface: existence and properties of interface object",
"FileList interface object length",
"FileList interface object name",
"FileList interface: existence and properties of interface prototype object",
"FileList interface: existence and properties of interface prototype object's \"constructor\" property",
"FileList interface: existence and properties of interface prototype object's @@unscopables property",
"FileList interface: operation item(unsigned long)",
"FileList interface: attribute length",
"FileReaderSync interface: existence and properties of interface object",
"FileReaderSync interface object length",
"FileReaderSync interface object name",
"FileReaderSync interface: existence and properties of interface prototype object",
"FileReaderSync interface: existence and properties of interface prototype object's \"constructor\" property",
"FileReaderSync interface: existence and properties of interface prototype object's @@unscopables property",
"FileReaderSync interface: operation readAsArrayBuffer(Blob)",
"FileReaderSync interface: operation readAsBinaryString(Blob)",
"FileReaderSync interface: operation readAsText(Blob, optional DOMString)",
"FileReaderSync interface: operation readAsDataURL(Blob)"
],
"FileReaderSync.worker.html": false,
"idlharness.worker.html": [
"FileList interface: existence and properties of interface object",
"FileList interface object length",
"FileList interface object name",
"FileList interface: existence and properties of interface prototype object",
"FileList interface: existence and properties of interface prototype object's \"constructor\" property",
"FileList interface: existence and properties of interface prototype object's @@unscopables property",
"FileList interface: operation item(unsigned long)",
"FileList interface: attribute length",
"FileReaderSync interface: existence and properties of interface object",
"FileReaderSync interface object length",
"FileReaderSync interface object name",
"FileReaderSync interface: existence and properties of interface prototype object",
"FileReaderSync interface: existence and properties of interface prototype object's \"constructor\" property",
"FileReaderSync interface: existence and properties of interface prototype object's @@unscopables property",
"FileReaderSync interface: operation readAsArrayBuffer(Blob)",
"FileReaderSync interface: operation readAsBinaryString(Blob)",
"FileReaderSync interface: operation readAsText(Blob, optional DOMString)",
"FileReaderSync interface: operation readAsDataURL(Blob)",
"FileReaderSync must be primary interface of new FileReaderSync()",
"Stringification of new FileReaderSync()",
"FileReaderSync interface: new FileReaderSync() must inherit property \"readAsArrayBuffer(Blob)\" with the proper type",
"FileReaderSync interface: calling readAsArrayBuffer(Blob) on new FileReaderSync() with too few arguments must throw TypeError",
"FileReaderSync interface: new FileReaderSync() must inherit property \"readAsBinaryString(Blob)\" with the proper type",
"FileReaderSync interface: calling readAsBinaryString(Blob) on new FileReaderSync() with too few arguments must throw TypeError",
"FileReaderSync interface: new FileReaderSync() must inherit property \"readAsText(Blob, optional DOMString)\" with the proper type",
"FileReaderSync interface: calling readAsText(Blob, optional DOMString) on new FileReaderSync() with too few arguments must throw TypeError",
"FileReaderSync interface: new FileReaderSync() must inherit property \"readAsDataURL(Blob)\" with the proper type",
"FileReaderSync interface: calling readAsDataURL(Blob) on new FileReaderSync() with too few arguments must throw TypeError"
2021-08-09 12:49:31 -04:00
]
},
"html": {
2021-09-25 09:27:34 -04:00
"semantics": {
"scripting-1": {
"the-script-element": {
"import-assertions": {
"dynamic-import-with-assertion-argument.any.html": true,
"dynamic-import-with-assertion-argument.any.worker.html": true
},
2021-09-25 09:27:34 -04:00
"json-module": {
"charset-bom.any.html": [
"UTF-16BE BOM should result in parse error in JSON module script",
"UTF-16LE BOM should result in parse error in JSON module script"
],
"charset-bom.any.worker.html": [
"UTF-16BE BOM should result in parse error in JSON module script",
"UTF-16LE BOM should result in parse error in JSON module script"
],
"invalid-content-type.any.html": true,
"invalid-content-type.any.worker.html": true,
"non-object.any.html": true,
"non-object.any.worker.html": true,
2021-09-25 09:27:34 -04:00
"repeated-imports.any.html": [
"Two modules of different type with the same specifier can load if the server changes its responses"
2021-09-25 09:27:34 -04:00
],
"repeated-imports.any.worker.html": [
"Two modules of different type with the same specifier can load if the server changes its responses"
2021-09-25 09:27:34 -04:00
]
},
"microtasks": {
"checkpoint-importScripts.any.worker.html": true,
"evaluation-order-1-nothrow-importScripts.any.worker.html": true,
"evaluation-order-1-nothrow-static-import.any.worker-module.html": true,
"evaluation-order-1-throw-importScripts.any.worker.html": false,
"evaluation-order-1-throw-static-import.any.worker-module.html": false,
"evaluation-order-2.any.worker-module.html": false,
"evaluation-order-3.any.worker-module.html": true
2021-09-25 09:27:34 -04:00
},
"module": {
"dynamic-import": {
"blob-url.any.html": [
"Revoking a blob URL immediately after calling import will not fail"
],
"blob-url.any.worker.html": [
"Revoking a blob URL immediately after calling import will not fail"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"blob-url.any.worker-module.html": [
"Revoking a blob URL immediately after calling import will not fail"
],
"blob-url-workers.window.html": [
"A revoked blob URL will not resolve in a worker even if it's in the window's module graph"
],
"microtasks": {
"basic.any.html": [
"import() should not drain the microtask queue if it fails during specifier resolution",
"import() should not drain the microtask queue when loading an already loaded module"
],
"basic.any.worker.html": [
"import() should not drain the microtask queue if it fails during specifier resolution",
"import() should not drain the microtask queue when loading an already loaded module"
],
"css-import-in-worker.any.worker.html": true,
"with-import-assertions.any.html": true,
"with-import-assertions.any.worker.html": true
}
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
},
"import-meta": {
"import-meta-url.any.worker-module.html": true,
"import-meta-object.any.worker-module.html": true,
"import-meta-resolve.any.worker-module.html": [
"import.meta.resolve is a function with the right properties",
"import.meta.resolve is not a constructor"
]
2021-09-25 09:27:34 -04:00
}
}
}
},
"document-metadata": {
"the-style-element": {
"mutations.window.html": false
}
},
"embedded-content": {
"the-iframe-element": {
"cross-origin-to-whom-part-2.window.html": false,
"cross-origin-to-whom.window.html": false,
"sandbox-top-navigation-child-special-cases.tentative.sub.window.html": false,
"sandbox-top-navigation-child.tentative.sub.window.html": false,
"sandbox-top-navigation-escalate-privileges.tentative.sub.window.html": false,
"sandbox-top-navigation-grandchild.tentative.sub.window.html": false
},
"the-img-element": {
"historical-progress-event.window.html": false
}
},
"forms": {
"form-control-infrastructure": {
"association.window.html": false
},
"form-submission-0": {
"FormDataEvent.window.html": false,
"SubmitEvent.window.html": false,
"form-data-set-empty-file.window.html": false,
"historical.window.html": false,
"multipart-formdata.window.html": false,
"submission-checks.window.html": false,
"text-plain.window.html": false,
"urlencoded2.window.html": false
},
"the-output-element": {
"mutations.window.html": false
},
"the-progress-element": {
"progress.window.html": false
},
"the-textarea-element": {
"wrapping-transformation.window.html": false
}
},
"links": {
"following-hyperlinks": {
"activation-behavior.window.html": false,
"active-document.window.html": false
}
2021-09-25 09:27:34 -04:00
}
},
"webappapis": {
2021-02-15 20:10:59 -05:00
"atob": {
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"base64.any.html": true,
"base64.any.worker.html": true
2021-02-15 20:10:59 -05:00
},
"timers": {
2021-12-06 10:03:09 -05:00
"clearinterval-from-callback.any.html": true,
"clearinterval-from-callback.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"cleartimeout-clearinterval.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"cleartimeout-clearinterval.any.worker.html": true,
2021-12-06 10:03:09 -05:00
"evil-spec-example.any.html": true,
"evil-spec-example.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"missing-timeout-setinterval.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"missing-timeout-setinterval.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"negative-setinterval.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"negative-setinterval.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"negative-settimeout.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"negative-settimeout.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"type-long-setinterval.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"type-long-setinterval.any.worker.html": true,
"type-long-settimeout.any.html": true,
"type-long-settimeout.any.worker.html": true
},
"microtask-queuing": {
"queue-microtask-exceptions.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"queue-microtask.any.html": true,
"queue-microtask.any.worker.html": true,
"queue-microtask-exceptions.any.worker.html": true,
"queue-microtask.window.html": false
2021-08-09 12:49:31 -04:00
},
2021-09-25 09:27:34 -04:00
"scripting": {
"reporterror.any.html": false,
"reporterror.any.worker.html": false,
"event-loops": {
"fully_active_document.window.html": false
},
"events": {
"event-handler-processing-algorithm-error": {
"synthetic-errorevent-click.worker.html": true,
"workerglobalscope-runtime-error.worker.html": true,
"workerglobalscope-synthetic-errorevent.worker.html": true,
"workerglobalscope-synthetic-event.worker.html": true
},
"event-handler-removal.window.html": false,
"event-handler-spec-example.window.html": false,
"invalid-uncompiled-raw-handler-compiled-late.window.html": false,
"invalid-uncompiled-raw-handler-compiled-once.window.html": false,
"invalid-uncompiled-raw-handler-keeps-position.window.html": false
},
"processing-model-2": {
"integration-with-the-javascript-agent-formalism": {
"requires-failure.https.any.html": false,
"requires-success.any.worker.html": true
}
}
2021-09-25 09:27:34 -04:00
},
2021-08-09 12:49:31 -04:00
"structured-clone": {
"structured-clone.any.html": [
"Blob basic",
"Blob unpaired high surrogate (invalid utf-8)",
"Blob unpaired low surrogate (invalid utf-8)",
"Blob paired surrogates (invalid utf-8)",
"Blob empty",
"Blob NUL",
"Array Blob object, Blob basic",
"Array Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Array Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Array Blob object, Blob paired surrogates (invalid utf-8)",
"Array Blob object, Blob empty",
"Array Blob object, Blob NUL",
"Array Blob object, two Blobs",
"Object Blob object, Blob basic",
"Object Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Object Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Object Blob object, Blob paired surrogates (invalid utf-8)",
"Object Blob object, Blob empty",
"Object Blob object, Blob NUL",
2021-09-25 09:27:34 -04:00
"File basic",
"Serializing a non-serializable platform object fails",
"An object whose interface is deleted from the global must still deserialize",
"A subclass instance will deserialize as its closest serializable superclass",
"Resizable ArrayBuffer",
"Growable SharedArrayBuffer",
"Length-tracking TypedArray",
"Length-tracking DataView",
"Serializing OOB TypedArray throws",
"Serializing OOB DataView throws",
"A subclass instance will be received as its closest transferable superclass",
"Resizable ArrayBuffer is transferable",
"Length-tracking TypedArray is transferable",
"Length-tracking DataView is transferable",
"Transferring OOB TypedArray throws",
"Transferring OOB DataView throws"
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
],
"structured-clone.any.worker.html": [
"Blob basic",
"Blob unpaired high surrogate (invalid utf-8)",
"Blob unpaired low surrogate (invalid utf-8)",
"Blob paired surrogates (invalid utf-8)",
"Blob empty",
"Blob NUL",
"Array Blob object, Blob basic",
"Array Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Array Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Array Blob object, Blob paired surrogates (invalid utf-8)",
"Array Blob object, Blob empty",
"Array Blob object, Blob NUL",
"Array Blob object, two Blobs",
"Object Blob object, Blob basic",
"Object Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Object Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Object Blob object, Blob paired surrogates (invalid utf-8)",
"Object Blob object, Blob empty",
"Object Blob object, Blob NUL",
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"File basic",
"Serializing a non-serializable platform object fails",
"An object whose interface is deleted from the global must still deserialize",
"A subclass instance will deserialize as its closest serializable superclass",
"Resizable ArrayBuffer",
"Growable SharedArrayBuffer",
"Length-tracking TypedArray",
"Length-tracking DataView",
"Serializing OOB TypedArray throws",
"Serializing OOB DataView throws",
"A subclass instance will be received as its closest transferable superclass",
"Resizable ArrayBuffer is transferable",
"Length-tracking TypedArray is transferable",
"Length-tracking DataView is transferable",
"Transferring OOB TypedArray throws",
"Transferring OOB DataView throws"
2021-08-09 12:49:31 -04:00
]
},
"dynamic-markup-insertion": {
"closing-the-input-stream": {
"load-event-after-location-set-during-write.window.html": false
},
"document-write": {
"contentType.window.html": false,
"during-readystatechange.window.html": false
},
"opening-the-input-stream": {
"abort-refresh-immediate.window.html": false,
"abort-refresh-multisecond-header.window.html": false,
"abort-refresh-multisecond-meta.window.html": false,
"abort-while-navigating.window.html": false,
"abort.sub.window.html": false,
"aborted-parser.window.html": false,
"active.window.html": false,
"bailout-exception-vs-return-origin.sub.window.html": false,
"bailout-exception-vs-return-xml.window.html": false,
"bailout-side-effects-ignore-opens-during-unload.window.html": false,
"bailout-side-effects-same-origin-domain.sub.window.html": false,
"bailout-side-effects-synchronous-script.window.html": false,
"bailout-side-effects-xml.window.html": false,
"beforeunload.window.html": false,
"crbug-583445-regression.window.html": false,
"custom-element.window.html": false,
"encoding.window.html": false,
"event-listeners.window.html": false,
"history-state.window.html": false,
"history.window.html": false,
"ignore-opens-during-unload.window.html": false,
"mutation-events.window.html": false,
"mutation-observer.window.html": false,
"no-new-global.window.html": false,
"quirks.window.html": false,
"readiness.window.html": false,
"reload.window.html": false,
"remove-initial-about-blankness.window.html": false,
"tasks.window.html": false,
"type-argument-plaintext.window.html": false,
"type-argument.window.html": false,
"unload.window.html": false,
"url-entry-document-sync-call.window.html": false,
"url-entry-document.window.html": false,
"url-fragment.window.html": false,
"url.window.html": false
}
},
"system-state-and-capabilities": {
"the-navigator-object": {
"clientinformation.window.html": false,
"historical.https.window.html": [
"registerProtocolHandler has no third argument"
],
"navigator.any.html": [
"appCodeName",
"appName",
"appVersion",
"platform",
"product",
"productSub",
"userAgent value",
"vendor",
"vendorSub",
"taintEnabled",
"oscpu"
],
"navigator.any.worker.html": false,
"per-global.window.html": false
}
}
},
"cross-origin-embedder-policy": {
"credentialless": {
"cache-storage.https.window.html?dedicated_worker": false,
"cache-storage.https.window.html?document": false,
"cache-storage.https.window.html?service_worker": false,
"cache-storage.https.window.html?shared_worker": false,
"cache.window.html": false,
"cross-origin-isolated.window.html": false,
"dedicated-worker.https.window.html": false,
"fetch.https.window.html": false,
"iframe-coep-credentialless.https.window.html?1-4": false,
"iframe-coep-credentialless.https.window.html?5-9": false,
"iframe-coep-credentialless.https.window.html?9-last": false,
"iframe-coep-none.https.window.html?1-4": false,
"iframe-coep-none.https.window.html?5-last": false,
"iframe-coep-require-corp.https.window.html?1-4": false,
"iframe-coep-require-corp.https.window.html?5-9": false,
"iframe-coep-require-corp.https.window.html?9-last": false,
"iframe.window.html": false,
"image.https.window.html": false,
"link.https.window.html": false,
"redirect.window.html": false,
"reporting-navigation.https.window.html": false,
"reporting-subresource-corp.https.window.html": false,
"script.https.window.html": false,
"service-worker-coep-credentialless-proxy.https.window.html": false,
"service-worker-coep-none-proxy.https.window.html": false,
"service-worker.https.window.html": false,
"shared-worker.https.window.html": false,
"video.https.window.html": false
},
"cross-origin-isolated-permission-iframe.https.window.html": false,
"cross-origin-isolated-permission-worker.https.window.html": false,
"reflection-credentialless.tentative.https.any.html": false,
"reflection-credentialless.tentative.https.any.worker.html": false,
"reflection-require-corp.tentative.https.any.html": false,
"reflection-require-corp.tentative.https.any.worker.html": false,
"reflection-unsafe-none.tentative.https.any.html": false,
"reflection-unsafe-none.tentative.https.any.worker.html": false,
"reporting-to-document-reporting-endpoint.https.window.html": false
},
"dom": {
"elements": {
"global-attributes": {
"dataset-binding.window.html": false
},
"the-innertext-and-outertext-properties": {
"multiple-text-nodes.window.html": false
}
},
"idlharness-shadowrealm.window.html": false,
"idlharness.worker.html": false,
"self-origin.any.html": false,
"self-origin.any.worker.html": false
},
"infrastructure": {
"safe-passing-of-structured-data": {
"messagechannel.any.html": [
"Blob basic",
"Blob unpaired high surrogate (invalid utf-8)",
"Blob unpaired low surrogate (invalid utf-8)",
"Blob paired surrogates (invalid utf-8)",
"Blob empty",
"Blob NUL",
"Array Blob object, Blob basic",
"Array Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Array Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Array Blob object, Blob paired surrogates (invalid utf-8)",
"Array Blob object, Blob empty",
"Array Blob object, Blob NUL",
"Array Blob object, two Blobs",
"Object Blob object, Blob basic",
"Object Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Object Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Object Blob object, Blob paired surrogates (invalid utf-8)",
"Object Blob object, Blob empty",
"Object Blob object, Blob NUL",
"File basic",
"FileList empty",
"Array FileList object, FileList empty",
"Object FileList object, FileList empty",
"ImageData 1x1 transparent black",
"ImageData 1x1 non-transparent non-black",
"Array ImageData object, ImageData 1x1 transparent black",
"Array ImageData object, ImageData 1x1 non-transparent non-black",
"Object ImageData object, ImageData 1x1 transparent black",
"Object ImageData object, ImageData 1x1 non-transparent non-black",
"ImageBitmap 1x1 transparent black",
"ImageBitmap 1x1 non-transparent non-black",
"Array ImageBitmap object, ImageBitmap 1x1 transparent black",
"Array ImageBitmap object, ImageBitmap 1x1 transparent non-black",
"Object ImageBitmap object, ImageBitmap 1x1 transparent black",
"Object ImageBitmap object, ImageBitmap 1x1 transparent non-black",
"Serializing a non-serializable platform object fails",
"An object whose interface is deleted from the global must still deserialize",
"A subclass instance will deserialize as its closest serializable superclass",
"Resizable ArrayBuffer",
"Growable SharedArrayBuffer",
"Length-tracking TypedArray",
"Length-tracking DataView",
"Serializing OOB TypedArray throws",
"Serializing OOB DataView throws",
"A subclass instance will be received as its closest transferable superclass",
"Resizable ArrayBuffer is transferable",
"Length-tracking TypedArray is transferable",
"Length-tracking DataView is transferable",
"Transferring OOB TypedArray throws",
"Transferring OOB DataView throws"
],
"messagechannel.any.worker.html": [
"Blob basic",
"Blob unpaired high surrogate (invalid utf-8)",
"Blob unpaired low surrogate (invalid utf-8)",
"Blob paired surrogates (invalid utf-8)",
"Blob empty",
"Blob NUL",
"Array Blob object, Blob basic",
"Array Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Array Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Array Blob object, Blob paired surrogates (invalid utf-8)",
"Array Blob object, Blob empty",
"Array Blob object, Blob NUL",
"Array Blob object, two Blobs",
"Object Blob object, Blob basic",
"Object Blob object, Blob unpaired high surrogate (invalid utf-8)",
"Object Blob object, Blob unpaired low surrogate (invalid utf-8)",
"Object Blob object, Blob paired surrogates (invalid utf-8)",
"Object Blob object, Blob empty",
"Object Blob object, Blob NUL",
"File basic",
"Serializing a non-serializable platform object fails",
"An object whose interface is deleted from the global must still deserialize",
"A subclass instance will deserialize as its closest serializable superclass",
"Resizable ArrayBuffer",
"Growable SharedArrayBuffer",
"Length-tracking TypedArray",
"Length-tracking DataView",
"Serializing OOB TypedArray throws",
"Serializing OOB DataView throws",
"A subclass instance will be received as its closest transferable superclass",
"Resizable ArrayBuffer is transferable",
"Length-tracking TypedArray is transferable",
"Length-tracking DataView is transferable",
"Transferring OOB TypedArray throws",
"Transferring OOB DataView throws"
],
"shared-array-buffers": {
"no-coop-coep.https.any.html": false,
"no-coop-coep.https.any.worker.html": false,
"serialization-via-idb.any.html": false,
"serialization-via-idb.any.worker.html": false,
"serialization-via-notifications-api.any.html": false,
"serialization-via-notifications-api.any.worker.html": false
},
"structured-cloning-error-stack-optional.sub.window.html": [
"page-created Error (cross-site iframe)",
"page-created Error (same-origin iframe)",
"page-created DOMException (structuredClone())",
"page-created DOMException (cross-site iframe)",
"page-created DOMException (same-origin iframe)",
"JS-engine-created TypeError (cross-site iframe)",
"JS-engine-created TypeError (same-origin iframe)",
"web API-created TypeError (cross-site iframe)",
"web API-created TypeError (same-origin iframe)",
"web API-created DOMException (cross-site iframe)",
"web API-created DOMException (same-origin iframe)",
"page-created DOMException (worker)"
],
"transfer-errors.window.html": false,
"window-postmessage.window.html": false
},
"urls": {
"terminology-0": {
"document-base-url-about-srcdoc.https.window.html": false,
"document-base-url-changes-about-srcdoc.https.window.html": false,
"document-base-url-changes-after-nav-about-srcdoc.https.window.html": false,
"document-base-url-initiated-grand-parent.https.window.html": false
}
}
},
"interaction": {
"focus": {
"composed.window.html": false
}
}
},
"webstorage": {
"defineProperty.window.html": true,
"set.window.html": true,
"storage_enumerate.window.html": true,
"storage_in.window.html": true,
"event_constructor.window.html": false,
"event_initstorageevent.window.html": false,
"missing_arguments.window.html": true,
"storage_builtins.window.html": true,
"storage_clear.window.html": true,
"storage_functions_not_overwritten.window.html": true,
"storage_getitem.window.html": true,
"storage_indexing.window.html": true,
"storage_key.window.html": true,
"storage_key_empty_string.window.html": true,
"storage_length.window.html": true,
"storage_local_setitem_quotaexceedederr.window.html": true,
"storage_removeitem.window.html": true,
"storage_session_setitem_quotaexceedederr.window.html": true,
"storage_set_value_enumerate.window.html": true,
"storage_setitem.window.html": [
"localStorage[] = \"\ud800\"",
"localStorage[] = \"\udbff\"",
"localStorage[] = \"\udc00\"",
"localStorage[] = \"\udfff\"",
"localStorage[] = \"\ud83ca\"",
"localStorage[] = \"a\udf4d\"",
"sessionStorage[] = \"\ud800\"",
"sessionStorage[] = \"\udbff\"",
"sessionStorage[] = \"\udc00\"",
"sessionStorage[] = \"\udfff\"",
"sessionStorage[] = \"\ud83ca\"",
"sessionStorage[] = \"a\udf4d\""
],
"storage_string_conversion.window.html": true,
"storage_supported_property_names.window.html": true,
"symbol-props.window.html": [
"localStorage: defineProperty not configurable",
"sessionStorage: defineProperty not configurable"
],
"localstorage-cross-origin-iframe.tentative.https.window.html": false,
"storage_local_window_open.window.html": false,
"storage_session_window_noopener.window.html": false,
"storage_session_window_open.window.html": false,
"storage_session_window_reopen.window.html": false
},
"webmessaging": {
"broadcastchannel": {
"basics.any.html": [
"postMessage results in correct event"
],
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"basics.any.worker.html": [
"postMessage results in correct event"
],
"interface.any.html": true,
"interface.any.worker.html": true,
"origin.window.html": false
},
"message-channels": {
"basics.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"basics.any.worker.html": true,
"close.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"close.any.worker.html": true,
"dictionary-transferrable.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"dictionary-transferrable.any.worker.html": true,
"implied-start.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"implied-start.any.worker.html": true,
"no-start.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"no-start.any.worker.html": true,
"user-activation.tentative.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"user-activation.tentative.any.worker.html": false,
"worker-post-after-close.any.html": false,
"worker.any.html": false,
"detached-iframe.window.html": false,
"worker-post-after-close.any.worker.html": false,
"worker.any.worker.html": false
},
"Channel_postMessage_Blob.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_Blob.any.worker.html": false,
"Channel_postMessage_DataCloneErr.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_DataCloneErr.any.worker.html": true,
"Channel_postMessage_clone_port.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_clone_port.any.worker.html": true,
"Channel_postMessage_clone_port_error.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_clone_port_error.any.worker.html": true,
"Channel_postMessage_event_properties.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_event_properties.any.worker.html": true,
"Channel_postMessage_ports_readonly_array.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_ports_readonly_array.any.worker.html": false,
"Channel_postMessage_target_source.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_target_source.any.worker.html": true,
"Channel_postMessage_transfer_xsite_incoming_messages.window.html": false,
"Channel_postMessage_with_transfer_entangled.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_with_transfer_entangled.any.worker.html": true,
"Channel_postMessage_with_transfer_incoming_messages.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_with_transfer_incoming_messages.any.worker.html": true,
"Channel_postMessage_with_transfer_outgoing_messages.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Channel_postMessage_with_transfer_outgoing_messages.any.worker.html": true,
"MessageEvent-trusted.any.html": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"MessageEvent-trusted.any.worker.html": false,
"MessageEvent-trusted.window.html": false,
"MessageEvent.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"MessageEvent.any.worker.html": true,
"MessagePort_initial_disabled.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"MessagePort_initial_disabled.any.worker.html": true,
"MessagePort_onmessage_start.any.html": true,
"MessagePort_onmessage_start.any.worker.html": true,
"postMessage_MessagePorts_xsite.sub.window.html": false
},
"xhr": {
"formdata": {
2021-05-09 10:32:30 -04:00
"append.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"append.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"constructor.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"delete.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"delete.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"foreach.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"foreach.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"get.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"get.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"has.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"has.any.worker.html": true,
2021-05-09 10:32:30 -04:00
"set-blob.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"set-blob.any.worker.html": true,
"set.any.html": true,
"set.any.worker.html": true,
"iteration.any.html": true,
"iteration.any.worker.html": true
},
"XMLHttpRequest-withCredentials.any.html": false,
"XMLHttpRequest-withCredentials.any.worker.html": false,
"abort-after-receive.any.html": false,
"abort-after-receive.any.worker.html": false,
"abort-after-send.any.html": false,
"abort-after-send.any.worker.html": false,
"abort-after-stop.window.html": false,
"abort-after-timeout.any.html": false,
"abort-after-timeout.any.worker.html": false,
"abort-during-done.window.html": false,
"abort-during-headers-received.window.html": false,
"abort-during-loading.window.html": false,
"abort-during-open.any.html": false,
"abort-during-open.any.worker.html": false,
"abort-during-readystatechange.any.html": false,
"abort-during-readystatechange.any.worker.html": false,
"abort-during-unsent.any.html": false,
"abort-during-unsent.any.worker.html": false,
"abort-during-upload.any.html": false,
"abort-during-upload.any.worker.html": false,
"abort-event-abort.any.html": false,
"abort-event-abort.any.worker.html": false,
"abort-event-listeners.any.html": false,
"abort-event-listeners.any.worker.html": false,
"abort-event-loadend.any.html": false,
"abort-event-loadend.any.worker.html": false,
"abort-upload-event-abort.any.html": false,
"abort-upload-event-abort.any.worker.html": false,
"abort-upload-event-loadend.any.html": false,
"abort-upload-event-loadend.any.worker.html": false,
"access-control-and-redirects-async-same-origin.any.html": false,
"access-control-and-redirects-async-same-origin.any.worker.html": false,
"access-control-and-redirects-async.any.html": false,
"access-control-and-redirects-async.any.worker.html": false,
"access-control-and-redirects.any.html": false,
"access-control-and-redirects.any.worker.html": false,
"access-control-basic-allow-access-control-origin-header.any.html": false,
"access-control-basic-allow-access-control-origin-header.any.worker.html": false,
"access-control-basic-allow-async.any.html": false,
"access-control-basic-allow-async.any.worker.html": false,
"access-control-basic-allow-non-cors-safelisted-method-async.any.html": false,
"access-control-basic-allow-non-cors-safelisted-method-async.any.worker.html": false,
"access-control-basic-allow-non-cors-safelisted-method.any.html": false,
"access-control-basic-allow-non-cors-safelisted-method.any.worker.html": false,
"access-control-basic-allow-preflight-cache-invalidation-by-header.any.html": false,
"access-control-basic-allow-preflight-cache-invalidation-by-header.any.worker.html": false,
"access-control-basic-allow-preflight-cache-invalidation-by-method.any.html": false,
"access-control-basic-allow-preflight-cache-invalidation-by-method.any.worker.html": false,
"access-control-basic-allow-preflight-cache-timeout.any.html": false,
"access-control-basic-allow-preflight-cache-timeout.any.worker.html": false,
"access-control-basic-allow-preflight-cache.any.html": false,
"access-control-basic-allow-preflight-cache.any.worker.html": false,
"access-control-basic-allow-star.any.html": false,
"access-control-basic-allow-star.any.worker.html": false,
"access-control-basic-allow.any.html": false,
"access-control-basic-allow.any.worker.html": false,
"access-control-preflight-request-allow-headers-returns-star.any.html": false,
"access-control-preflight-request-allow-headers-returns-star.any.worker.html": false,
"access-control-preflight-request-header-returns-origin.any.html": false,
"access-control-preflight-request-header-returns-origin.any.worker.html": false,
"content-type-unmodified.any.html": false,
"content-type-unmodified.any.worker.html": false,
"cors-expose-star.sub.any.html": false,
"cors-expose-star.sub.any.worker.html": false,
"cors-upload.any.html": false,
"cors-upload.any.worker.html": false,
"event-abort.any.html": false,
"event-abort.any.worker.html": false,
"event-error.sub.any.html": false,
"event-error.sub.any.worker.html": false,
"event-load.any.html": false,
"event-load.any.worker.html": false,
"event-loadend.any.html": false,
"event-loadend.any.worker.html": false,
"event-loadstart-upload.any.html": false,
"event-loadstart-upload.any.worker.html": false,
"event-loadstart.any.html": false,
"event-loadstart.any.worker.html": false,
"event-progress.any.html": false,
"event-progress.any.worker.html": false,
"event-readystate-sync-open.any.html": false,
"event-readystate-sync-open.any.worker.html": false,
"event-readystatechange-loaded.any.html": false,
"event-readystatechange-loaded.any.worker.html": false,
"event-timeout-order.any.html": false,
"event-timeout-order.any.worker.html": false,
"event-timeout.any.html": false,
"event-timeout.any.worker.html": false,
"event-upload-progress-crossorigin.any.html": false,
"event-upload-progress-crossorigin.any.worker.html": false,
"event-upload-progress.any.html": false,
"event-upload-progress.any.worker.html": false,
"getresponseheader.any.html": false,
"getresponseheader.any.worker.html": false,
"idlharness.any.html": [
"XMLHttpRequestEventTarget interface: existence and properties of interface object",
"XMLHttpRequestEventTarget interface object length",
"XMLHttpRequestEventTarget interface object name",
"XMLHttpRequestEventTarget interface: existence and properties of interface prototype object",
"XMLHttpRequestEventTarget interface: existence and properties of interface prototype object's \"constructor\" property",
"XMLHttpRequestEventTarget interface: existence and properties of interface prototype object's @@unscopables property",
"XMLHttpRequestEventTarget interface: attribute onloadstart",
"XMLHttpRequestEventTarget interface: attribute onprogress",
"XMLHttpRequestEventTarget interface: attribute onabort",
"XMLHttpRequestEventTarget interface: attribute onerror",
"XMLHttpRequestEventTarget interface: attribute onload",
"XMLHttpRequestEventTarget interface: attribute ontimeout",
"XMLHttpRequestEventTarget interface: attribute onloadend",
"XMLHttpRequestUpload interface: existence and properties of interface object",
"XMLHttpRequestUpload interface object length",
"XMLHttpRequestUpload interface object name",
"XMLHttpRequestUpload interface: existence and properties of interface prototype object",
"XMLHttpRequestUpload interface: existence and properties of interface prototype object's \"constructor\" property",
"XMLHttpRequestUpload interface: existence and properties of interface prototype object's @@unscopables property",
"XMLHttpRequestUpload must be primary interface of (new XMLHttpRequest()).upload",
"Stringification of (new XMLHttpRequest()).upload",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onloadstart\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onprogress\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onabort\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onerror\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onload\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"ontimeout\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onloadend\" with the proper type",
"XMLHttpRequest interface: existence and properties of interface object",
"XMLHttpRequest interface object length",
"XMLHttpRequest interface object name",
"XMLHttpRequest interface: existence and properties of interface prototype object",
"XMLHttpRequest interface: existence and properties of interface prototype object's \"constructor\" property",
"XMLHttpRequest interface: existence and properties of interface prototype object's @@unscopables property",
"XMLHttpRequest interface: attribute onreadystatechange",
"XMLHttpRequest interface: constant UNSENT on interface object",
"XMLHttpRequest interface: constant UNSENT on interface prototype object",
"XMLHttpRequest interface: constant OPENED on interface object",
"XMLHttpRequest interface: constant OPENED on interface prototype object",
"XMLHttpRequest interface: constant HEADERS_RECEIVED on interface object",
"XMLHttpRequest interface: constant HEADERS_RECEIVED on interface prototype object",
"XMLHttpRequest interface: constant LOADING on interface object",
"XMLHttpRequest interface: constant LOADING on interface prototype object",
"XMLHttpRequest interface: constant DONE on interface object",
"XMLHttpRequest interface: constant DONE on interface prototype object",
"XMLHttpRequest interface: attribute readyState",
"XMLHttpRequest interface: operation open(ByteString, USVString)",
"XMLHttpRequest interface: operation open(ByteString, USVString, boolean, optional USVString?, optional USVString?)",
"XMLHttpRequest interface: operation setRequestHeader(ByteString, ByteString)",
"XMLHttpRequest interface: attribute timeout",
"XMLHttpRequest interface: attribute withCredentials",
"XMLHttpRequest interface: attribute upload",
"XMLHttpRequest interface: operation send(optional (Document or XMLHttpRequestBodyInit)?)",
"XMLHttpRequest interface: operation abort()",
"XMLHttpRequest interface: attribute responseURL",
"XMLHttpRequest interface: attribute status",
"XMLHttpRequest interface: attribute statusText",
"XMLHttpRequest interface: operation getResponseHeader(ByteString)",
"XMLHttpRequest interface: operation getAllResponseHeaders()",
"XMLHttpRequest interface: operation overrideMimeType(DOMString)",
"XMLHttpRequest interface: attribute responseType",
"XMLHttpRequest interface: attribute response",
"XMLHttpRequest interface: attribute responseText",
"XMLHttpRequest interface: attribute responseXML",
"XMLHttpRequest must be primary interface of new XMLHttpRequest()",
"Stringification of new XMLHttpRequest()",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"onreadystatechange\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"UNSENT\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"OPENED\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"HEADERS_RECEIVED\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"LOADING\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"DONE\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"readyState\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"open(ByteString, USVString)\" with the proper type",
"XMLHttpRequest interface: calling open(ByteString, USVString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"open(ByteString, USVString, boolean, optional USVString?, optional USVString?)\" with the proper type",
"XMLHttpRequest interface: calling open(ByteString, USVString, boolean, optional USVString?, optional USVString?) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"setRequestHeader(ByteString, ByteString)\" with the proper type",
"XMLHttpRequest interface: calling setRequestHeader(ByteString, ByteString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"timeout\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"withCredentials\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"upload\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"send(optional (Document or XMLHttpRequestBodyInit)?)\" with the proper type",
"XMLHttpRequest interface: calling send(optional (Document or XMLHttpRequestBodyInit)?) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"abort()\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseURL\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"status\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"statusText\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"getResponseHeader(ByteString)\" with the proper type",
"XMLHttpRequest interface: calling getResponseHeader(ByteString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"getAllResponseHeaders()\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"overrideMimeType(DOMString)\" with the proper type",
"XMLHttpRequest interface: calling overrideMimeType(DOMString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseType\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"response\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseText\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseXML\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onloadstart\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onprogress\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onabort\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onerror\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onload\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"ontimeout\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onloadend\" with the proper type",
"FormData interface object length",
"FormData interface: operation append(USVString, USVString)",
"FormData interface: operation append(USVString, Blob, optional USVString)",
"FormData interface: operation set(USVString, USVString)",
"FormData interface: operation set(USVString, Blob, optional USVString)",
"ProgressEvent interface: attribute lengthComputable",
"ProgressEvent interface: attribute loaded",
"ProgressEvent interface: attribute total",
"ProgressEvent interface: new ProgressEvent(\"type\") must inherit property \"lengthComputable\" with the proper type",
"ProgressEvent interface: new ProgressEvent(\"type\") must inherit property \"loaded\" with the proper type",
"ProgressEvent interface: new ProgressEvent(\"type\") must inherit property \"total\" with the proper type",
"idl_test setup"
],
"idlharness.any.worker.html": [
"XMLHttpRequestEventTarget interface: existence and properties of interface object",
"XMLHttpRequestEventTarget interface object length",
"XMLHttpRequestEventTarget interface object name",
"XMLHttpRequestEventTarget interface: existence and properties of interface prototype object",
"XMLHttpRequestEventTarget interface: existence and properties of interface prototype object's \"constructor\" property",
"XMLHttpRequestEventTarget interface: existence and properties of interface prototype object's @@unscopables property",
"XMLHttpRequestEventTarget interface: attribute onloadstart",
"XMLHttpRequestEventTarget interface: attribute onprogress",
"XMLHttpRequestEventTarget interface: attribute onabort",
"XMLHttpRequestEventTarget interface: attribute onerror",
"XMLHttpRequestEventTarget interface: attribute onload",
"XMLHttpRequestEventTarget interface: attribute ontimeout",
"XMLHttpRequestEventTarget interface: attribute onloadend",
"XMLHttpRequestUpload interface: existence and properties of interface object",
"XMLHttpRequestUpload interface object length",
"XMLHttpRequestUpload interface object name",
"XMLHttpRequestUpload interface: existence and properties of interface prototype object",
"XMLHttpRequestUpload interface: existence and properties of interface prototype object's \"constructor\" property",
"XMLHttpRequestUpload interface: existence and properties of interface prototype object's @@unscopables property",
"XMLHttpRequestUpload must be primary interface of (new XMLHttpRequest()).upload",
"Stringification of (new XMLHttpRequest()).upload",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onloadstart\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onprogress\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onabort\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onerror\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onload\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"ontimeout\" with the proper type",
"XMLHttpRequestEventTarget interface: (new XMLHttpRequest()).upload must inherit property \"onloadend\" with the proper type",
"XMLHttpRequest interface: existence and properties of interface object",
"XMLHttpRequest interface object length",
"XMLHttpRequest interface object name",
"XMLHttpRequest interface: existence and properties of interface prototype object",
"XMLHttpRequest interface: existence and properties of interface prototype object's \"constructor\" property",
"XMLHttpRequest interface: existence and properties of interface prototype object's @@unscopables property",
"XMLHttpRequest interface: attribute onreadystatechange",
"XMLHttpRequest interface: constant UNSENT on interface object",
"XMLHttpRequest interface: constant UNSENT on interface prototype object",
"XMLHttpRequest interface: constant OPENED on interface object",
"XMLHttpRequest interface: constant OPENED on interface prototype object",
"XMLHttpRequest interface: constant HEADERS_RECEIVED on interface object",
"XMLHttpRequest interface: constant HEADERS_RECEIVED on interface prototype object",
"XMLHttpRequest interface: constant LOADING on interface object",
"XMLHttpRequest interface: constant LOADING on interface prototype object",
"XMLHttpRequest interface: constant DONE on interface object",
"XMLHttpRequest interface: constant DONE on interface prototype object",
"XMLHttpRequest interface: attribute readyState",
"XMLHttpRequest interface: operation open(ByteString, USVString)",
"XMLHttpRequest interface: operation open(ByteString, USVString, boolean, optional USVString?, optional USVString?)",
"XMLHttpRequest interface: operation setRequestHeader(ByteString, ByteString)",
"XMLHttpRequest interface: attribute timeout",
"XMLHttpRequest interface: attribute withCredentials",
"XMLHttpRequest interface: attribute upload",
"XMLHttpRequest interface: operation send(optional (Document or XMLHttpRequestBodyInit)?)",
"XMLHttpRequest interface: operation abort()",
"XMLHttpRequest interface: attribute responseURL",
"XMLHttpRequest interface: attribute status",
"XMLHttpRequest interface: attribute statusText",
"XMLHttpRequest interface: operation getResponseHeader(ByteString)",
"XMLHttpRequest interface: operation getAllResponseHeaders()",
"XMLHttpRequest interface: operation overrideMimeType(DOMString)",
"XMLHttpRequest interface: attribute responseType",
"XMLHttpRequest interface: attribute response",
"XMLHttpRequest interface: attribute responseText",
"XMLHttpRequest interface: member responseXML",
"XMLHttpRequest must be primary interface of new XMLHttpRequest()",
"Stringification of new XMLHttpRequest()",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"onreadystatechange\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"UNSENT\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"OPENED\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"HEADERS_RECEIVED\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"LOADING\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"DONE\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"readyState\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"open(ByteString, USVString)\" with the proper type",
"XMLHttpRequest interface: calling open(ByteString, USVString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"open(ByteString, USVString, boolean, optional USVString?, optional USVString?)\" with the proper type",
"XMLHttpRequest interface: calling open(ByteString, USVString, boolean, optional USVString?, optional USVString?) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"setRequestHeader(ByteString, ByteString)\" with the proper type",
"XMLHttpRequest interface: calling setRequestHeader(ByteString, ByteString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"timeout\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"withCredentials\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"upload\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"send(optional (Document or XMLHttpRequestBodyInit)?)\" with the proper type",
"XMLHttpRequest interface: calling send(optional (Document or XMLHttpRequestBodyInit)?) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"abort()\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseURL\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"status\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"statusText\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"getResponseHeader(ByteString)\" with the proper type",
"XMLHttpRequest interface: calling getResponseHeader(ByteString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"getAllResponseHeaders()\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"overrideMimeType(DOMString)\" with the proper type",
"XMLHttpRequest interface: calling overrideMimeType(DOMString) on new XMLHttpRequest() with too few arguments must throw TypeError",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseType\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"response\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must inherit property \"responseText\" with the proper type",
"XMLHttpRequest interface: new XMLHttpRequest() must not have property \"responseXML\"",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onloadstart\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onprogress\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onabort\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onerror\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onload\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"ontimeout\" with the proper type",
"XMLHttpRequestEventTarget interface: new XMLHttpRequest() must inherit property \"onloadend\" with the proper type",
"FormData interface object length",
"FormData interface: operation append(USVString, USVString)",
"FormData interface: operation append(USVString, Blob, optional USVString)",
"FormData interface: operation set(USVString, USVString)",
"FormData interface: operation set(USVString, Blob, optional USVString)",
"ProgressEvent interface: attribute lengthComputable",
"ProgressEvent interface: attribute loaded",
"ProgressEvent interface: attribute total",
"ProgressEvent interface: new ProgressEvent(\"type\") must inherit property \"lengthComputable\" with the proper type",
"ProgressEvent interface: new ProgressEvent(\"type\") must inherit property \"loaded\" with the proper type",
"ProgressEvent interface: new ProgressEvent(\"type\") must inherit property \"total\" with the proper type"
],
"json.any.html": false,
"json.any.worker.html": false,
"open-after-stop.window.html": false,
"over-1-meg.any.html": false,
"over-1-meg.any.worker.html": false,
"overridemimetype-done-state.any.html": false,
"overridemimetype-done-state.any.worker.html": false,
"overridemimetype-edge-cases.window.html": false,
"overridemimetype-unsent-state-force-shiftjis.any.html": false,
"overridemimetype-unsent-state-force-shiftjis.any.worker.html": false,
"request-content-length.any.html": false,
"request-content-length.any.worker.html": false,
"response-body-errors.any.html": false,
"response-body-errors.any.worker.html": false,
"responsetype.any.html": false,
"responsetype.any.worker.html": false,
"send-data-arraybuffer.any.html": false,
"send-data-arraybuffer.any.worker.html": false,
"send-data-arraybufferview.any.html": false,
"send-data-arraybufferview.any.worker.html": false,
"send-data-es-object.any.html": false,
"send-data-es-object.any.worker.html": false,
"send-data-formdata.any.html": false,
"send-data-formdata.any.worker.html": false,
"send-data-sharedarraybuffer.any.html": false,
"send-data-sharedarraybuffer.any.worker.html": false,
"send-data-string-invalid-unicode.any.html": false,
"send-data-string-invalid-unicode.any.worker.html": false,
"send-send.any.html": false,
"send-send.any.worker.html": false,
"send-usp.any.html": false,
"send-usp.any.worker.html": false,
"setrequestheader-combining.window.html": false,
"sync-no-progress.any.html": false,
"sync-no-progress.any.worker.html": false,
"sync-no-timeout.any.html": false,
"sync-no-timeout.any.worker.html": false,
"xhr-authorization-redirect.any.html": false,
"xhr-authorization-redirect.any.worker.html": false,
"xhr-timeout-longtask.any.html": false,
"xhr-timeout-longtask.any.worker.html": false
},
"websockets": {
"Close-1000-reason.any.html": true,
"Close-1000-reason.any.html?wpt_flags=h2": false,
"Close-1000-reason.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-1000-reason.any.worker.html": true,
"Close-1000-reason.any.worker.html?wpt_flags=h2": false,
"Close-1000-reason.any.worker.html?wss": true,
"Close-1000-verify-code.any.html": true,
"Close-1000-verify-code.any.html?wpt_flags=h2": false,
"Close-1000-verify-code.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-1000-verify-code.any.worker.html": true,
"Close-1000-verify-code.any.worker.html?wpt_flags=h2": false,
"Close-1000-verify-code.any.worker.html?wss": true,
"Close-1000.any.html": true,
"Close-1000.any.html?wpt_flags=h2": false,
"Close-1000.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-1000.any.worker.html": true,
"Close-1000.any.worker.html?wpt_flags=h2": false,
"Close-1000.any.worker.html?wss": true,
"Close-1005-verify-code.any.html": true,
"Close-1005-verify-code.any.html?wpt_flags=h2": false,
"Close-1005-verify-code.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-1005-verify-code.any.worker.html": true,
"Close-1005-verify-code.any.worker.html?wpt_flags=h2": false,
"Close-1005-verify-code.any.worker.html?wss": true,
"Close-1005.any.html": true,
"Close-1005.any.html?wpt_flags=h2": false,
"Close-1005.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-1005.any.worker.html": true,
"Close-1005.any.worker.html?wpt_flags=h2": false,
"Close-1005.any.worker.html?wss": true,
"Close-2999-reason.any.html": true,
"Close-2999-reason.any.html?wpt_flags=h2": false,
"Close-2999-reason.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-2999-reason.any.worker.html": true,
"Close-2999-reason.any.worker.html?wpt_flags=h2": false,
"Close-2999-reason.any.worker.html?wss": true,
"Close-3000-reason.any.html": true,
"Close-3000-reason.any.html?wpt_flags=h2": false,
"Close-3000-reason.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-3000-reason.any.worker.html": true,
"Close-3000-reason.any.worker.html?wpt_flags=h2": false,
"Close-3000-reason.any.worker.html?wss": true,
"Close-3000-verify-code.any.html": true,
"Close-3000-verify-code.any.html?wpt_flags=h2": false,
"Close-3000-verify-code.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-3000-verify-code.any.worker.html": true,
"Close-3000-verify-code.any.worker.html?wpt_flags=h2": false,
"Close-3000-verify-code.any.worker.html?wss": true,
"Close-4999-reason.any.html": true,
"Close-4999-reason.any.html?wpt_flags=h2": false,
"Close-4999-reason.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-4999-reason.any.worker.html": true,
"Close-4999-reason.any.worker.html?wpt_flags=h2": false,
"Close-4999-reason.any.worker.html?wss": true,
"Close-Reason-124Bytes.any.html": true,
"Close-Reason-124Bytes.any.html?wpt_flags=h2": false,
"Close-Reason-124Bytes.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-Reason-124Bytes.any.worker.html": true,
"Close-Reason-124Bytes.any.worker.html?wpt_flags=h2": false,
"Close-Reason-124Bytes.any.worker.html?wss": true,
"Close-onlyReason.any.html": true,
"Close-onlyReason.any.html?wpt_flags=h2": false,
"Close-onlyReason.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-onlyReason.any.worker.html": true,
"Close-onlyReason.any.worker.html?wpt_flags=h2": false,
"Close-onlyReason.any.worker.html?wss": true,
"Close-readyState-Closed.any.html": true,
"Close-readyState-Closed.any.html?wpt_flags=h2": false,
"Close-readyState-Closed.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-readyState-Closed.any.worker.html": true,
"Close-readyState-Closed.any.worker.html?wpt_flags=h2": false,
"Close-readyState-Closed.any.worker.html?wss": true,
"Close-readyState-Closing.any.html": true,
"Close-readyState-Closing.any.html?wpt_flags=h2": false,
"Close-readyState-Closing.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-readyState-Closing.any.worker.html": true,
"Close-readyState-Closing.any.worker.html?wpt_flags=h2": false,
"Close-readyState-Closing.any.worker.html?wss": true,
"Close-reason-unpaired-surrogates.any.html": true,
"Close-reason-unpaired-surrogates.any.html?wpt_flags=h2": false,
"Close-reason-unpaired-surrogates.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-reason-unpaired-surrogates.any.worker.html": true,
"Close-reason-unpaired-surrogates.any.worker.html?wpt_flags=h2": false,
"Close-reason-unpaired-surrogates.any.worker.html?wss": true,
"Close-server-initiated-close.any.html": true,
"Close-server-initiated-close.any.html?wpt_flags=h2": false,
"Close-server-initiated-close.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-server-initiated-close.any.worker.html": true,
"Close-server-initiated-close.any.worker.html?wpt_flags=h2": false,
"Close-server-initiated-close.any.worker.html?wss": true,
"Close-undefined.any.html": true,
"Close-undefined.any.html?wpt_flags=h2": false,
"Close-undefined.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-undefined.any.worker.html": true,
"Close-undefined.any.worker.html?wpt_flags=h2": false,
"Close-undefined.any.worker.html?wss": true,
"Create-asciiSep-protocol-string.any.html": true,
"Create-asciiSep-protocol-string.any.html?wpt_flags=h2": true,
"Create-asciiSep-protocol-string.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-asciiSep-protocol-string.any.worker.html": true,
"Create-asciiSep-protocol-string.any.worker.html?wpt_flags=h2": true,
"Create-asciiSep-protocol-string.any.worker.html?wss": true,
"Create-blocked-port.any.html": true,
"Create-blocked-port.any.html?wpt_flags=h2": [
"Basic check"
],
"Create-blocked-port.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-blocked-port.any.worker.html": true,
"Create-blocked-port.any.worker.html?wpt_flags=h2": [
"Basic check"
],
"Create-blocked-port.any.worker.html?wss": true,
"Create-extensions-empty.any.html": true,
"Create-extensions-empty.any.html?wpt_flags=h2": false,
"Create-extensions-empty.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-extensions-empty.any.worker.html": true,
"Create-extensions-empty.any.worker.html?wpt_flags=h2": false,
"Create-extensions-empty.any.worker.html?wss": true,
"Create-invalid-urls.any.html": true,
"Create-invalid-urls.any.html?wpt_flags=h2": true,
"Create-invalid-urls.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-invalid-urls.any.worker.html": true,
"Create-invalid-urls.any.worker.html?wpt_flags=h2": true,
"Create-invalid-urls.any.worker.html?wss": true,
"Create-non-absolute-url.any.html": true,
"Create-non-absolute-url.any.html?wpt_flags=h2": true,
"Create-non-absolute-url.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-non-absolute-url.any.worker.html": true,
"Create-non-absolute-url.any.worker.html?wpt_flags=h2": true,
"Create-non-absolute-url.any.worker.html?wss": true,
"Create-nonAscii-protocol-string.any.html": true,
"Create-nonAscii-protocol-string.any.html?wpt_flags=h2": true,
"Create-nonAscii-protocol-string.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-nonAscii-protocol-string.any.worker.html": true,
"Create-nonAscii-protocol-string.any.worker.html?wpt_flags=h2": true,
"Create-nonAscii-protocol-string.any.worker.html?wss": true,
"Create-on-worker-shutdown.any.html": false,
"Create-protocol-with-space.any.html": true,
"Create-protocol-with-space.any.html?wpt_flags=h2": true,
"Create-protocol-with-space.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-protocol-with-space.any.worker.html": true,
"Create-protocol-with-space.any.worker.html?wpt_flags=h2": true,
"Create-protocol-with-space.any.worker.html?wss": true,
"Create-protocols-repeated-case-insensitive.any.html": true,
"Create-protocols-repeated-case-insensitive.any.html?wpt_flags=h2": true,
"Create-protocols-repeated-case-insensitive.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-protocols-repeated-case-insensitive.any.worker.html": true,
"Create-protocols-repeated-case-insensitive.any.worker.html?wpt_flags=h2": true,
"Create-protocols-repeated-case-insensitive.any.worker.html?wss": true,
"Create-protocols-repeated.any.html": true,
"Create-protocols-repeated.any.html?wpt_flags=h2": true,
"Create-protocols-repeated.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-protocols-repeated.any.worker.html": true,
"Create-protocols-repeated.any.worker.html?wpt_flags=h2": true,
"Create-protocols-repeated.any.worker.html?wss": true,
"Create-url-with-space.any.html": true,
"Create-url-with-space.any.html?wpt_flags=h2": true,
"Create-url-with-space.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-url-with-space.any.worker.html": true,
"Create-url-with-space.any.worker.html?wpt_flags=h2": true,
"Create-url-with-space.any.worker.html?wss": true,
"Create-valid-url-array-protocols.any.html": true,
"Create-valid-url-array-protocols.any.html?wpt_flags=h2": false,
"Create-valid-url-array-protocols.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url-array-protocols.any.worker.html": true,
"Create-valid-url-array-protocols.any.worker.html?wpt_flags=h2": false,
"Create-valid-url-array-protocols.any.worker.html?wss": true,
"Create-valid-url-binaryType-blob.any.html": true,
"Create-valid-url-binaryType-blob.any.html?wpt_flags=h2": false,
"Create-valid-url-binaryType-blob.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url-binaryType-blob.any.worker.html": true,
"Create-valid-url-binaryType-blob.any.worker.html?wpt_flags=h2": false,
"Create-valid-url-binaryType-blob.any.worker.html?wss": true,
"Create-valid-url-protocol-empty.any.html": true,
"Create-valid-url-protocol-empty.any.html?wpt_flags=h2": true,
"Create-valid-url-protocol-empty.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url-protocol-empty.any.worker.html": true,
"Create-valid-url-protocol-empty.any.worker.html?wpt_flags=h2": true,
"Create-valid-url-protocol-empty.any.worker.html?wss": true,
"Create-valid-url-protocol-setCorrectly.any.html": true,
"Create-valid-url-protocol-setCorrectly.any.html?wpt_flags=h2": false,
"Create-valid-url-protocol-setCorrectly.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url-protocol-setCorrectly.any.worker.html": true,
"Create-valid-url-protocol-setCorrectly.any.worker.html?wpt_flags=h2": false,
"Create-valid-url-protocol-setCorrectly.any.worker.html?wss": true,
"Create-valid-url-protocol-string.any.html": true,
"Create-valid-url-protocol-string.any.html?wpt_flags=h2": false,
"Create-valid-url-protocol-string.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url-protocol-string.any.worker.html": true,
"Create-valid-url-protocol-string.any.worker.html?wpt_flags=h2": false,
"Create-valid-url-protocol-string.any.worker.html?wss": true,
"Create-valid-url-protocol.any.html": true,
"Create-valid-url-protocol.any.html?wpt_flags=h2": false,
"Create-valid-url-protocol.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url-protocol.any.worker.html": true,
"Create-valid-url-protocol.any.worker.html?wpt_flags=h2": false,
"Create-valid-url-protocol.any.worker.html?wss": true,
"Create-valid-url.any.html": true,
"Create-valid-url.any.html?wpt_flags=h2": false,
"Create-valid-url.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-valid-url.any.worker.html": true,
"Create-valid-url.any.worker.html?wpt_flags=h2": false,
"Create-valid-url.any.worker.html?wss": true,
"Create-wrong-scheme.any.html": true,
"Create-wrong-scheme.any.html?wpt_flags=h2": true,
"Create-wrong-scheme.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Create-wrong-scheme.any.worker.html": true,
"Create-wrong-scheme.any.worker.html?wpt_flags=h2": true,
"Create-wrong-scheme.any.worker.html?wss": true,
"Send-0byte-data.any.html": true,
"Send-0byte-data.any.html?wpt_flags=h2": false,
"Send-0byte-data.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-0byte-data.any.worker.html": true,
"Send-0byte-data.any.worker.html?wpt_flags=h2": false,
"Send-0byte-data.any.worker.html?wss": true,
"Send-65K-data.any.html": true,
"Send-65K-data.any.html?wpt_flags=h2": false,
"Send-65K-data.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-65K-data.any.worker.html": true,
"Send-65K-data.any.worker.html?wpt_flags=h2": false,
"Send-65K-data.any.worker.html?wss": true,
"Send-before-open.any.html": true,
"Send-before-open.any.html?wpt_flags=h2": true,
"Send-before-open.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-before-open.any.worker.html": true,
"Send-before-open.any.worker.html?wpt_flags=h2": true,
"Send-before-open.any.worker.html?wss": true,
"Send-binary-65K-arraybuffer.any.html": true,
"Send-binary-65K-arraybuffer.any.html?wpt_flags=h2": false,
"Send-binary-65K-arraybuffer.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-65K-arraybuffer.any.worker.html": true,
"Send-binary-65K-arraybuffer.any.worker.html?wpt_flags=h2": false,
"Send-binary-65K-arraybuffer.any.worker.html?wss": true,
"Send-binary-arraybuffer.any.html": true,
"Send-binary-arraybuffer.any.html?wpt_flags=h2": false,
"Send-binary-arraybuffer.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybuffer.any.worker.html": true,
"Send-binary-arraybuffer.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybuffer.any.worker.html?wss": true,
"Send-binary-arraybufferview-float32.any.html": true,
"Send-binary-arraybufferview-float32.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-float32.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-float32.any.worker.html": true,
"Send-binary-arraybufferview-float32.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-float32.any.worker.html?wss": true,
"Send-binary-arraybufferview-float64.any.html": true,
"Send-binary-arraybufferview-float64.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-float64.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-float64.any.worker.html": true,
"Send-binary-arraybufferview-float64.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-float64.any.worker.html?wss": true,
"Send-binary-arraybufferview-int16-offset.any.html": true,
"Send-binary-arraybufferview-int16-offset.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-int16-offset.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-int16-offset.any.worker.html": true,
"Send-binary-arraybufferview-int16-offset.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-int16-offset.any.worker.html?wss": true,
"Send-binary-arraybufferview-int32.any.html": true,
"Send-binary-arraybufferview-int32.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-int32.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-int32.any.worker.html": true,
"Send-binary-arraybufferview-int32.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-int32.any.worker.html?wss": true,
"Send-binary-arraybufferview-int8.any.html": true,
"Send-binary-arraybufferview-int8.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-int8.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-int8.any.worker.html": true,
"Send-binary-arraybufferview-int8.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-int8.any.worker.html?wss": true,
"Send-binary-arraybufferview-uint16-offset-length.any.html": true,
"Send-binary-arraybufferview-uint16-offset-length.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint16-offset-length.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-uint16-offset-length.any.worker.html": true,
"Send-binary-arraybufferview-uint16-offset-length.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint16-offset-length.any.worker.html?wss": true,
"Send-binary-arraybufferview-uint32-offset.any.html": true,
"Send-binary-arraybufferview-uint32-offset.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint32-offset.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-uint32-offset.any.worker.html": true,
"Send-binary-arraybufferview-uint32-offset.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint32-offset.any.worker.html?wss": true,
"Send-binary-arraybufferview-uint8-offset-length.any.html": true,
"Send-binary-arraybufferview-uint8-offset-length.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint8-offset-length.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-uint8-offset-length.any.worker.html": true,
"Send-binary-arraybufferview-uint8-offset-length.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint8-offset-length.any.worker.html?wss": true,
"Send-binary-arraybufferview-uint8-offset.any.html": true,
"Send-binary-arraybufferview-uint8-offset.any.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint8-offset.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-arraybufferview-uint8-offset.any.worker.html": true,
"Send-binary-arraybufferview-uint8-offset.any.worker.html?wpt_flags=h2": false,
"Send-binary-arraybufferview-uint8-offset.any.worker.html?wss": true,
"Send-binary-blob.any.html": true,
"Send-binary-blob.any.html?wpt_flags=h2": false,
"Send-binary-blob.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-binary-blob.any.worker.html": true,
"Send-binary-blob.any.worker.html?wpt_flags=h2": false,
"Send-binary-blob.any.worker.html?wss": true,
"Send-data.any.html": true,
"Send-data.any.html?wpt_flags=h2": false,
"Send-data.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-data.any.worker.html": true,
"Send-data.any.worker.html?wpt_flags=h2": false,
"Send-data.any.worker.html?wss": true,
"Send-null.any.html": true,
"Send-null.any.html?wpt_flags=h2": false,
"Send-null.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-null.any.worker.html": true,
"Send-null.any.worker.html?wpt_flags=h2": false,
"Send-null.any.worker.html?wss": true,
"Send-paired-surrogates.any.html": true,
"Send-paired-surrogates.any.html?wpt_flags=h2": false,
"Send-paired-surrogates.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-paired-surrogates.any.worker.html": true,
"Send-paired-surrogates.any.worker.html?wpt_flags=h2": false,
"Send-paired-surrogates.any.worker.html?wss": true,
"Send-unicode-data.any.html": true,
"Send-unicode-data.any.html?wpt_flags=h2": false,
"Send-unicode-data.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-unicode-data.any.worker.html": true,
"Send-unicode-data.any.worker.html?wpt_flags=h2": false,
"Send-unicode-data.any.worker.html?wss": true,
"Send-unpaired-surrogates.any.html": true,
"Send-unpaired-surrogates.any.html?wpt_flags=h2": false,
"Send-unpaired-surrogates.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Send-unpaired-surrogates.any.worker.html": true,
"Send-unpaired-surrogates.any.worker.html?wpt_flags=h2": false,
"Send-unpaired-surrogates.any.worker.html?wss": true,
"basic-auth.any.html?wpt_flags=h2": false,
"basic-auth.any.html?wss": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"basic-auth.any.worker.html?wpt_flags=h2": false,
"basic-auth.any.worker.html?wss": false,
"binaryType-wrong-value.any.html": true,
"binaryType-wrong-value.any.html?wpt_flags=h2": false,
"binaryType-wrong-value.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"binaryType-wrong-value.any.worker.html": true,
"binaryType-wrong-value.any.worker.html?wpt_flags=h2": false,
"binaryType-wrong-value.any.worker.html?wss": true,
"bufferedAmount-unchanged-by-sync-xhr.any.html": false,
"bufferedAmount-unchanged-by-sync-xhr.any.html?wpt_flags=h2": false,
"bufferedAmount-unchanged-by-sync-xhr.any.html?wss": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"bufferedAmount-unchanged-by-sync-xhr.any.worker.html": false,
"bufferedAmount-unchanged-by-sync-xhr.any.worker.html?wpt_flags=h2": false,
"bufferedAmount-unchanged-by-sync-xhr.any.worker.html?wss": false,
"close-invalid.any.html": true,
"close-invalid.any.html?wpt_flags=h2": true,
"close-invalid.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"close-invalid.any.worker.html": true,
"close-invalid.any.worker.html?wpt_flags=h2": true,
"close-invalid.any.worker.html?wss": true,
"constructor.any.html": true,
"constructor.any.html?wpt_flags=h2": true,
"constructor.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.worker.html": true,
"constructor.any.worker.html?wpt_flags=h2": true,
"constructor.any.worker.html?wss": true,
"eventhandlers.any.html": true,
"eventhandlers.any.html?wpt_flags=h2": true,
"eventhandlers.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"eventhandlers.any.worker.html": true,
"eventhandlers.any.worker.html?wpt_flags=h2": true,
"eventhandlers.any.worker.html?wss": true,
2021-08-09 12:49:31 -04:00
"referrer.any.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"referrer.any.worker.html": true,
"Close-delayed.any.html": true,
2021-08-09 12:49:31 -04:00
"Close-delayed.any.html?wpt_flags=h2": false,
"Close-delayed.any.html?wss": true,
"Close-delayed.any.worker.html": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"Close-delayed.any.worker.html?wpt_flags=h2": false,
"Close-delayed.any.worker.html?wss": true,
"stream": {
"tentative": {
"abort.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"abort.any.worker.html?wss": true,
2021-09-25 09:27:34 -04:00
"backpressure-receive.any.html?wpt_flags=h2": false,
"backpressure-receive.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"backpressure-receive.any.worker.html?wss": true,
2021-09-25 09:27:34 -04:00
"backpressure-send.any.html?wpt_flags=h2": false,
"backpressure-send.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"backpressure-send.any.worker.html?wpt_flags=h2": false,
"backpressure-send.any.worker.html?wss": true,
2021-09-25 09:27:34 -04:00
"close.any.html?wpt_flags=h2": false,
"close.any.html?wss": true,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"close.any.worker.html?wpt_flags=h2": false,
"close.any.worker.html?wss": true,
2021-09-25 09:27:34 -04:00
"constructor.any.html?wpt_flags=h2": false,
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
"constructor.any.html?wss": true,
"constructor.any.worker.html?wpt_flags=h2": false,
2022-04-18 15:17:19 -04:00
"constructor.any.worker.html?wss": true,
"abort.any.html?wpt_flags=h2": [
"abort after connect should do nothing"
],
"abort.any.worker.html?wpt_flags=h2": [
"abort after connect should do nothing"
],
"backpressure-receive.any.worker.html?wpt_flags=h2": false
}
chore(wpt): Enable WPT worker tests (#12222) Classic workers were implemented in denoland#11338, which also enabled the WPT tests in the `workers` directory. However, the rest of WPT worker tests were not enabled because a number of them were hanging due to web-platform-tests/wpt#29777. Now that that WPT issue is fixed, the bulk of worker tests can be enabled. There are still a few tests that hang, and so haven't been enabled. In particular: - The following tests seem to hang because a promise fails to resolve. We can detect such cases in non-worker tests because the process will exit without calling the WPT completion callback, but in worker tests the worker message ops will keep the event loop running. This will be fixed when we add timeouts to WPT tests (denoland#9460). - `/fetch/api/basic/error-after-response.any.worker.html` - `/html/webappapis/microtask-queuing/queue-microtask-exceptions.any.worker.html` - `/webmessaging/message-channels/worker-post-after-close.any.worker.html` - `/webmessaging/message-channels/worker.any.worker.html` - `/websockets/Create-on-worker-shutdown.any.worker.html` - The following tests apparently hang because a promise rejection is never handled, which will kill the process in the main thread but not in workers (denoland#12221). - `/streams/readable-streams/async-iterator.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html` - `/workers/interfaces/WorkerUtils/importScripts/report-error-setTimeout-same-origin.sub.any.worker.html`
2021-10-08 11:44:38 -04:00
},
"opening-handshake": {
"003-sets-origin.worker.html": false
2022-04-18 15:17:19 -04:00
},
"Send-data.worker.html": true,
"Send-data.worker.html?wpt_flags=h2": false,
"Send-data.worker.html?wss": true,
"idlharness.any.html": [
"WebSocket interface: constant CONNECTING on interface object",
"WebSocket interface: constant CONNECTING on interface prototype object",
"WebSocket interface: constant OPEN on interface object",
"WebSocket interface: constant OPEN on interface prototype object",
"WebSocket interface: constant CLOSING on interface object",
"WebSocket interface: constant CLOSING on interface prototype object",
"WebSocket interface: constant CLOSED on interface object",
"WebSocket interface: constant CLOSED on interface prototype object",
"WebSocket interface: attribute onopen",
"WebSocket interface: attribute onerror",
"WebSocket interface: attribute onclose",
"WebSocket interface: attribute onmessage",
"CloseEvent interface: attribute wasClean",
"CloseEvent interface: attribute code",
"CloseEvent interface: attribute reason",
"Stringification of new CloseEvent(\"close\")"
],
"idlharness.any.worker.html": [
"WebSocket interface: constant CONNECTING on interface object",
"WebSocket interface: constant CONNECTING on interface prototype object",
"WebSocket interface: constant OPEN on interface object",
"WebSocket interface: constant OPEN on interface prototype object",
"WebSocket interface: constant CLOSING on interface object",
"WebSocket interface: constant CLOSING on interface prototype object",
"WebSocket interface: constant CLOSED on interface object",
"WebSocket interface: constant CLOSED on interface prototype object",
"WebSocket interface: attribute onopen",
"WebSocket interface: attribute onerror",
"WebSocket interface: attribute onclose",
"WebSocket interface: attribute onmessage",
"CloseEvent interface: attribute wasClean",
"CloseEvent interface: attribute code",
"CloseEvent interface: attribute reason",
"Stringification of new CloseEvent(\"close\")"
],
"remove-own-iframe-during-onerror.window.html": false,
"remove-own-iframe-during-onerror.window.html?wpt_flags=h2": false,
"remove-own-iframe-during-onerror.window.html?wss": false,
"Create-on-worker-shutdown.any.worker.html": false
},
"workers": {
"Worker-base64.any.worker.html": true,
"Worker-call.worker.html": true,
"Worker-constructor-proto.any.worker.html": true,
"Worker-custom-event.any.worker.html": true,
2022-04-18 15:17:19 -04:00
"Worker-formdata.any.worker.html": false,
"Worker-location.sub.any.worker.html": false,
"Worker-replace-event-handler.any.worker.html": true,
"Worker-replace-global-constructor.any.worker.html": true,
"Worker-replace-self.any.worker.html": true,
2022-04-18 15:17:19 -04:00
"WorkerGlobalScope_requestAnimationFrame.tentative.worker.html": false,
"WorkerLocation-origin.sub.window.html": false,
"WorkerNavigator-hardware-concurrency.any.worker.html": true,
2022-04-18 15:17:19 -04:00
"WorkerNavigator.any.worker.html": false,
"constructors": {
"Worker": {
"DedicatedWorkerGlobalScope-members.worker.html": [
"existence of onoffline",
"existence of ononline"
],
"expected-self-properties.worker.html": [
"existence of XMLHttpRequest",
"existence of EventSource",
"existence of SharedWorker"
],
"unexpected-self-properties.worker.html": true
}
},
"dedicated-worker-from-blob-url.window.html": {
"ignore": true
},
"dedicated-worker-in-data-url-context.window.html": [
"Create a dedicated worker in a data url frame",
"Create a dedicated worker in a data url dedicated worker",
"Create a data url dedicated worker in a data url frame"
],
"examples": {
"general.any.worker.html": true,
"general.worker.html": true
},
"importscripts_mime.any.worker.html": [
"importScripts() requires scripty MIME types: text/ecmascript is allowed."
],
"interfaces": {
"DedicatedWorkerGlobalScope": {
"EventTarget.worker.html": true,
"onmessage.worker.html": true,
"postMessage": {
"return-value.worker.html": true
}
},
"WorkerGlobalScope": {
"location": {
"returns-same-object.any.worker.html": true
},
"self.any.worker.html": true
},
"WorkerUtils": {
"importScripts": {
"001.worker.html": true,
"002.worker.html": true,
2021-09-25 09:27:34 -04:00
"blob-url.worker.html": [
"A revoked blob URL will fail"
],
"catch.sub.any.worker.html": [
"Cross-origin syntax error",
"Cross-origin throw"
2021-09-25 09:27:34 -04:00
],
"report-error-cross-origin.sub.any.worker.html": false,
"report-error-redirect-to-cross-origin.sub.any.worker.html": false,
2022-04-18 15:17:19 -04:00
"report-error-same-origin.sub.any.worker.html": false,
"report-error-setTimeout-cross-origin.sub.any.worker.html": [
"WorkerGlobalScope error event: error",
"WorkerGlobalScope error event: filename",
"WorkerGlobalScope error event: lineno"
],
"report-error-setTimeout-redirect-to-cross-origin.sub.any.worker.html": [
"WorkerGlobalScope error event: filename",
"WorkerGlobalScope error event: lineno"
],
"report-error-setTimeout-same-origin.sub.any.worker.html": [
"WorkerGlobalScope error event: filename",
"WorkerGlobalScope error event: lineno"
]
}
}
},
"modules": {
"dedicated-worker-import-blob-url.any.html": true,
"dedicated-worker-import-blob-url.any.worker.html": true,
"dedicated-worker-import-data-url.any.html": true,
"dedicated-worker-import-data-url.any.worker.html": true,
"dedicated-worker-import.any.html": true,
"dedicated-worker-import.any.worker.html": true,
"shared-worker-import-blob-url.window.html": false,
"shared-worker-import-data-url.window.html": false,
"shared-worker-import.window.html": false
},
"nested_worker.worker.html": true,
"nested_worker_close_self.worker.html": true,
"nested_worker_importScripts.worker.html": true,
2022-04-18 15:17:19 -04:00
"nested_worker_sync_xhr.worker.html": false,
"semantics": {
"encodings": {
"004.worker.html": true
},
"interface-objects": {
"001.worker.html": [
"The SharedWorker interface object should be exposed.",
"The ImageData interface object should be exposed.",
"The ImageBitmap interface object should be exposed.",
"The CanvasGradient interface object should be exposed.",
"The CanvasPattern interface object should be exposed.",
"The CanvasPath interface object should be exposed.",
"The TextMetrics interface object should be exposed.",
"The Path2D interface object should be exposed.",
"The EventSource interface object should be exposed.",
"The XMLHttpRequestEventTarget interface object should be exposed.",
"The XMLHttpRequestUpload interface object should be exposed.",
"The XMLHttpRequest interface object should be exposed.",
"The FileList interface object should be exposed.",
"The FileReaderSync interface object should be exposed.",
"The IDBRequest interface object should be exposed.",
"The IDBOpenDBRequest interface object should be exposed.",
"The IDBVersionChangeEvent interface object should be exposed.",
"The IDBFactory interface object should be exposed.",
"The IDBDatabase interface object should be exposed.",
"The IDBObjectStore interface object should be exposed.",
"The IDBIndex interface object should be exposed.",
"The IDBKeyRange interface object should be exposed.",
"The IDBCursor interface object should be exposed.",
"The IDBCursorWithValue interface object should be exposed.",
"The IDBTransaction interface object should be exposed."
],
"002.worker.html": true
},
"multiple-workers": {
"exposure.any.html": [
"SharedWorker exposure"
],
"exposure.any.worker.html": true
}
},
2022-04-18 15:17:19 -04:00
"shared-worker-from-blob-url.window.html": false,
"shared-worker-in-data-url-context.window.html": false,
"worker-performance.worker.html": [
"Resource timing seems to work in workers",
"performance.clearResourceTimings in workers",
"performance.setResourceTimingBufferSize in workers"
],
"importscripts_mime_local.any.worker.html": [
"importScripts() requires scripty MIME types for data: URLs: text/ecmascript is allowed.",
"importScripts() requires scripty MIME types for blob: URLs: text/ecmascript is allowed."
]
},
"urlpattern": {
2021-09-25 09:27:34 -04:00
"urlpattern-compare.any.html": [
"Component: pathname Left: {\"pathname\":\"/foo/a\"} Right: {\"pathname\":\"/foo/b\"}",
"Component: pathname Left: {\"pathname\":\"/foo/b\"} Right: {\"pathname\":\"/foo/bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/bar\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:bar\"} Right: {\"pathname\":\"/foo/*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/(bar)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/{bar}+\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}+\"} Right: {\"pathname\":\"/foo/{bar}?\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}?\"} Right: {\"pathname\":\"/foo/{bar}*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/(123)\"} Right: {\"pathname\":\"/foo/(12)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:b\"} Right: {\"pathname\":\"/foo/:a\"}",
"Component: pathname Left: {\"pathname\":\"*/foo\"} Right: {\"pathname\":\"*\"}",
"Component: port Left: {\"port\":\"9\"} Right: {\"port\":\"100\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo/{:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"fo{o/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar/}?baz\"}",
"Component: pathname Left: \"https://a.example.com/b?a\" Right: \"https://b.example.com/a?b\"",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}/baz\"} Right: {\"pathname\":\"/foo/bar/baz\"}",
"Component: protocol Left: {\"protocol\":\"a\"} Right: {\"protocol\":\"b\"}",
"Component: username Left: {\"username\":\"a\"} Right: {\"username\":\"b\"}",
"Component: password Left: {\"password\":\"a\"} Right: {\"password\":\"b\"}",
"Component: hostname Left: {\"hostname\":\"a\"} Right: {\"hostname\":\"b\"}",
"Component: search Left: {\"search\":\"a\"} Right: {\"search\":\"b\"}",
"Component: hash Left: {\"hash\":\"a\"} Right: {\"hash\":\"b\"}"
],
"urlpattern-compare.any.worker.html": [
"Component: pathname Left: {\"pathname\":\"/foo/a\"} Right: {\"pathname\":\"/foo/b\"}",
"Component: pathname Left: {\"pathname\":\"/foo/b\"} Right: {\"pathname\":\"/foo/bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/bar\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:bar\"} Right: {\"pathname\":\"/foo/*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/(bar)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/{bar}+\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}+\"} Right: {\"pathname\":\"/foo/{bar}?\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}?\"} Right: {\"pathname\":\"/foo/{bar}*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/(123)\"} Right: {\"pathname\":\"/foo/(12)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:b\"} Right: {\"pathname\":\"/foo/:a\"}",
"Component: pathname Left: {\"pathname\":\"*/foo\"} Right: {\"pathname\":\"*\"}",
"Component: port Left: {\"port\":\"9\"} Right: {\"port\":\"100\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo/{:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"fo{o/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar/}?baz\"}",
"Component: pathname Left: \"https://a.example.com/b?a\" Right: \"https://b.example.com/a?b\"",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}/baz\"} Right: {\"pathname\":\"/foo/bar/baz\"}",
"Component: protocol Left: {\"protocol\":\"a\"} Right: {\"protocol\":\"b\"}",
"Component: username Left: {\"username\":\"a\"} Right: {\"username\":\"b\"}",
"Component: password Left: {\"password\":\"a\"} Right: {\"password\":\"b\"}",
"Component: hostname Left: {\"hostname\":\"a\"} Right: {\"hostname\":\"b\"}",
"Component: search Left: {\"search\":\"a\"} Right: {\"search\":\"b\"}",
"Component: hash Left: {\"hash\":\"a\"} Right: {\"hash\":\"b\"}"
],
"urlpattern-compare.https.any.html": [
"Component: pathname Left: {\"pathname\":\"/foo/a\"} Right: {\"pathname\":\"/foo/b\"}",
"Component: pathname Left: {\"pathname\":\"/foo/b\"} Right: {\"pathname\":\"/foo/bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/bar\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:bar\"} Right: {\"pathname\":\"/foo/*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/(bar)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/{bar}+\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}+\"} Right: {\"pathname\":\"/foo/{bar}?\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}?\"} Right: {\"pathname\":\"/foo/{bar}*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/(123)\"} Right: {\"pathname\":\"/foo/(12)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:b\"} Right: {\"pathname\":\"/foo/:a\"}",
"Component: pathname Left: {\"pathname\":\"*/foo\"} Right: {\"pathname\":\"*\"}",
"Component: port Left: {\"port\":\"9\"} Right: {\"port\":\"100\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo/{:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"fo{o/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar/}?baz\"}",
"Component: pathname Left: \"https://a.example.com/b?a\" Right: \"https://b.example.com/a?b\"",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}/baz\"} Right: {\"pathname\":\"/foo/bar/baz\"}",
"Component: protocol Left: {\"protocol\":\"a\"} Right: {\"protocol\":\"b\"}",
"Component: username Left: {\"username\":\"a\"} Right: {\"username\":\"b\"}",
"Component: password Left: {\"password\":\"a\"} Right: {\"password\":\"b\"}",
"Component: hostname Left: {\"hostname\":\"a\"} Right: {\"hostname\":\"b\"}",
"Component: search Left: {\"search\":\"a\"} Right: {\"search\":\"b\"}",
"Component: hash Left: {\"hash\":\"a\"} Right: {\"hash\":\"b\"}"
],
"urlpattern-compare.https.any.worker.html": [
"Component: pathname Left: {\"pathname\":\"/foo/a\"} Right: {\"pathname\":\"/foo/b\"}",
"Component: pathname Left: {\"pathname\":\"/foo/b\"} Right: {\"pathname\":\"/foo/bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/bar\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/\"} Right: {\"pathname\":\"/foo/:bar\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:bar\"} Right: {\"pathname\":\"/foo/*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/(bar)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}\"} Right: {\"pathname\":\"/foo/{bar}+\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}+\"} Right: {\"pathname\":\"/foo/{bar}?\"}",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}?\"} Right: {\"pathname\":\"/foo/{bar}*\"}",
"Component: pathname Left: {\"pathname\":\"/foo/(123)\"} Right: {\"pathname\":\"/foo/(12)\"}",
"Component: pathname Left: {\"pathname\":\"/foo/:b\"} Right: {\"pathname\":\"/foo/:a\"}",
"Component: pathname Left: {\"pathname\":\"*/foo\"} Right: {\"pathname\":\"*\"}",
"Component: port Left: {\"port\":\"9\"} Right: {\"port\":\"100\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo/{:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"fo{o/:bar}?/baz\"}",
"Component: pathname Left: {\"pathname\":\"foo/:bar?/baz\"} Right: {\"pathname\":\"foo{/:bar/}?baz\"}",
"Component: pathname Left: \"https://a.example.com/b?a\" Right: \"https://b.example.com/a?b\"",
"Component: pathname Left: {\"pathname\":\"/foo/{bar}/baz\"} Right: {\"pathname\":\"/foo/bar/baz\"}",
"Component: protocol Left: {\"protocol\":\"a\"} Right: {\"protocol\":\"b\"}",
"Component: username Left: {\"username\":\"a\"} Right: {\"username\":\"b\"}",
"Component: password Left: {\"password\":\"a\"} Right: {\"password\":\"b\"}",
"Component: hostname Left: {\"hostname\":\"a\"} Right: {\"hostname\":\"b\"}",
"Component: search Left: {\"search\":\"a\"} Right: {\"search\":\"b\"}",
"Component: hash Left: {\"hash\":\"a\"} Right: {\"hash\":\"b\"}"
],
"urlpattern.any.html": [
2022-02-16 08:33:34 -05:00
"Pattern: [{\"pathname\":\"/foo/:bar?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/:bar*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/*?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/**\"}] Inputs: [{\"pathname\":\"/foo\"}]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"pathname\":\"/foo/bar\"}] Inputs: [\"./foo/bar\",\"https://example.com\"]",
2022-02-16 08:33:34 -05:00
"Pattern: [\"https://(sub.)?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"https://(sub(?:.))?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"data\\\\:text/javascript,let x = 100/:tens?5;\"] Inputs: [\"data:text/javascript,let x = 100/5;\"]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"hostname\":\"bad\\\\:hostname\"}] Inputs: undefined",
"Pattern: [] Inputs: [\"https://example.com/\"]",
"Pattern: [] Inputs: [{}]",
2022-01-14 11:00:02 -05:00
"Pattern: [] Inputs: []",
2022-09-22 05:07:50 -04:00
"Pattern: [{\"pathname\":\"*{}**?\"}] Inputs: [{\"pathname\":\"foobar\"}]",
"Pattern: [{\"pathname\":\"/foo/bar\"},{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO/BAR\"}]",
"Pattern: [\"https://example.com:8080/foo?bar#baz\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [\"/foo?bar#baz\",\"https://example.com:8080\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}] Inputs: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}]",
"Pattern: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}] Inputs: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}]",
"Pattern: [\"#foo\",\"https://example.com/?q=*&v=?&hmm={}&umm=()\"] Inputs: [\"https://example.com/?q=*&v=?&hmm={}&umm=()#foo\"]"
],
"urlpattern.any.worker.html": [
2022-02-16 08:33:34 -05:00
"Pattern: [{\"pathname\":\"/foo/:bar?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/:bar*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/*?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/**\"}] Inputs: [{\"pathname\":\"/foo\"}]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"pathname\":\"/foo/bar\"}] Inputs: [\"./foo/bar\",\"https://example.com\"]",
2022-02-16 08:33:34 -05:00
"Pattern: [\"https://(sub.)?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"https://(sub(?:.))?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"data\\\\:text/javascript,let x = 100/:tens?5;\"] Inputs: [\"data:text/javascript,let x = 100/5;\"]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"hostname\":\"bad\\\\:hostname\"}] Inputs: undefined",
"Pattern: [] Inputs: [\"https://example.com/\"]",
"Pattern: [] Inputs: [{}]",
2022-01-14 11:00:02 -05:00
"Pattern: [] Inputs: []",
2022-09-22 05:07:50 -04:00
"Pattern: [{\"pathname\":\"*{}**?\"}] Inputs: [{\"pathname\":\"foobar\"}]",
"Pattern: [{\"pathname\":\"/foo/bar\"},{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO/BAR\"}]",
"Pattern: [\"https://example.com:8080/foo?bar#baz\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [\"/foo?bar#baz\",\"https://example.com:8080\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}] Inputs: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}]",
"Pattern: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}] Inputs: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}]",
"Pattern: [\"#foo\",\"https://example.com/?q=*&v=?&hmm={}&umm=()\"] Inputs: [\"https://example.com/?q=*&v=?&hmm={}&umm=()#foo\"]"
],
"urlpattern.https.any.html": [
2022-02-16 08:33:34 -05:00
"Pattern: [{\"pathname\":\"/foo/:bar?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/:bar*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/*?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/**\"}] Inputs: [{\"pathname\":\"/foo\"}]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"pathname\":\"/foo/bar\"}] Inputs: [\"./foo/bar\",\"https://example.com\"]",
2022-02-16 08:33:34 -05:00
"Pattern: [\"https://(sub.)?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"https://(sub(?:.))?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"data\\\\:text/javascript,let x = 100/:tens?5;\"] Inputs: [\"data:text/javascript,let x = 100/5;\"]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"hostname\":\"bad\\\\:hostname\"}] Inputs: undefined",
"Pattern: [] Inputs: [\"https://example.com/\"]",
"Pattern: [] Inputs: [{}]",
2022-01-14 11:00:02 -05:00
"Pattern: [] Inputs: []",
2022-09-22 05:07:50 -04:00
"Pattern: [{\"pathname\":\"*{}**?\"}] Inputs: [{\"pathname\":\"foobar\"}]",
"Pattern: [{\"pathname\":\"/foo/bar\"},{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO/BAR\"}]",
"Pattern: [\"https://example.com:8080/foo?bar#baz\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [\"/foo?bar#baz\",\"https://example.com:8080\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}] Inputs: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}]",
"Pattern: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}] Inputs: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}]",
"Pattern: [\"#foo\",\"https://example.com/?q=*&v=?&hmm={}&umm=()\"] Inputs: [\"https://example.com/?q=*&v=?&hmm={}&umm=()#foo\"]"
],
"urlpattern.https.any.worker.html": [
2022-02-16 08:33:34 -05:00
"Pattern: [{\"pathname\":\"/foo/:bar?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/:bar*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/*?\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/(.*)*\"}] Inputs: [{\"pathname\":\"/foo\"}]",
"Pattern: [{\"pathname\":\"/foo/**\"}] Inputs: [{\"pathname\":\"/foo\"}]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"pathname\":\"/foo/bar\"}] Inputs: [\"./foo/bar\",\"https://example.com\"]",
2022-02-16 08:33:34 -05:00
"Pattern: [\"https://(sub.)?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"https://(sub(?:.))?example.com/foo\"] Inputs: [\"https://example.com/foo\"]",
"Pattern: [\"data\\\\:text/javascript,let x = 100/:tens?5;\"] Inputs: [\"data:text/javascript,let x = 100/5;\"]",
2021-09-25 09:27:34 -04:00
"Pattern: [{\"hostname\":\"bad\\\\:hostname\"}] Inputs: undefined",
"Pattern: [] Inputs: [\"https://example.com/\"]",
"Pattern: [] Inputs: [{}]",
2022-01-14 11:00:02 -05:00
"Pattern: [] Inputs: []",
2022-09-22 05:07:50 -04:00
"Pattern: [{\"pathname\":\"*{}**?\"}] Inputs: [{\"pathname\":\"foobar\"}]",
"Pattern: [{\"pathname\":\"/foo/bar\"},{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO/BAR\"}]",
"Pattern: [\"https://example.com:8080/foo?bar#baz\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [\"/foo?bar#baz\",\"https://example.com:8080\",{\"ignoreCase\":true}] Inputs: [{\"pathname\":\"/FOO\",\"search\":\"BAR\",\"hash\":\"BAZ\",\"baseURL\":\"https://example.com:8080\"}]",
"Pattern: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}] Inputs: [{\"search\":\"foo\",\"baseURL\":\"https://example.com/a/+/b\"}]",
"Pattern: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}] Inputs: [{\"hash\":\"foo\",\"baseURL\":\"https://example.com/?q=*&v=?&hmm={}&umm=()\"}]",
"Pattern: [\"#foo\",\"https://example.com/?q=*&v=?&hmm={}&umm=()\"] Inputs: [\"https://example.com/?q=*&v=?&hmm={}&umm=()#foo\"]"
]
},
"compression": {
"compression-bad-chunks.tentative.any.html": true,
"compression-bad-chunks.tentative.any.worker.html": true,
"compression-including-empty-chunk.tentative.any.html": true,
"compression-including-empty-chunk.tentative.any.worker.html": true,
"compression-multiple-chunks.tentative.any.html": true,
"compression-multiple-chunks.tentative.any.worker.html": true,
"compression-output-length.tentative.any.html": true,
"compression-output-length.tentative.any.worker.html": true,
"compression-stream.tentative.any.html": true,
"compression-stream.tentative.any.worker.html": true,
"compression-with-detach.tentative.window.html": true,
"decompression-bad-chunks.tentative.any.html": true,
"decompression-bad-chunks.tentative.any.worker.html": true,
"decompression-buffersource.tentative.any.html": true,
"decompression-buffersource.tentative.any.worker.html": true,
"decompression-constructor-error.tentative.any.html": true,
"decompression-constructor-error.tentative.any.worker.html": true,
"decompression-correct-input.tentative.any.html": true,
"decompression-correct-input.tentative.any.worker.html": true,
"decompression-corrupt-input.tentative.any.html": true,
"decompression-corrupt-input.tentative.any.worker.html": true,
"decompression-empty-input.tentative.any.html": true,
"decompression-empty-input.tentative.any.worker.html": true,
"decompression-split-chunk.tentative.any.html": true,
"decompression-split-chunk.tentative.any.worker.html": true,
"decompression-uint8array-output.tentative.any.html": true,
"decompression-uint8array-output.tentative.any.worker.html": true,
"decompression-with-detach.tentative.window.html": true,
"idlharness.https.any.html": true,
2022-04-18 15:17:19 -04:00
"idlharness.https.any.worker.html": true,
"idlharness-shadowrealm.window.html": false,
"compression-constructor-error.tentative.any.html": true,
"compression-constructor-error.tentative.any.worker.html": true
2022-09-28 08:11:12 -04:00
},
"service-workers": {
"idlharness.https.any.html": [
"ServiceWorker interface: existence and properties of interface object",
"ServiceWorker interface object length",
"ServiceWorker interface object name",
"ServiceWorker interface: existence and properties of interface prototype object",
"ServiceWorker interface: existence and properties of interface prototype object's \"constructor\" property",
"ServiceWorker interface: existence and properties of interface prototype object's @@unscopables property",
"ServiceWorker interface: attribute scriptURL",
"ServiceWorker interface: attribute state",
"ServiceWorker interface: operation postMessage(any, sequence<object>)",
"ServiceWorker interface: operation postMessage(any, optional StructuredSerializeOptions)",
"ServiceWorker interface: attribute onstatechange",
"ServiceWorker must be primary interface of registrationInstance.installing",
"Stringification of registrationInstance.installing",
"ServiceWorker interface: registrationInstance.installing must inherit property \"scriptURL\" with the proper type",
"ServiceWorker interface: registrationInstance.installing must inherit property \"state\" with the proper type",
"ServiceWorker interface: registrationInstance.installing must inherit property \"postMessage(any, sequence<object>)\" with the proper type",
"ServiceWorker interface: calling postMessage(any, sequence<object>) on registrationInstance.installing with too few arguments must throw TypeError",
"ServiceWorker interface: registrationInstance.installing must inherit property \"postMessage(any, optional StructuredSerializeOptions)\" with the proper type",
"ServiceWorker interface: calling postMessage(any, optional StructuredSerializeOptions) on registrationInstance.installing with too few arguments must throw TypeError",
"ServiceWorker interface: registrationInstance.installing must inherit property \"onstatechange\" with the proper type",
"ServiceWorkerRegistration interface: existence and properties of interface object",
"ServiceWorkerRegistration interface object length",
"ServiceWorkerRegistration interface object name",
"ServiceWorkerRegistration interface: existence and properties of interface prototype object",
"ServiceWorkerRegistration interface: existence and properties of interface prototype object's \"constructor\" property",
"ServiceWorkerRegistration interface: existence and properties of interface prototype object's @@unscopables property",
"ServiceWorkerRegistration interface: attribute installing",
"ServiceWorkerRegistration interface: attribute waiting",
"ServiceWorkerRegistration interface: attribute active",
"ServiceWorkerRegistration interface: attribute navigationPreload",
"ServiceWorkerRegistration interface: attribute scope",
"ServiceWorkerRegistration interface: attribute updateViaCache",
"ServiceWorkerRegistration interface: operation update()",
"ServiceWorkerRegistration interface: operation unregister()",
"ServiceWorkerRegistration interface: attribute onupdatefound",
"ServiceWorkerRegistration must be primary interface of registrationInstance",
"Stringification of registrationInstance",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"installing\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"waiting\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"active\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"navigationPreload\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"scope\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"updateViaCache\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"update()\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"unregister()\" with the proper type",
"ServiceWorkerRegistration interface: registrationInstance must inherit property \"onupdatefound\" with the proper type",
"ServiceWorkerContainer interface: existence and properties of interface object",
"ServiceWorkerContainer interface object length",
"ServiceWorkerContainer interface object name",
"ServiceWorkerContainer interface: existence and properties of interface prototype object",
"ServiceWorkerContainer interface: existence and properties of interface prototype object's \"constructor\" property",
"ServiceWorkerContainer interface: existence and properties of interface prototype object's @@unscopables property",
"ServiceWorkerContainer interface: attribute controller",
"ServiceWorkerContainer interface: attribute ready",
"ServiceWorkerContainer interface: operation register(USVString, optional RegistrationOptions)",
"ServiceWorkerContainer interface: operation getRegistration(optional USVString)",
"ServiceWorkerContainer interface: operation getRegistrations()",
"ServiceWorkerContainer interface: operation startMessages()",
"ServiceWorkerContainer interface: attribute oncontrollerchange",
"ServiceWorkerContainer interface: attribute onmessage",
"ServiceWorkerContainer interface: attribute onmessageerror",
"ServiceWorkerContainer must be primary interface of navigator.serviceWorker",
"Stringification of navigator.serviceWorker",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"controller\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"ready\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"register(USVString, optional RegistrationOptions)\" with the proper type",
"ServiceWorkerContainer interface: calling register(USVString, optional RegistrationOptions) on navigator.serviceWorker with too few arguments must throw TypeError",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"getRegistration(optional USVString)\" with the proper type",
"ServiceWorkerContainer interface: calling getRegistration(optional USVString) on navigator.serviceWorker with too few arguments must throw TypeError",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"getRegistrations()\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"startMessages()\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"oncontrollerchange\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"onmessage\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"onmessageerror\" with the proper type",
"NavigationPreloadManager interface: existence and properties of interface object",
"NavigationPreloadManager interface object length",
"NavigationPreloadManager interface object name",
"NavigationPreloadManager interface: existence and properties of interface prototype object",
"NavigationPreloadManager interface: existence and properties of interface prototype object's \"constructor\" property",
"NavigationPreloadManager interface: existence and properties of interface prototype object's @@unscopables property",
"NavigationPreloadManager interface: operation enable()",
"NavigationPreloadManager interface: operation disable()",
"NavigationPreloadManager interface: operation setHeaderValue(ByteString)",
"NavigationPreloadManager interface: operation getState()",
"Cache interface: operation match(RequestInfo, optional CacheQueryOptions)",
"Cache interface: operation matchAll(optional RequestInfo, optional CacheQueryOptions)",
"Cache interface: operation add(RequestInfo)",
"Cache interface: operation addAll(sequence<RequestInfo>)",
"Cache interface: operation delete(RequestInfo, optional CacheQueryOptions)",
"Cache interface: operation keys(optional RequestInfo, optional CacheQueryOptions)",
"Cache interface: self.cacheInstance must inherit property \"matchAll(optional RequestInfo, optional CacheQueryOptions)\" with the proper type",
"Cache interface: calling matchAll(optional RequestInfo, optional CacheQueryOptions) on self.cacheInstance with too few arguments must throw TypeError",
"Cache interface: self.cacheInstance must inherit property \"add(RequestInfo)\" with the proper type",
"Cache interface: calling add(RequestInfo) on self.cacheInstance with too few arguments must throw TypeError",
"Cache interface: self.cacheInstance must inherit property \"addAll(sequence<RequestInfo>)\" with the proper type",
"Cache interface: calling addAll(sequence<RequestInfo>) on self.cacheInstance with too few arguments must throw TypeError",
"Cache interface: self.cacheInstance must inherit property \"keys(optional RequestInfo, optional CacheQueryOptions)\" with the proper type",
"Cache interface: calling keys(optional RequestInfo, optional CacheQueryOptions) on self.cacheInstance with too few arguments must throw TypeError",
"CacheStorage interface: operation match(RequestInfo, optional MultiCacheQueryOptions)",
"CacheStorage interface: operation keys()",
"CacheStorage interface: caches must inherit property \"match(RequestInfo, optional MultiCacheQueryOptions)\" with the proper type",
"CacheStorage interface: calling match(RequestInfo, optional MultiCacheQueryOptions) on caches with too few arguments must throw TypeError",
"CacheStorage interface: caches must inherit property \"keys()\" with the proper type",
"Window interface: attribute caches",
"Navigator interface: attribute serviceWorker",
"idl_test setup"
],
"idlharness.https.any.worker.html": [
"ServiceWorker interface: existence and properties of interface object",
"ServiceWorker interface object length",
"ServiceWorker interface object name",
"ServiceWorker interface: existence and properties of interface prototype object",
"ServiceWorker interface: existence and properties of interface prototype object's \"constructor\" property",
"ServiceWorker interface: existence and properties of interface prototype object's @@unscopables property",
"ServiceWorker interface: attribute scriptURL",
"ServiceWorker interface: attribute state",
"ServiceWorker interface: operation postMessage(any, sequence<object>)",
"ServiceWorker interface: operation postMessage(any, optional StructuredSerializeOptions)",
"ServiceWorker interface: attribute onstatechange",
"ServiceWorkerRegistration interface: existence and properties of interface object",
"ServiceWorkerRegistration interface object length",
"ServiceWorkerRegistration interface object name",
"ServiceWorkerRegistration interface: existence and properties of interface prototype object",
"ServiceWorkerRegistration interface: existence and properties of interface prototype object's \"constructor\" property",
"ServiceWorkerRegistration interface: existence and properties of interface prototype object's @@unscopables property",
"ServiceWorkerRegistration interface: attribute installing",
"ServiceWorkerRegistration interface: attribute waiting",
"ServiceWorkerRegistration interface: attribute active",
"ServiceWorkerRegistration interface: attribute navigationPreload",
"ServiceWorkerRegistration interface: attribute scope",
"ServiceWorkerRegistration interface: attribute updateViaCache",
"ServiceWorkerRegistration interface: operation update()",
"ServiceWorkerRegistration interface: operation unregister()",
"ServiceWorkerRegistration interface: attribute onupdatefound",
"ServiceWorkerContainer interface: existence and properties of interface object",
"ServiceWorkerContainer interface object length",
"ServiceWorkerContainer interface object name",
"ServiceWorkerContainer interface: existence and properties of interface prototype object",
"ServiceWorkerContainer interface: existence and properties of interface prototype object's \"constructor\" property",
"ServiceWorkerContainer interface: existence and properties of interface prototype object's @@unscopables property",
"ServiceWorkerContainer interface: attribute controller",
"ServiceWorkerContainer interface: attribute ready",
"ServiceWorkerContainer interface: operation register(USVString, optional RegistrationOptions)",
"ServiceWorkerContainer interface: operation getRegistration(optional USVString)",
"ServiceWorkerContainer interface: operation getRegistrations()",
"ServiceWorkerContainer interface: operation startMessages()",
"ServiceWorkerContainer interface: attribute oncontrollerchange",
"ServiceWorkerContainer interface: attribute onmessage",
"ServiceWorkerContainer interface: attribute onmessageerror",
"ServiceWorkerContainer must be primary interface of navigator.serviceWorker",
"Stringification of navigator.serviceWorker",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"controller\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"ready\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"register(USVString, optional RegistrationOptions)\" with the proper type",
"ServiceWorkerContainer interface: calling register(USVString, optional RegistrationOptions) on navigator.serviceWorker with too few arguments must throw TypeError",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"getRegistration(optional USVString)\" with the proper type",
"ServiceWorkerContainer interface: calling getRegistration(optional USVString) on navigator.serviceWorker with too few arguments must throw TypeError",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"getRegistrations()\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"startMessages()\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"oncontrollerchange\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"onmessage\" with the proper type",
"ServiceWorkerContainer interface: navigator.serviceWorker must inherit property \"onmessageerror\" with the proper type",
"NavigationPreloadManager interface: existence and properties of interface object",
"NavigationPreloadManager interface object length",
"NavigationPreloadManager interface object name",
"NavigationPreloadManager interface: existence and properties of interface prototype object",
"NavigationPreloadManager interface: existence and properties of interface prototype object's \"constructor\" property",
"NavigationPreloadManager interface: existence and properties of interface prototype object's @@unscopables property",
"NavigationPreloadManager interface: operation enable()",
"NavigationPreloadManager interface: operation disable()",
"NavigationPreloadManager interface: operation setHeaderValue(ByteString)",
"NavigationPreloadManager interface: operation getState()",
"Cache interface: operation match(RequestInfo, optional CacheQueryOptions)",
"Cache interface: operation matchAll(optional RequestInfo, optional CacheQueryOptions)",
"Cache interface: operation add(RequestInfo)",
"Cache interface: operation addAll(sequence<RequestInfo>)",
"Cache interface: operation delete(RequestInfo, optional CacheQueryOptions)",
"Cache interface: operation keys(optional RequestInfo, optional CacheQueryOptions)",
"Cache interface: self.cacheInstance must inherit property \"matchAll(optional RequestInfo, optional CacheQueryOptions)\" with the proper type",
"Cache interface: calling matchAll(optional RequestInfo, optional CacheQueryOptions) on self.cacheInstance with too few arguments must throw TypeError",
"Cache interface: self.cacheInstance must inherit property \"add(RequestInfo)\" with the proper type",
"Cache interface: calling add(RequestInfo) on self.cacheInstance with too few arguments must throw TypeError",
"Cache interface: self.cacheInstance must inherit property \"addAll(sequence<RequestInfo>)\" with the proper type",
"Cache interface: calling addAll(sequence<RequestInfo>) on self.cacheInstance with too few arguments must throw TypeError",
"Cache interface: self.cacheInstance must inherit property \"keys(optional RequestInfo, optional CacheQueryOptions)\" with the proper type",
"Cache interface: calling keys(optional RequestInfo, optional CacheQueryOptions) on self.cacheInstance with too few arguments must throw TypeError",
"CacheStorage interface: operation match(RequestInfo, optional MultiCacheQueryOptions)",
"CacheStorage interface: operation keys()",
"CacheStorage interface: caches must inherit property \"match(RequestInfo, optional MultiCacheQueryOptions)\" with the proper type",
"CacheStorage interface: calling match(RequestInfo, optional MultiCacheQueryOptions) on caches with too few arguments must throw TypeError",
"CacheStorage interface: caches must inherit property \"keys()\" with the proper type",
"WorkerGlobalScope interface: attribute caches",
"WorkerNavigator interface: attribute serviceWorker"
],
"cache-storage": {
"cache-match.https.any.html": [
"Cache.match supports ignoreMethod",
"Cache.match supports ignoreVary",
"Cache.match with Request and Response objects with different URLs",
"Cache.match with a network error Response",
"cors-exposed header should be stored correctly.",
"MIME type should be set from content-header correctly.",
"Cache.match ignores vary headers on opaque response."
],
"cache-delete.https.any.html": [
"Cache.delete called with a HEAD request",
"Cache.delete supports ignoreVary",
"Cache.delete with ignoreSearch option (request with search parameters)",
"Cache.delete with ignoreSearch option (when it is specified as false)"
],
"cache-abort.https.any.html": false,
"cache-abort.https.any.worker.html": false,
"cache-add.https.any.html": false,
"cache-add.https.any.worker.html": false,
"cache-delete.https.any.worker.html": [
"Cache.delete called with a HEAD request",
"Cache.delete supports ignoreVary",
"Cache.delete with ignoreSearch option (request with search parameters)",
"Cache.delete with ignoreSearch option (when it is specified as false)"
],
"cache-keys.https.any.html": false,
"cache-keys.https.any.worker.html": false,
"cache-match.https.any.worker.html": [
"Cache.match supports ignoreMethod",
"Cache.match supports ignoreVary",
"Cache.match with Request and Response objects with different URLs",
"Cache.match with a network error Response",
"cors-exposed header should be stored correctly.",
"MIME type should be set from content-header correctly.",
"Cache.match ignores vary headers on opaque response."
],
"cache-matchAll.https.any.html": false,
"cache-matchAll.https.any.worker.html": false,
"cache-put.https.any.html": [
"Cache.put called with Request and Response from fetch()",
"Cache.put with opaque-filtered HTTP 206 response",
"Cache.put with HTTP 500 response",
"Cache.put called multiple times with request URLs that differ only by a fragment",
"Cache.put with a VARY:* opaque response should not reject"
2022-09-28 08:11:12 -04:00
],
"cache-put.https.any.worker.html": [
"Cache.put called with Request and Response from fetch()",
"Cache.put with opaque-filtered HTTP 206 response",
"Cache.put with HTTP 500 response",
"Cache.put called multiple times with request URLs that differ only by a fragment",
"Cache.put with a VARY:* opaque response should not reject"
2022-09-28 08:11:12 -04:00
],
"cache-storage-keys.https.any.html": false,
"cache-storage-keys.https.any.worker.html": false,
"cache-storage-match.https.any.html": false,
"cache-storage-match.https.any.worker.html": false,
"cache-storage.https.any.html": [
"CacheStorage.delete dooms, but does not delete immediately",
"CacheStorage.open with existing cache",
"CacheStorage names are DOMStrings not USVStrings"
],
"cache-storage.https.any.worker.html": [
"CacheStorage.delete dooms, but does not delete immediately",
"CacheStorage.open with existing cache",
"CacheStorage names are DOMStrings not USVStrings"
],
"common.https.window.html": true,
"cache-storage-buckets.https.any.html": false,
"cache-storage-buckets.https.any.worker.html": false
},
"service-worker": {
"fetch-request-xhr-sync-error.https.window.html": false,
"ready.https.window.html": false,
"xhr-content-length.https.window.html": false
2022-09-28 08:11:12 -04:00
}
},
"mimesniff": {
"mime-types": {
"parsing.any.html": [
"TEXT/HTML;CHARSET=GBK (Blob/File)",
"text/html;charset=gbk( (Blob/File)",
"text/html;x=(;charset=gbk (Blob/File)",
"text/html;charset=gbk;charset=windows-1255 (Blob/File)",
"text/html;charset=();charset=GBK (Blob/File)",
"text/html;charset =gbk (Blob/File)",
"text/html ;charset=gbk (Blob/File)",
"text/html; charset=gbk (Blob/File)",
"text/html;charset= gbk (Blob/File)",
"text/html;charset= \"gbk\" (Blob/File)",
"text/html;charset=\u000bgbk (Blob/File)",
"text/html;charset=\fgbk (Blob/File)",
"text/html;\u000bcharset=gbk (Blob/File)",
"text/html;\fcharset=gbk (Blob/File)",
"text/html;charset=';charset=GBK (Blob/File)",
"text/html;test;charset=gbk (Blob/File)",
"text/html;test=;charset=gbk (Blob/File)",
"text/html;';charset=gbk (Blob/File)",
"text/html;\";charset=gbk (Blob/File)",
"text/html ; ; charset=gbk (Blob/File)",
"text/html;;;;charset=gbk (Blob/File)",
"text/html;charset= \";charset=GBK (Blob/File)",
"text/html;charset=\";charset=foo\";charset=GBK (Blob/File)",
"text/html;charset=\"gbk\" (Blob/File)",
"text/html;charset=\"gbk (Blob/File)",
"text/html;charset=gbk\" (Blob/File)",
"text/html;charset=\"\\ gbk\" (Blob/File)",
"text/html;charset=\"\\g\\b\\k\" (Blob/File)",
"text/html;charset=\"gbk\"x (Blob/File)",
"text/html;charset=\"\";charset=GBK (Blob/File)",
"text/html;charset=\";charset=GBK (Blob/File)",
"text/html;charset={gbk} (Blob/File)",
"text/html;a]=bar;b[=bar;c=bar (Blob/File)",
"text/html;in]valid=\";asd=foo\";foo=bar (Blob/File)",
"!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz/!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz;!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz=!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz (Blob/File)",
"x/x;x=\"\t !\\\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\\\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ\" (Blob/File)",
"x/x;test (Blob/File)",
"x/x;test=\"\\ (Blob/File)",
"x/x;x= (Blob/File)",
"x/x;x=\t (Blob/File)",
"x/x\n\r\t ;x=x (Blob/File)",
"\n\r\t x/x;x=x\n\r\t (Blob/File)",
"x/x;\n\r\t x=x\n\r\t ;x=y (Blob/File)",
"text/html;test=ÿ;charset=gbk (Blob/File)",
"x/x;test=<3D>;x=x (Blob/File)",
"/ (Blob/File)",
"bogus (Blob/File)",
"bogus/ (Blob/File)",
"bogus/ (Blob/File)",
"bogus/bogus/; (Blob/File)",
"</> (Blob/File)",
"(/) (Blob/File)",
"text/html(;doesnot=matter (Blob/File)",
"{/} (Blob/File)",
"text /html (Blob/File)",
"text/ html (Blob/File)",
"\"text/html\" (Blob/File)",
"x/x;\u0000=x;bonus=x (Blob/File)",
"x/x;x=\u0000;bonus=x (Blob/File)",
"x/x;x=\"\u0000\";bonus=x (Blob/File)",
"x/x;\u0001=x;bonus=x (Blob/File)",
"x/x;x=\u0001;bonus=x (Blob/File)",
"x/x;x=\"\u0001\";bonus=x (Blob/File)",
"x/x;\u0002=x;bonus=x (Blob/File)",
"x/x;x=\u0002;bonus=x (Blob/File)",
"x/x;x=\"\u0002\";bonus=x (Blob/File)",
"x/x;\u0003=x;bonus=x (Blob/File)",
"x/x;x=\u0003;bonus=x (Blob/File)",
"x/x;x=\"\u0003\";bonus=x (Blob/File)",
"x/x;\u0004=x;bonus=x (Blob/File)",
"x/x;x=\u0004;bonus=x (Blob/File)",
"x/x;x=\"\u0004\";bonus=x (Blob/File)",
"x/x;\u0005=x;bonus=x (Blob/File)",
"x/x;x=\u0005;bonus=x (Blob/File)",
"x/x;x=\"\u0005\";bonus=x (Blob/File)",
"x/x;\u0006=x;bonus=x (Blob/File)",
"x/x;x=\u0006;bonus=x (Blob/File)",
"x/x;x=\"\u0006\";bonus=x (Blob/File)",
"x/x;\u0007=x;bonus=x (Blob/File)",
"x/x;x=\u0007;bonus=x (Blob/File)",
"x/x;x=\"\u0007\";bonus=x (Blob/File)",
"x/x;\b=x;bonus=x (Blob/File)",
"x/x;x=\b;bonus=x (Blob/File)",
"x/x;x=\"\b\";bonus=x (Blob/File)",
"x/x;\t=x;bonus=x (Blob/File)",
"x/x;\n=x;bonus=x (Blob/File)",
"x/x;x=\n;bonus=x (Blob/File)",
"x/x;x=\"\n\";bonus=x (Blob/File)",
"x/x;\u000b=x;bonus=x (Blob/File)",
"x/x;x=\u000b;bonus=x (Blob/File)",
"x/x;x=\"\u000b\";bonus=x (Blob/File)",
"x/x;\f=x;bonus=x (Blob/File)",
"x/x;x=\f;bonus=x (Blob/File)",
"x/x;x=\"\f\";bonus=x (Blob/File)",
"x/x;\r=x;bonus=x (Blob/File)",
"x/x;x=\r;bonus=x (Blob/File)",
"x/x;x=\"\r\";bonus=x (Blob/File)",
"x/x;\u000e=x;bonus=x (Blob/File)",
"x/x;x=\u000e;bonus=x (Blob/File)",
"x/x;x=\"\u000e\";bonus=x (Blob/File)",
"x/x;\u000f=x;bonus=x (Blob/File)",
"x/x;x=\u000f;bonus=x (Blob/File)",
"x/x;x=\"\u000f\";bonus=x (Blob/File)",
"x/x;\u0010=x;bonus=x (Blob/File)",
"x/x;x=\u0010;bonus=x (Blob/File)",
"x/x;x=\"\u0010\";bonus=x (Blob/File)",
"x/x;\u0011=x;bonus=x (Blob/File)",
"x/x;x=\u0011;bonus=x (Blob/File)",
"x/x;x=\"\u0011\";bonus=x (Blob/File)",
"x/x;\u0012=x;bonus=x (Blob/File)",
"x/x;x=\u0012;bonus=x (Blob/File)",
"x/x;x=\"\u0012\";bonus=x (Blob/File)",
"x/x;\u0013=x;bonus=x (Blob/File)",
"x/x;x=\u0013;bonus=x (Blob/File)",
"x/x;x=\"\u0013\";bonus=x (Blob/File)",
"x/x;\u0014=x;bonus=x (Blob/File)",
"x/x;x=\u0014;bonus=x (Blob/File)",
"x/x;x=\"\u0014\";bonus=x (Blob/File)",
"x/x;\u0015=x;bonus=x (Blob/File)",
"x/x;x=\u0015;bonus=x (Blob/File)",
"x/x;x=\"\u0015\";bonus=x (Blob/File)",
"x/x;\u0016=x;bonus=x (Blob/File)",
"x/x;x=\u0016;bonus=x (Blob/File)",
"x/x;x=\"\u0016\";bonus=x (Blob/File)",
"x/x;\u0017=x;bonus=x (Blob/File)",
"x/x;x=\u0017;bonus=x (Blob/File)",
"x/x;x=\"\u0017\";bonus=x (Blob/File)",
"x/x;\u0018=x;bonus=x (Blob/File)",
"x/x;x=\u0018;bonus=x (Blob/File)",
"x/x;x=\"\u0018\";bonus=x (Blob/File)",
"x/x;\u0019=x;bonus=x (Blob/File)",
"x/x;x=\u0019;bonus=x (Blob/File)",
"x/x;x=\"\u0019\";bonus=x (Blob/File)",
"x/x;\u001a=x;bonus=x (Blob/File)",
"x/x;x=\u001a;bonus=x (Blob/File)",
"x/x;x=\"\u001a\";bonus=x (Blob/File)",
"x/x;\u001b=x;bonus=x (Blob/File)",
"x/x;x=\u001b;bonus=x (Blob/File)",
"x/x;x=\"\u001b\";bonus=x (Blob/File)",
"x/x;\u001c=x;bonus=x (Blob/File)",
"x/x;x=\u001c;bonus=x (Blob/File)",
"x/x;x=\"\u001c\";bonus=x (Blob/File)",
"x/x;\u001d=x;bonus=x (Blob/File)",
"x/x;x=\u001d;bonus=x (Blob/File)",
"x/x;x=\"\u001d\";bonus=x (Blob/File)",
"x/x;\u001e=x;bonus=x (Blob/File)",
"x/x;x=\u001e;bonus=x (Blob/File)",
"x/x;x=\"\u001e\";bonus=x (Blob/File)",
"x/x;\u001f=x;bonus=x (Blob/File)",
"x/x;x=\u001f;bonus=x (Blob/File)",
"x/x;x=\"\u001f\";bonus=x (Blob/File)",
" /x (Blob/File)",
"x/ (Blob/File)",
"x/x; =x;bonus=x (Blob/File)",
"\"/x (Blob/File)",
"x/\" (Blob/File)",
"x/x;\"=x;bonus=x (Blob/File)",
"(/x (Blob/File)",
"x/( (Blob/File)",
"x/x;(=x;bonus=x (Blob/File)",
"x/x;x=(;bonus=x (Blob/File)",
")/x (Blob/File)",
"x/) (Blob/File)",
"x/x;)=x;bonus=x (Blob/File)",
"x/x;x=);bonus=x (Blob/File)",
",/x (Blob/File)",
"x/, (Blob/File)",
"x/x;,=x;bonus=x (Blob/File)",
"x/x;x=,;bonus=x (Blob/File)",
"x/x;/=x;bonus=x (Blob/File)",
"x/x;x=/;bonus=x (Blob/File)",
":/x (Blob/File)",
"x/: (Blob/File)",
"x/x;:=x;bonus=x (Blob/File)",
"x/x;x=:;bonus=x (Blob/File)",
";/x (Blob/File)",
"x/; (Blob/File)",
"</x (Blob/File)",
"x/< (Blob/File)",
"x/x;<=x;bonus=x (Blob/File)",
"x/x;x=<;bonus=x (Blob/File)",
"=/x (Blob/File)",
"x/= (Blob/File)",
"x/x;x==;bonus=x (Blob/File)",
">/x (Blob/File)",
"x/> (Blob/File)",
"x/x;>=x;bonus=x (Blob/File)",
"x/x;x=>;bonus=x (Blob/File)",
"?/x (Blob/File)",
"x/? (Blob/File)",
"x/x;?=x;bonus=x (Blob/File)",
"x/x;x=?;bonus=x (Blob/File)",
"@/x (Blob/File)",
"x/@ (Blob/File)",
"x/x;@=x;bonus=x (Blob/File)",
"x/x;x=@;bonus=x (Blob/File)",
"[/x (Blob/File)",
"x/[ (Blob/File)",
"x/x;[=x;bonus=x (Blob/File)",
"x/x;x=[;bonus=x (Blob/File)",
"\\/x (Blob/File)",
"x/\\ (Blob/File)",
"x/x;\\=x;bonus=x (Blob/File)",
"]/x (Blob/File)",
"x/] (Blob/File)",
"x/x;]=x;bonus=x (Blob/File)",
"x/x;x=];bonus=x (Blob/File)",
"{/x (Blob/File)",
"x/{ (Blob/File)",
"x/x;{=x;bonus=x (Blob/File)",
"x/x;x={;bonus=x (Blob/File)",
"}/x (Blob/File)",
"x/} (Blob/File)",
"x/x;}=x;bonus=x (Blob/File)",
"x/x;x=};bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;€=x;bonus=x (Blob/File)",
"x/x;x=€;bonus=x (Blob/File)",
"x/x;x=\"€\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;‚=x;bonus=x (Blob/File)",
"x/x;x=‚;bonus=x (Blob/File)",
"x/x;x=\"‚\";bonus=x (Blob/File)",
"x/x;ƒ=x;bonus=x (Blob/File)",
"x/x;x=ƒ;bonus=x (Blob/File)",
"x/x;x=\"ƒ\";bonus=x (Blob/File)",
"x/x;„=x;bonus=x (Blob/File)",
"x/x;x=„;bonus=x (Blob/File)",
"x/x;x=\"„\";bonus=x (Blob/File)",
"x/x;…=x;bonus=x (Blob/File)",
"x/x;x=…;bonus=x (Blob/File)",
"x/x;x=\"…\";bonus=x (Blob/File)",
"x/x;†=x;bonus=x (Blob/File)",
"x/x;x=†;bonus=x (Blob/File)",
"x/x;x=\"†\";bonus=x (Blob/File)",
"x/x;‡=x;bonus=x (Blob/File)",
"x/x;x=‡;bonus=x (Blob/File)",
"x/x;x=\"‡\";bonus=x (Blob/File)",
"x/x;ˆ=x;bonus=x (Blob/File)",
"x/x;x=ˆ;bonus=x (Blob/File)",
"x/x;x=\"ˆ\";bonus=x (Blob/File)",
"x/x;‰=x;bonus=x (Blob/File)",
"x/x;x=‰;bonus=x (Blob/File)",
"x/x;x=\"‰\";bonus=x (Blob/File)",
"x/x;Š=x;bonus=x (Blob/File)",
"x/x;x=Š;bonus=x (Blob/File)",
"x/x;x=\"Š\";bonus=x (Blob/File)",
"x/x;‹=x;bonus=x (Blob/File)",
"x/x;x=‹;bonus=x (Blob/File)",
"x/x;x=\"‹\";bonus=x (Blob/File)",
"x/x;Œ=x;bonus=x (Blob/File)",
"x/x;x=Œ;bonus=x (Blob/File)",
"x/x;x=\"Œ\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;Ž=x;bonus=x (Blob/File)",
"x/x;x=Ž;bonus=x (Blob/File)",
"x/x;x=\"Ž\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;‘=x;bonus=x (Blob/File)",
"x/x;x=‘;bonus=x (Blob/File)",
"x/x;x=\"‘\";bonus=x (Blob/File)",
"x/x;’=x;bonus=x (Blob/File)",
"x/x;x=’;bonus=x (Blob/File)",
"x/x;x=\"’\";bonus=x (Blob/File)",
"x/x;“=x;bonus=x (Blob/File)",
"x/x;x=“;bonus=x (Blob/File)",
"x/x;x=\"“\";bonus=x (Blob/File)",
"x/x;”=x;bonus=x (Blob/File)",
"x/x;x=”;bonus=x (Blob/File)",
"x/x;x=\"”\";bonus=x (Blob/File)",
"x/x;•=x;bonus=x (Blob/File)",
"x/x;x=•;bonus=x (Blob/File)",
"x/x;x=\"•\";bonus=x (Blob/File)",
"x/x;–=x;bonus=x (Blob/File)",
"x/x;x=–;bonus=x (Blob/File)",
"x/x;x=\"–\";bonus=x (Blob/File)",
"x/x;—=x;bonus=x (Blob/File)",
"x/x;x=—;bonus=x (Blob/File)",
"x/x;x=\"—\";bonus=x (Blob/File)",
"x/x;˜=x;bonus=x (Blob/File)",
"x/x;x=˜;bonus=x (Blob/File)",
"x/x;x=\"˜\";bonus=x (Blob/File)",
"x/x;™=x;bonus=x (Blob/File)",
"x/x;x=™;bonus=x (Blob/File)",
"x/x;x=\"™\";bonus=x (Blob/File)",
"x/x;š=x;bonus=x (Blob/File)",
"x/x;x=š;bonus=x (Blob/File)",
"x/x;x=\"š\";bonus=x (Blob/File)",
"x/x;›=x;bonus=x (Blob/File)",
"x/x;x=›;bonus=x (Blob/File)",
"x/x;x=\"›\";bonus=x (Blob/File)",
"x/x;œ=x;bonus=x (Blob/File)",
"x/x;x=œ;bonus=x (Blob/File)",
"x/x;x=\"œ\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;ž=x;bonus=x (Blob/File)",
"x/x;x=ž;bonus=x (Blob/File)",
"x/x;x=\"ž\";bonus=x (Blob/File)",
"x/x;Ÿ=x;bonus=x (Blob/File)",
"x/x;x=Ÿ;bonus=x (Blob/File)",
"x/x;x=\"Ÿ\";bonus=x (Blob/File)",
"x/x; =x;bonus=x (Blob/File)",
"x/x;x= ;bonus=x (Blob/File)",
"x/x;x=\" \";bonus=x (Blob/File)",
"x/x;¡=x;bonus=x (Blob/File)",
"x/x;x=¡;bonus=x (Blob/File)",
"x/x;x=\"¡\";bonus=x (Blob/File)",
"x/x;¢=x;bonus=x (Blob/File)",
"x/x;x=¢;bonus=x (Blob/File)",
"x/x;x=\"¢\";bonus=x (Blob/File)",
"x/x;£=x;bonus=x (Blob/File)",
"x/x;x=£;bonus=x (Blob/File)",
"x/x;x=\"£\";bonus=x (Blob/File)",
"x/x;¤=x;bonus=x (Blob/File)",
"x/x;x=¤;bonus=x (Blob/File)",
"x/x;x=\"¤\";bonus=x (Blob/File)",
"x/x;¥=x;bonus=x (Blob/File)",
"x/x;x=¥;bonus=x (Blob/File)",
"x/x;x=\"¥\";bonus=x (Blob/File)",
"x/x;¦=x;bonus=x (Blob/File)",
"x/x;x=¦;bonus=x (Blob/File)",
"x/x;x=\"¦\";bonus=x (Blob/File)",
"x/x;§=x;bonus=x (Blob/File)",
"x/x;x=§;bonus=x (Blob/File)",
"x/x;x=\"§\";bonus=x (Blob/File)",
"x/x;¨=x;bonus=x (Blob/File)",
"x/x;x=¨;bonus=x (Blob/File)",
"x/x;x=\"¨\";bonus=x (Blob/File)",
"x/x;©=x;bonus=x (Blob/File)",
"x/x;x=©;bonus=x (Blob/File)",
"x/x;x=\"©\";bonus=x (Blob/File)",
"x/x;ª=x;bonus=x (Blob/File)",
"x/x;x=ª;bonus=x (Blob/File)",
"x/x;x=\"ª\";bonus=x (Blob/File)",
"x/x;«=x;bonus=x (Blob/File)",
"x/x;x=«;bonus=x (Blob/File)",
"x/x;x=\"«\";bonus=x (Blob/File)",
"x/x;¬=x;bonus=x (Blob/File)",
"x/x;x=¬;bonus=x (Blob/File)",
"x/x;x=\"¬\";bonus=x (Blob/File)",
"x/x;­=x;bonus=x (Blob/File)",
"x/x;x=­;bonus=x (Blob/File)",
"x/x;x=\"­\";bonus=x (Blob/File)",
"x/x;®=x;bonus=x (Blob/File)",
"x/x;x=®;bonus=x (Blob/File)",
"x/x;x=\"®\";bonus=x (Blob/File)",
"x/x;¯=x;bonus=x (Blob/File)",
"x/x;x=¯;bonus=x (Blob/File)",
"x/x;x=\"¯\";bonus=x (Blob/File)",
"x/x;°=x;bonus=x (Blob/File)",
"x/x;x=°;bonus=x (Blob/File)",
"x/x;x=\"°\";bonus=x (Blob/File)",
"x/x;±=x;bonus=x (Blob/File)",
"x/x;x=±;bonus=x (Blob/File)",
"x/x;x=\"±\";bonus=x (Blob/File)",
"x/x;²=x;bonus=x (Blob/File)",
"x/x;x=²;bonus=x (Blob/File)",
"x/x;x=\"²\";bonus=x (Blob/File)",
"x/x;³=x;bonus=x (Blob/File)",
"x/x;x=³;bonus=x (Blob/File)",
"x/x;x=\"³\";bonus=x (Blob/File)",
"x/x;´=x;bonus=x (Blob/File)",
"x/x;x=´;bonus=x (Blob/File)",
"x/x;x=\"´\";bonus=x (Blob/File)",
"x/x;µ=x;bonus=x (Blob/File)",
"x/x;x=µ;bonus=x (Blob/File)",
"x/x;x=\"µ\";bonus=x (Blob/File)",
"x/x;¶=x;bonus=x (Blob/File)",
"x/x;x=¶;bonus=x (Blob/File)",
"x/x;x=\"¶\";bonus=x (Blob/File)",
"x/x;·=x;bonus=x (Blob/File)",
"x/x;x=·;bonus=x (Blob/File)",
"x/x;x=\"·\";bonus=x (Blob/File)",
"x/x;¸=x;bonus=x (Blob/File)",
"x/x;x=¸;bonus=x (Blob/File)",
"x/x;x=\"¸\";bonus=x (Blob/File)",
"x/x;¹=x;bonus=x (Blob/File)",
"x/x;x=¹;bonus=x (Blob/File)",
"x/x;x=\"¹\";bonus=x (Blob/File)",
"x/x;º=x;bonus=x (Blob/File)",
"x/x;x=º;bonus=x (Blob/File)",
"x/x;x=\"º\";bonus=x (Blob/File)",
"x/x;»=x;bonus=x (Blob/File)",
"x/x;x=»;bonus=x (Blob/File)",
"x/x;x=\"»\";bonus=x (Blob/File)",
"x/x;¼=x;bonus=x (Blob/File)",
"x/x;x=¼;bonus=x (Blob/File)",
"x/x;x=\"¼\";bonus=x (Blob/File)",
"x/x;½=x;bonus=x (Blob/File)",
"x/x;x=½;bonus=x (Blob/File)",
"x/x;x=\"½\";bonus=x (Blob/File)",
"x/x;¾=x;bonus=x (Blob/File)",
"x/x;x=¾;bonus=x (Blob/File)",
"x/x;x=\"¾\";bonus=x (Blob/File)",
"x/x;¿=x;bonus=x (Blob/File)",
"x/x;x=¿;bonus=x (Blob/File)",
"x/x;x=\"¿\";bonus=x (Blob/File)",
"x/x;À=x;bonus=x (Blob/File)",
"x/x;x=À;bonus=x (Blob/File)",
"x/x;x=\"À\";bonus=x (Blob/File)",
"x/x;Á=x;bonus=x (Blob/File)",
"x/x;x=Á;bonus=x (Blob/File)",
"x/x;x=\"Á\";bonus=x (Blob/File)",
"x/x;Â=x;bonus=x (Blob/File)",
"x/x;x=Â;bonus=x (Blob/File)",
"x/x;x=\"Â\";bonus=x (Blob/File)",
"x/x;Ã=x;bonus=x (Blob/File)",
"x/x;x=Ã;bonus=x (Blob/File)",
"x/x;x=\"Ã\";bonus=x (Blob/File)",
"x/x;Ä=x;bonus=x (Blob/File)",
"x/x;x=Ä;bonus=x (Blob/File)",
"x/x;x=\"Ä\";bonus=x (Blob/File)",
"x/x;Å=x;bonus=x (Blob/File)",
"x/x;x=Å;bonus=x (Blob/File)",
"x/x;x=\"Å\";bonus=x (Blob/File)",
"x/x;Æ=x;bonus=x (Blob/File)",
"x/x;x=Æ;bonus=x (Blob/File)",
"x/x;x=\"Æ\";bonus=x (Blob/File)",
"x/x;Ç=x;bonus=x (Blob/File)",
"x/x;x=Ç;bonus=x (Blob/File)",
"x/x;x=\"Ç\";bonus=x (Blob/File)",
"x/x;È=x;bonus=x (Blob/File)",
"x/x;x=È;bonus=x (Blob/File)",
"x/x;x=\"È\";bonus=x (Blob/File)",
"x/x;É=x;bonus=x (Blob/File)",
"x/x;x=É;bonus=x (Blob/File)",
"x/x;x=\"É\";bonus=x (Blob/File)",
"x/x;Ê=x;bonus=x (Blob/File)",
"x/x;x=Ê;bonus=x (Blob/File)",
"x/x;x=\"Ê\";bonus=x (Blob/File)",
"x/x;Ë=x;bonus=x (Blob/File)",
"x/x;x=Ë;bonus=x (Blob/File)",
"x/x;x=\"Ë\";bonus=x (Blob/File)",
"x/x;Ì=x;bonus=x (Blob/File)",
"x/x;x=Ì;bonus=x (Blob/File)",
"x/x;x=\"Ì\";bonus=x (Blob/File)",
"x/x;Í=x;bonus=x (Blob/File)",
"x/x;x=Í;bonus=x (Blob/File)",
"x/x;x=\"Í\";bonus=x (Blob/File)",
"x/x;Î=x;bonus=x (Blob/File)",
"x/x;x=Î;bonus=x (Blob/File)",
"x/x;x=\"Î\";bonus=x (Blob/File)",
"x/x;Ï=x;bonus=x (Blob/File)",
"x/x;x=Ï;bonus=x (Blob/File)",
"x/x;x=\"Ï\";bonus=x (Blob/File)",
"x/x;Ð=x;bonus=x (Blob/File)",
"x/x;x=Ð;bonus=x (Blob/File)",
"x/x;x=\"Ð\";bonus=x (Blob/File)",
"x/x;Ñ=x;bonus=x (Blob/File)",
"x/x;x=Ñ;bonus=x (Blob/File)",
"x/x;x=\"Ñ\";bonus=x (Blob/File)",
"x/x;Ò=x;bonus=x (Blob/File)",
"x/x;x=Ò;bonus=x (Blob/File)",
"x/x;x=\"Ò\";bonus=x (Blob/File)",
"x/x;Ó=x;bonus=x (Blob/File)",
"x/x;x=Ó;bonus=x (Blob/File)",
"x/x;x=\"Ó\";bonus=x (Blob/File)",
"x/x;Ô=x;bonus=x (Blob/File)",
"x/x;x=Ô;bonus=x (Blob/File)",
"x/x;x=\"Ô\";bonus=x (Blob/File)",
"x/x;Õ=x;bonus=x (Blob/File)",
"x/x;x=Õ;bonus=x (Blob/File)",
"x/x;x=\"Õ\";bonus=x (Blob/File)",
"x/x;Ö=x;bonus=x (Blob/File)",
"x/x;x=Ö;bonus=x (Blob/File)",
"x/x;x=\"Ö\";bonus=x (Blob/File)",
"x/x;×=x;bonus=x (Blob/File)",
"x/x;x=×;bonus=x (Blob/File)",
"x/x;x=\"×\";bonus=x (Blob/File)",
"x/x;Ø=x;bonus=x (Blob/File)",
"x/x;x=Ø;bonus=x (Blob/File)",
"x/x;x=\"Ø\";bonus=x (Blob/File)",
"x/x;Ù=x;bonus=x (Blob/File)",
"x/x;x=Ù;bonus=x (Blob/File)",
"x/x;x=\"Ù\";bonus=x (Blob/File)",
"x/x;Ú=x;bonus=x (Blob/File)",
"x/x;x=Ú;bonus=x (Blob/File)",
"x/x;x=\"Ú\";bonus=x (Blob/File)",
"x/x;Û=x;bonus=x (Blob/File)",
"x/x;x=Û;bonus=x (Blob/File)",
"x/x;x=\"Û\";bonus=x (Blob/File)",
"x/x;Ü=x;bonus=x (Blob/File)",
"x/x;x=Ü;bonus=x (Blob/File)",
"x/x;x=\"Ü\";bonus=x (Blob/File)",
"x/x;Ý=x;bonus=x (Blob/File)",
"x/x;x=Ý;bonus=x (Blob/File)",
"x/x;x=\"Ý\";bonus=x (Blob/File)",
"x/x;Þ=x;bonus=x (Blob/File)",
"x/x;x=Þ;bonus=x (Blob/File)",
"x/x;x=\"Þ\";bonus=x (Blob/File)",
"x/x;ß=x;bonus=x (Blob/File)",
"x/x;x=ß;bonus=x (Blob/File)",
"x/x;x=\"ß\";bonus=x (Blob/File)",
"x/x;à=x;bonus=x (Blob/File)",
"x/x;x=à;bonus=x (Blob/File)",
"x/x;x=\"à\";bonus=x (Blob/File)",
"x/x;á=x;bonus=x (Blob/File)",
"x/x;x=á;bonus=x (Blob/File)",
"x/x;x=\"á\";bonus=x (Blob/File)",
"x/x;â=x;bonus=x (Blob/File)",
"x/x;x=â;bonus=x (Blob/File)",
"x/x;x=\"â\";bonus=x (Blob/File)",
"x/x;ã=x;bonus=x (Blob/File)",
"x/x;x=ã;bonus=x (Blob/File)",
"x/x;x=\"ã\";bonus=x (Blob/File)",
"x/x;ä=x;bonus=x (Blob/File)",
"x/x;x=ä;bonus=x (Blob/File)",
"x/x;x=\"ä\";bonus=x (Blob/File)",
"x/x;å=x;bonus=x (Blob/File)",
"x/x;x=å;bonus=x (Blob/File)",
"x/x;x=\"å\";bonus=x (Blob/File)",
"x/x;æ=x;bonus=x (Blob/File)",
"x/x;x=æ;bonus=x (Blob/File)",
"x/x;x=\"æ\";bonus=x (Blob/File)",
"x/x;ç=x;bonus=x (Blob/File)",
"x/x;x=ç;bonus=x (Blob/File)",
"x/x;x=\"ç\";bonus=x (Blob/File)",
"x/x;è=x;bonus=x (Blob/File)",
"x/x;x=è;bonus=x (Blob/File)",
"x/x;x=\"è\";bonus=x (Blob/File)",
"x/x;é=x;bonus=x (Blob/File)",
"x/x;x=é;bonus=x (Blob/File)",
"x/x;x=\"é\";bonus=x (Blob/File)",
"x/x;ê=x;bonus=x (Blob/File)",
"x/x;x=ê;bonus=x (Blob/File)",
"x/x;x=\"ê\";bonus=x (Blob/File)",
"x/x;ë=x;bonus=x (Blob/File)",
"x/x;x=ë;bonus=x (Blob/File)",
"x/x;x=\"ë\";bonus=x (Blob/File)",
"x/x;ì=x;bonus=x (Blob/File)",
"x/x;x=ì;bonus=x (Blob/File)",
"x/x;x=\"ì\";bonus=x (Blob/File)",
"x/x;í=x;bonus=x (Blob/File)",
"x/x;x=í;bonus=x (Blob/File)",
"x/x;x=\"í\";bonus=x (Blob/File)",
"x/x;î=x;bonus=x (Blob/File)",
"x/x;x=î;bonus=x (Blob/File)",
"x/x;x=\"î\";bonus=x (Blob/File)",
"x/x;ï=x;bonus=x (Blob/File)",
"x/x;x=ï;bonus=x (Blob/File)",
"x/x;x=\"ï\";bonus=x (Blob/File)",
"x/x;ð=x;bonus=x (Blob/File)",
"x/x;x=ð;bonus=x (Blob/File)",
"x/x;x=\"ð\";bonus=x (Blob/File)",
"x/x;ñ=x;bonus=x (Blob/File)",
"x/x;x=ñ;bonus=x (Blob/File)",
"x/x;x=\"ñ\";bonus=x (Blob/File)",
"x/x;ò=x;bonus=x (Blob/File)",
"x/x;x=ò;bonus=x (Blob/File)",
"x/x;x=\"ò\";bonus=x (Blob/File)",
"x/x;ó=x;bonus=x (Blob/File)",
"x/x;x=ó;bonus=x (Blob/File)",
"x/x;x=\"ó\";bonus=x (Blob/File)",
"x/x;ô=x;bonus=x (Blob/File)",
"x/x;x=ô;bonus=x (Blob/File)",
"x/x;x=\"ô\";bonus=x (Blob/File)",
"x/x;õ=x;bonus=x (Blob/File)",
"x/x;x=õ;bonus=x (Blob/File)",
"x/x;x=\"õ\";bonus=x (Blob/File)",
"x/x;ö=x;bonus=x (Blob/File)",
"x/x;x=ö;bonus=x (Blob/File)",
"x/x;x=\"ö\";bonus=x (Blob/File)",
"x/x;÷=x;bonus=x (Blob/File)",
"x/x;x=÷;bonus=x (Blob/File)",
"x/x;x=\"÷\";bonus=x (Blob/File)",
"x/x;ø=x;bonus=x (Blob/File)",
"x/x;x=ø;bonus=x (Blob/File)",
"x/x;x=\"ø\";bonus=x (Blob/File)",
"x/x;ù=x;bonus=x (Blob/File)",
"x/x;x=ù;bonus=x (Blob/File)",
"x/x;x=\"ù\";bonus=x (Blob/File)",
"x/x;ú=x;bonus=x (Blob/File)",
"x/x;x=ú;bonus=x (Blob/File)",
"x/x;x=\"ú\";bonus=x (Blob/File)",
"x/x;û=x;bonus=x (Blob/File)",
"x/x;x=û;bonus=x (Blob/File)",
"x/x;x=\"û\";bonus=x (Blob/File)",
"x/x;ü=x;bonus=x (Blob/File)",
"x/x;x=ü;bonus=x (Blob/File)",
"x/x;x=\"ü\";bonus=x (Blob/File)",
"x/x;ý=x;bonus=x (Blob/File)",
"x/x;x=ý;bonus=x (Blob/File)",
"x/x;x=\"ý\";bonus=x (Blob/File)",
"x/x;þ=x;bonus=x (Blob/File)",
"x/x;x=þ;bonus=x (Blob/File)",
"x/x;x=\"þ\";bonus=x (Blob/File)",
"x/x;ÿ=x;bonus=x (Blob/File)",
"x/x;x=ÿ;bonus=x (Blob/File)",
"x/x;x=\"ÿ\";bonus=x (Blob/File)",
"TEXT/HTML;CHARSET=GBK (Request/Response)",
"text/html;charset= \";charset=GBK (Request/Response)",
"text/html;charset=\";charset=foo\";charset=GBK (Request/Response)",
"text/html;charset=\"\";charset=GBK (Request/Response)",
"text/html;charset=\";charset=GBK (Request/Response)",
"!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz/!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz;!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz=!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz (Request/Response)",
"x/x;x=\"\t !\\\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\\\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ\" (Request/Response)",
"text/html;test=ÿ;charset=gbk (Request/Response)",
"x/x;,=x;bonus=x (Request/Response)",
"x/x;x=,;bonus=x (Request/Response)",
"x/x;x=€;bonus=x (Request/Response)",
"x/x;x=\"€\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=‚;bonus=x (Request/Response)",
"x/x;x=\"‚\";bonus=x (Request/Response)",
"x/x;x=ƒ;bonus=x (Request/Response)",
"x/x;x=\"ƒ\";bonus=x (Request/Response)",
"x/x;x=„;bonus=x (Request/Response)",
"x/x;x=\"„\";bonus=x (Request/Response)",
"x/x;x=…;bonus=x (Request/Response)",
"x/x;x=\"…\";bonus=x (Request/Response)",
"x/x;x=†;bonus=x (Request/Response)",
"x/x;x=\"†\";bonus=x (Request/Response)",
"x/x;x=‡;bonus=x (Request/Response)",
"x/x;x=\"‡\";bonus=x (Request/Response)",
"x/x;x=ˆ;bonus=x (Request/Response)",
"x/x;x=\"ˆ\";bonus=x (Request/Response)",
"x/x;x=‰;bonus=x (Request/Response)",
"x/x;x=\"‰\";bonus=x (Request/Response)",
"x/x;x=Š;bonus=x (Request/Response)",
"x/x;x=\"Š\";bonus=x (Request/Response)",
"x/x;x=‹;bonus=x (Request/Response)",
"x/x;x=\"‹\";bonus=x (Request/Response)",
"x/x;x=Œ;bonus=x (Request/Response)",
"x/x;x=\"Œ\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=Ž;bonus=x (Request/Response)",
"x/x;x=\"Ž\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=‘;bonus=x (Request/Response)",
"x/x;x=\"‘\";bonus=x (Request/Response)",
"x/x;x=’;bonus=x (Request/Response)",
"x/x;x=\"’\";bonus=x (Request/Response)",
"x/x;x=“;bonus=x (Request/Response)",
"x/x;x=\"“\";bonus=x (Request/Response)",
"x/x;x=”;bonus=x (Request/Response)",
"x/x;x=\"”\";bonus=x (Request/Response)",
"x/x;x=•;bonus=x (Request/Response)",
"x/x;x=\"•\";bonus=x (Request/Response)",
"x/x;x=–;bonus=x (Request/Response)",
"x/x;x=\"–\";bonus=x (Request/Response)",
"x/x;x=—;bonus=x (Request/Response)",
"x/x;x=\"—\";bonus=x (Request/Response)",
"x/x;x=˜;bonus=x (Request/Response)",
"x/x;x=\"˜\";bonus=x (Request/Response)",
"x/x;x=™;bonus=x (Request/Response)",
"x/x;x=\"™\";bonus=x (Request/Response)",
"x/x;x=š;bonus=x (Request/Response)",
"x/x;x=\"š\";bonus=x (Request/Response)",
"x/x;x=›;bonus=x (Request/Response)",
"x/x;x=\"›\";bonus=x (Request/Response)",
"x/x;x=œ;bonus=x (Request/Response)",
"x/x;x=\"œ\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=ž;bonus=x (Request/Response)",
"x/x;x=\"ž\";bonus=x (Request/Response)",
"x/x;x=Ÿ;bonus=x (Request/Response)",
"x/x;x=\"Ÿ\";bonus=x (Request/Response)",
"x/x;x= ;bonus=x (Request/Response)",
"x/x;x=\" \";bonus=x (Request/Response)",
"x/x;x=¡;bonus=x (Request/Response)",
"x/x;x=\"¡\";bonus=x (Request/Response)",
"x/x;x=¢;bonus=x (Request/Response)",
"x/x;x=\"¢\";bonus=x (Request/Response)",
"x/x;x=£;bonus=x (Request/Response)",
"x/x;x=\"£\";bonus=x (Request/Response)",
"x/x;x=¤;bonus=x (Request/Response)",
"x/x;x=\"¤\";bonus=x (Request/Response)",
"x/x;x=¥;bonus=x (Request/Response)",
"x/x;x=\"¥\";bonus=x (Request/Response)",
"x/x;x=¦;bonus=x (Request/Response)",
"x/x;x=\"¦\";bonus=x (Request/Response)",
"x/x;x=§;bonus=x (Request/Response)",
"x/x;x=\"§\";bonus=x (Request/Response)",
"x/x;x=¨;bonus=x (Request/Response)",
"x/x;x=\"¨\";bonus=x (Request/Response)",
"x/x;x=©;bonus=x (Request/Response)",
"x/x;x=\"©\";bonus=x (Request/Response)",
"x/x;x=ª;bonus=x (Request/Response)",
"x/x;x=\"ª\";bonus=x (Request/Response)",
"x/x;x=«;bonus=x (Request/Response)",
"x/x;x=\"«\";bonus=x (Request/Response)",
"x/x;x=¬;bonus=x (Request/Response)",
"x/x;x=\"¬\";bonus=x (Request/Response)",
"x/x;x=­;bonus=x (Request/Response)",
"x/x;x=\"­\";bonus=x (Request/Response)",
"x/x;x=®;bonus=x (Request/Response)",
"x/x;x=\"®\";bonus=x (Request/Response)",
"x/x;x=¯;bonus=x (Request/Response)",
"x/x;x=\"¯\";bonus=x (Request/Response)",
"x/x;x=°;bonus=x (Request/Response)",
"x/x;x=\"°\";bonus=x (Request/Response)",
"x/x;x=±;bonus=x (Request/Response)",
"x/x;x=\"±\";bonus=x (Request/Response)",
"x/x;x=²;bonus=x (Request/Response)",
"x/x;x=\"²\";bonus=x (Request/Response)",
"x/x;x=³;bonus=x (Request/Response)",
"x/x;x=\"³\";bonus=x (Request/Response)",
"x/x;x=´;bonus=x (Request/Response)",
"x/x;x=\"´\";bonus=x (Request/Response)",
"x/x;x=µ;bonus=x (Request/Response)",
"x/x;x=\"µ\";bonus=x (Request/Response)",
"x/x;x=¶;bonus=x (Request/Response)",
"x/x;x=\"¶\";bonus=x (Request/Response)",
"x/x;x=·;bonus=x (Request/Response)",
"x/x;x=\"·\";bonus=x (Request/Response)",
"x/x;x=¸;bonus=x (Request/Response)",
"x/x;x=\"¸\";bonus=x (Request/Response)",
"x/x;x=¹;bonus=x (Request/Response)",
"x/x;x=\"¹\";bonus=x (Request/Response)",
"x/x;x=º;bonus=x (Request/Response)",
"x/x;x=\"º\";bonus=x (Request/Response)",
"x/x;x=»;bonus=x (Request/Response)",
"x/x;x=\"»\";bonus=x (Request/Response)",
"x/x;x=¼;bonus=x (Request/Response)",
"x/x;x=\"¼\";bonus=x (Request/Response)",
"x/x;x=½;bonus=x (Request/Response)",
"x/x;x=\"½\";bonus=x (Request/Response)",
"x/x;x=¾;bonus=x (Request/Response)",
"x/x;x=\"¾\";bonus=x (Request/Response)",
"x/x;x=¿;bonus=x (Request/Response)",
"x/x;x=\"¿\";bonus=x (Request/Response)",
"x/x;x=À;bonus=x (Request/Response)",
"x/x;x=\"À\";bonus=x (Request/Response)",
"x/x;x=Á;bonus=x (Request/Response)",
"x/x;x=\"Á\";bonus=x (Request/Response)",
"x/x;x=Â;bonus=x (Request/Response)",
"x/x;x=\"Â\";bonus=x (Request/Response)",
"x/x;x=Ã;bonus=x (Request/Response)",
"x/x;x=\"Ã\";bonus=x (Request/Response)",
"x/x;x=Ä;bonus=x (Request/Response)",
"x/x;x=\"Ä\";bonus=x (Request/Response)",
"x/x;x=Å;bonus=x (Request/Response)",
"x/x;x=\"Å\";bonus=x (Request/Response)",
"x/x;x=Æ;bonus=x (Request/Response)",
"x/x;x=\"Æ\";bonus=x (Request/Response)",
"x/x;x=Ç;bonus=x (Request/Response)",
"x/x;x=\"Ç\";bonus=x (Request/Response)",
"x/x;x=È;bonus=x (Request/Response)",
"x/x;x=\"È\";bonus=x (Request/Response)",
"x/x;x=É;bonus=x (Request/Response)",
"x/x;x=\"É\";bonus=x (Request/Response)",
"x/x;x=Ê;bonus=x (Request/Response)",
"x/x;x=\"Ê\";bonus=x (Request/Response)",
"x/x;x=Ë;bonus=x (Request/Response)",
"x/x;x=\"Ë\";bonus=x (Request/Response)",
"x/x;x=Ì;bonus=x (Request/Response)",
"x/x;x=\"Ì\";bonus=x (Request/Response)",
"x/x;x=Í;bonus=x (Request/Response)",
"x/x;x=\"Í\";bonus=x (Request/Response)",
"x/x;x=Î;bonus=x (Request/Response)",
"x/x;x=\"Î\";bonus=x (Request/Response)",
"x/x;x=Ï;bonus=x (Request/Response)",
"x/x;x=\"Ï\";bonus=x (Request/Response)",
"x/x;x=Ð;bonus=x (Request/Response)",
"x/x;x=\"Ð\";bonus=x (Request/Response)",
"x/x;x=Ñ;bonus=x (Request/Response)",
"x/x;x=\"Ñ\";bonus=x (Request/Response)",
"x/x;x=Ò;bonus=x (Request/Response)",
"x/x;x=\"Ò\";bonus=x (Request/Response)",
"x/x;x=Ó;bonus=x (Request/Response)",
"x/x;x=\"Ó\";bonus=x (Request/Response)",
"x/x;x=Ô;bonus=x (Request/Response)",
"x/x;x=\"Ô\";bonus=x (Request/Response)",
"x/x;x=Õ;bonus=x (Request/Response)",
"x/x;x=\"Õ\";bonus=x (Request/Response)",
"x/x;x=Ö;bonus=x (Request/Response)",
"x/x;x=\"Ö\";bonus=x (Request/Response)",
"x/x;x=×;bonus=x (Request/Response)",
"x/x;x=\"×\";bonus=x (Request/Response)",
"x/x;x=Ø;bonus=x (Request/Response)",
"x/x;x=\"Ø\";bonus=x (Request/Response)",
"x/x;x=Ù;bonus=x (Request/Response)",
"x/x;x=\"Ù\";bonus=x (Request/Response)",
"x/x;x=Ú;bonus=x (Request/Response)",
"x/x;x=\"Ú\";bonus=x (Request/Response)",
"x/x;x=Û;bonus=x (Request/Response)",
"x/x;x=\"Û\";bonus=x (Request/Response)",
"x/x;x=Ü;bonus=x (Request/Response)",
"x/x;x=\"Ü\";bonus=x (Request/Response)",
"x/x;x=Ý;bonus=x (Request/Response)",
"x/x;x=\"Ý\";bonus=x (Request/Response)",
"x/x;x=Þ;bonus=x (Request/Response)",
"x/x;x=\"Þ\";bonus=x (Request/Response)",
"x/x;x=ß;bonus=x (Request/Response)",
"x/x;x=\"ß\";bonus=x (Request/Response)",
"x/x;x=à;bonus=x (Request/Response)",
"x/x;x=\"à\";bonus=x (Request/Response)",
"x/x;x=á;bonus=x (Request/Response)",
"x/x;x=\"á\";bonus=x (Request/Response)",
"x/x;x=â;bonus=x (Request/Response)",
"x/x;x=\"â\";bonus=x (Request/Response)",
"x/x;x=ã;bonus=x (Request/Response)",
"x/x;x=\"ã\";bonus=x (Request/Response)",
"x/x;x=ä;bonus=x (Request/Response)",
"x/x;x=\"ä\";bonus=x (Request/Response)",
"x/x;x=å;bonus=x (Request/Response)",
"x/x;x=\"å\";bonus=x (Request/Response)",
"x/x;x=æ;bonus=x (Request/Response)",
"x/x;x=\"æ\";bonus=x (Request/Response)",
"x/x;x=ç;bonus=x (Request/Response)",
"x/x;x=\"ç\";bonus=x (Request/Response)",
"x/x;x=è;bonus=x (Request/Response)",
"x/x;x=\"è\";bonus=x (Request/Response)",
"x/x;x=é;bonus=x (Request/Response)",
"x/x;x=\"é\";bonus=x (Request/Response)",
"x/x;x=ê;bonus=x (Request/Response)",
"x/x;x=\"ê\";bonus=x (Request/Response)",
"x/x;x=ë;bonus=x (Request/Response)",
"x/x;x=\"ë\";bonus=x (Request/Response)",
"x/x;x=ì;bonus=x (Request/Response)",
"x/x;x=\"ì\";bonus=x (Request/Response)",
"x/x;x=í;bonus=x (Request/Response)",
"x/x;x=\"í\";bonus=x (Request/Response)",
"x/x;x=î;bonus=x (Request/Response)",
"x/x;x=\"î\";bonus=x (Request/Response)",
"x/x;x=ï;bonus=x (Request/Response)",
"x/x;x=\"ï\";bonus=x (Request/Response)",
"x/x;x=ð;bonus=x (Request/Response)",
"x/x;x=\"ð\";bonus=x (Request/Response)",
"x/x;x=ñ;bonus=x (Request/Response)",
"x/x;x=\"ñ\";bonus=x (Request/Response)",
"x/x;x=ò;bonus=x (Request/Response)",
"x/x;x=\"ò\";bonus=x (Request/Response)",
"x/x;x=ó;bonus=x (Request/Response)",
"x/x;x=\"ó\";bonus=x (Request/Response)",
"x/x;x=ô;bonus=x (Request/Response)",
"x/x;x=\"ô\";bonus=x (Request/Response)",
"x/x;x=õ;bonus=x (Request/Response)",
"x/x;x=\"õ\";bonus=x (Request/Response)",
"x/x;x=ö;bonus=x (Request/Response)",
"x/x;x=\"ö\";bonus=x (Request/Response)",
"x/x;x=÷;bonus=x (Request/Response)",
"x/x;x=\"÷\";bonus=x (Request/Response)",
"x/x;x=ø;bonus=x (Request/Response)",
"x/x;x=\"ø\";bonus=x (Request/Response)",
"x/x;x=ù;bonus=x (Request/Response)",
"x/x;x=\"ù\";bonus=x (Request/Response)",
"x/x;x=ú;bonus=x (Request/Response)",
"x/x;x=\"ú\";bonus=x (Request/Response)",
"x/x;x=û;bonus=x (Request/Response)",
"x/x;x=\"û\";bonus=x (Request/Response)",
"x/x;x=ü;bonus=x (Request/Response)",
"x/x;x=\"ü\";bonus=x (Request/Response)",
"x/x;x=ý;bonus=x (Request/Response)",
"x/x;x=\"ý\";bonus=x (Request/Response)",
"x/x;x=þ;bonus=x (Request/Response)",
"x/x;x=\"þ\";bonus=x (Request/Response)",
"x/x;x=ÿ;bonus=x (Request/Response)",
"x/x;x=\"ÿ\";bonus=x (Request/Response)"
],
"parsing.any.worker.html": [
"TEXT/HTML;CHARSET=GBK (Blob/File)",
"text/html;charset=gbk( (Blob/File)",
"text/html;x=(;charset=gbk (Blob/File)",
"text/html;charset=gbk;charset=windows-1255 (Blob/File)",
"text/html;charset=();charset=GBK (Blob/File)",
"text/html;charset =gbk (Blob/File)",
"text/html ;charset=gbk (Blob/File)",
"text/html; charset=gbk (Blob/File)",
"text/html;charset= gbk (Blob/File)",
"text/html;charset= \"gbk\" (Blob/File)",
"text/html;charset=\u000bgbk (Blob/File)",
"text/html;charset=\fgbk (Blob/File)",
"text/html;\u000bcharset=gbk (Blob/File)",
"text/html;\fcharset=gbk (Blob/File)",
"text/html;charset=';charset=GBK (Blob/File)",
"text/html;test;charset=gbk (Blob/File)",
"text/html;test=;charset=gbk (Blob/File)",
"text/html;';charset=gbk (Blob/File)",
"text/html;\";charset=gbk (Blob/File)",
"text/html ; ; charset=gbk (Blob/File)",
"text/html;;;;charset=gbk (Blob/File)",
"text/html;charset= \";charset=GBK (Blob/File)",
"text/html;charset=\";charset=foo\";charset=GBK (Blob/File)",
"text/html;charset=\"gbk\" (Blob/File)",
"text/html;charset=\"gbk (Blob/File)",
"text/html;charset=gbk\" (Blob/File)",
"text/html;charset=\"\\ gbk\" (Blob/File)",
"text/html;charset=\"\\g\\b\\k\" (Blob/File)",
"text/html;charset=\"gbk\"x (Blob/File)",
"text/html;charset=\"\";charset=GBK (Blob/File)",
"text/html;charset=\";charset=GBK (Blob/File)",
"text/html;charset={gbk} (Blob/File)",
"text/html;a]=bar;b[=bar;c=bar (Blob/File)",
"text/html;in]valid=\";asd=foo\";foo=bar (Blob/File)",
"!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz/!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz;!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz=!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz (Blob/File)",
"x/x;x=\"\t !\\\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\\\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ\" (Blob/File)",
"x/x;test (Blob/File)",
"x/x;test=\"\\ (Blob/File)",
"x/x;x= (Blob/File)",
"x/x;x=\t (Blob/File)",
"x/x\n\r\t ;x=x (Blob/File)",
"\n\r\t x/x;x=x\n\r\t (Blob/File)",
"x/x;\n\r\t x=x\n\r\t ;x=y (Blob/File)",
"text/html;test=ÿ;charset=gbk (Blob/File)",
"x/x;test=<3D>;x=x (Blob/File)",
"/ (Blob/File)",
"bogus (Blob/File)",
"bogus/ (Blob/File)",
"bogus/ (Blob/File)",
"bogus/bogus/; (Blob/File)",
"</> (Blob/File)",
"(/) (Blob/File)",
"text/html(;doesnot=matter (Blob/File)",
"{/} (Blob/File)",
"text /html (Blob/File)",
"text/ html (Blob/File)",
"\"text/html\" (Blob/File)",
"x/x;\u0000=x;bonus=x (Blob/File)",
"x/x;x=\u0000;bonus=x (Blob/File)",
"x/x;x=\"\u0000\";bonus=x (Blob/File)",
"x/x;\u0001=x;bonus=x (Blob/File)",
"x/x;x=\u0001;bonus=x (Blob/File)",
"x/x;x=\"\u0001\";bonus=x (Blob/File)",
"x/x;\u0002=x;bonus=x (Blob/File)",
"x/x;x=\u0002;bonus=x (Blob/File)",
"x/x;x=\"\u0002\";bonus=x (Blob/File)",
"x/x;\u0003=x;bonus=x (Blob/File)",
"x/x;x=\u0003;bonus=x (Blob/File)",
"x/x;x=\"\u0003\";bonus=x (Blob/File)",
"x/x;\u0004=x;bonus=x (Blob/File)",
"x/x;x=\u0004;bonus=x (Blob/File)",
"x/x;x=\"\u0004\";bonus=x (Blob/File)",
"x/x;\u0005=x;bonus=x (Blob/File)",
"x/x;x=\u0005;bonus=x (Blob/File)",
"x/x;x=\"\u0005\";bonus=x (Blob/File)",
"x/x;\u0006=x;bonus=x (Blob/File)",
"x/x;x=\u0006;bonus=x (Blob/File)",
"x/x;x=\"\u0006\";bonus=x (Blob/File)",
"x/x;\u0007=x;bonus=x (Blob/File)",
"x/x;x=\u0007;bonus=x (Blob/File)",
"x/x;x=\"\u0007\";bonus=x (Blob/File)",
"x/x;\b=x;bonus=x (Blob/File)",
"x/x;x=\b;bonus=x (Blob/File)",
"x/x;x=\"\b\";bonus=x (Blob/File)",
"x/x;\t=x;bonus=x (Blob/File)",
"x/x;\n=x;bonus=x (Blob/File)",
"x/x;x=\n;bonus=x (Blob/File)",
"x/x;x=\"\n\";bonus=x (Blob/File)",
"x/x;\u000b=x;bonus=x (Blob/File)",
"x/x;x=\u000b;bonus=x (Blob/File)",
"x/x;x=\"\u000b\";bonus=x (Blob/File)",
"x/x;\f=x;bonus=x (Blob/File)",
"x/x;x=\f;bonus=x (Blob/File)",
"x/x;x=\"\f\";bonus=x (Blob/File)",
"x/x;\r=x;bonus=x (Blob/File)",
"x/x;x=\r;bonus=x (Blob/File)",
"x/x;x=\"\r\";bonus=x (Blob/File)",
"x/x;\u000e=x;bonus=x (Blob/File)",
"x/x;x=\u000e;bonus=x (Blob/File)",
"x/x;x=\"\u000e\";bonus=x (Blob/File)",
"x/x;\u000f=x;bonus=x (Blob/File)",
"x/x;x=\u000f;bonus=x (Blob/File)",
"x/x;x=\"\u000f\";bonus=x (Blob/File)",
"x/x;\u0010=x;bonus=x (Blob/File)",
"x/x;x=\u0010;bonus=x (Blob/File)",
"x/x;x=\"\u0010\";bonus=x (Blob/File)",
"x/x;\u0011=x;bonus=x (Blob/File)",
"x/x;x=\u0011;bonus=x (Blob/File)",
"x/x;x=\"\u0011\";bonus=x (Blob/File)",
"x/x;\u0012=x;bonus=x (Blob/File)",
"x/x;x=\u0012;bonus=x (Blob/File)",
"x/x;x=\"\u0012\";bonus=x (Blob/File)",
"x/x;\u0013=x;bonus=x (Blob/File)",
"x/x;x=\u0013;bonus=x (Blob/File)",
"x/x;x=\"\u0013\";bonus=x (Blob/File)",
"x/x;\u0014=x;bonus=x (Blob/File)",
"x/x;x=\u0014;bonus=x (Blob/File)",
"x/x;x=\"\u0014\";bonus=x (Blob/File)",
"x/x;\u0015=x;bonus=x (Blob/File)",
"x/x;x=\u0015;bonus=x (Blob/File)",
"x/x;x=\"\u0015\";bonus=x (Blob/File)",
"x/x;\u0016=x;bonus=x (Blob/File)",
"x/x;x=\u0016;bonus=x (Blob/File)",
"x/x;x=\"\u0016\";bonus=x (Blob/File)",
"x/x;\u0017=x;bonus=x (Blob/File)",
"x/x;x=\u0017;bonus=x (Blob/File)",
"x/x;x=\"\u0017\";bonus=x (Blob/File)",
"x/x;\u0018=x;bonus=x (Blob/File)",
"x/x;x=\u0018;bonus=x (Blob/File)",
"x/x;x=\"\u0018\";bonus=x (Blob/File)",
"x/x;\u0019=x;bonus=x (Blob/File)",
"x/x;x=\u0019;bonus=x (Blob/File)",
"x/x;x=\"\u0019\";bonus=x (Blob/File)",
"x/x;\u001a=x;bonus=x (Blob/File)",
"x/x;x=\u001a;bonus=x (Blob/File)",
"x/x;x=\"\u001a\";bonus=x (Blob/File)",
"x/x;\u001b=x;bonus=x (Blob/File)",
"x/x;x=\u001b;bonus=x (Blob/File)",
"x/x;x=\"\u001b\";bonus=x (Blob/File)",
"x/x;\u001c=x;bonus=x (Blob/File)",
"x/x;x=\u001c;bonus=x (Blob/File)",
"x/x;x=\"\u001c\";bonus=x (Blob/File)",
"x/x;\u001d=x;bonus=x (Blob/File)",
"x/x;x=\u001d;bonus=x (Blob/File)",
"x/x;x=\"\u001d\";bonus=x (Blob/File)",
"x/x;\u001e=x;bonus=x (Blob/File)",
"x/x;x=\u001e;bonus=x (Blob/File)",
"x/x;x=\"\u001e\";bonus=x (Blob/File)",
"x/x;\u001f=x;bonus=x (Blob/File)",
"x/x;x=\u001f;bonus=x (Blob/File)",
"x/x;x=\"\u001f\";bonus=x (Blob/File)",
" /x (Blob/File)",
"x/ (Blob/File)",
"x/x; =x;bonus=x (Blob/File)",
"\"/x (Blob/File)",
"x/\" (Blob/File)",
"x/x;\"=x;bonus=x (Blob/File)",
"(/x (Blob/File)",
"x/( (Blob/File)",
"x/x;(=x;bonus=x (Blob/File)",
"x/x;x=(;bonus=x (Blob/File)",
")/x (Blob/File)",
"x/) (Blob/File)",
"x/x;)=x;bonus=x (Blob/File)",
"x/x;x=);bonus=x (Blob/File)",
",/x (Blob/File)",
"x/, (Blob/File)",
"x/x;,=x;bonus=x (Blob/File)",
"x/x;x=,;bonus=x (Blob/File)",
"x/x;/=x;bonus=x (Blob/File)",
"x/x;x=/;bonus=x (Blob/File)",
":/x (Blob/File)",
"x/: (Blob/File)",
"x/x;:=x;bonus=x (Blob/File)",
"x/x;x=:;bonus=x (Blob/File)",
";/x (Blob/File)",
"x/; (Blob/File)",
"</x (Blob/File)",
"x/< (Blob/File)",
"x/x;<=x;bonus=x (Blob/File)",
"x/x;x=<;bonus=x (Blob/File)",
"=/x (Blob/File)",
"x/= (Blob/File)",
"x/x;x==;bonus=x (Blob/File)",
">/x (Blob/File)",
"x/> (Blob/File)",
"x/x;>=x;bonus=x (Blob/File)",
"x/x;x=>;bonus=x (Blob/File)",
"?/x (Blob/File)",
"x/? (Blob/File)",
"x/x;?=x;bonus=x (Blob/File)",
"x/x;x=?;bonus=x (Blob/File)",
"@/x (Blob/File)",
"x/@ (Blob/File)",
"x/x;@=x;bonus=x (Blob/File)",
"x/x;x=@;bonus=x (Blob/File)",
"[/x (Blob/File)",
"x/[ (Blob/File)",
"x/x;[=x;bonus=x (Blob/File)",
"x/x;x=[;bonus=x (Blob/File)",
"\\/x (Blob/File)",
"x/\\ (Blob/File)",
"x/x;\\=x;bonus=x (Blob/File)",
"]/x (Blob/File)",
"x/] (Blob/File)",
"x/x;]=x;bonus=x (Blob/File)",
"x/x;x=];bonus=x (Blob/File)",
"{/x (Blob/File)",
"x/{ (Blob/File)",
"x/x;{=x;bonus=x (Blob/File)",
"x/x;x={;bonus=x (Blob/File)",
"}/x (Blob/File)",
"x/} (Blob/File)",
"x/x;}=x;bonus=x (Blob/File)",
"x/x;x=};bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;€=x;bonus=x (Blob/File)",
"x/x;x=€;bonus=x (Blob/File)",
"x/x;x=\"€\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;‚=x;bonus=x (Blob/File)",
"x/x;x=‚;bonus=x (Blob/File)",
"x/x;x=\"‚\";bonus=x (Blob/File)",
"x/x;ƒ=x;bonus=x (Blob/File)",
"x/x;x=ƒ;bonus=x (Blob/File)",
"x/x;x=\"ƒ\";bonus=x (Blob/File)",
"x/x;„=x;bonus=x (Blob/File)",
"x/x;x=„;bonus=x (Blob/File)",
"x/x;x=\"„\";bonus=x (Blob/File)",
"x/x;…=x;bonus=x (Blob/File)",
"x/x;x=…;bonus=x (Blob/File)",
"x/x;x=\"…\";bonus=x (Blob/File)",
"x/x;†=x;bonus=x (Blob/File)",
"x/x;x=†;bonus=x (Blob/File)",
"x/x;x=\"†\";bonus=x (Blob/File)",
"x/x;‡=x;bonus=x (Blob/File)",
"x/x;x=‡;bonus=x (Blob/File)",
"x/x;x=\"‡\";bonus=x (Blob/File)",
"x/x;ˆ=x;bonus=x (Blob/File)",
"x/x;x=ˆ;bonus=x (Blob/File)",
"x/x;x=\"ˆ\";bonus=x (Blob/File)",
"x/x;‰=x;bonus=x (Blob/File)",
"x/x;x=‰;bonus=x (Blob/File)",
"x/x;x=\"‰\";bonus=x (Blob/File)",
"x/x;Š=x;bonus=x (Blob/File)",
"x/x;x=Š;bonus=x (Blob/File)",
"x/x;x=\"Š\";bonus=x (Blob/File)",
"x/x;‹=x;bonus=x (Blob/File)",
"x/x;x=‹;bonus=x (Blob/File)",
"x/x;x=\"‹\";bonus=x (Blob/File)",
"x/x;Œ=x;bonus=x (Blob/File)",
"x/x;x=Œ;bonus=x (Blob/File)",
"x/x;x=\"Œ\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;Ž=x;bonus=x (Blob/File)",
"x/x;x=Ž;bonus=x (Blob/File)",
"x/x;x=\"Ž\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;‘=x;bonus=x (Blob/File)",
"x/x;x=‘;bonus=x (Blob/File)",
"x/x;x=\"‘\";bonus=x (Blob/File)",
"x/x;’=x;bonus=x (Blob/File)",
"x/x;x=’;bonus=x (Blob/File)",
"x/x;x=\"’\";bonus=x (Blob/File)",
"x/x;“=x;bonus=x (Blob/File)",
"x/x;x=“;bonus=x (Blob/File)",
"x/x;x=\"“\";bonus=x (Blob/File)",
"x/x;”=x;bonus=x (Blob/File)",
"x/x;x=”;bonus=x (Blob/File)",
"x/x;x=\"”\";bonus=x (Blob/File)",
"x/x;•=x;bonus=x (Blob/File)",
"x/x;x=•;bonus=x (Blob/File)",
"x/x;x=\"•\";bonus=x (Blob/File)",
"x/x;–=x;bonus=x (Blob/File)",
"x/x;x=–;bonus=x (Blob/File)",
"x/x;x=\"–\";bonus=x (Blob/File)",
"x/x;—=x;bonus=x (Blob/File)",
"x/x;x=—;bonus=x (Blob/File)",
"x/x;x=\"—\";bonus=x (Blob/File)",
"x/x;˜=x;bonus=x (Blob/File)",
"x/x;x=˜;bonus=x (Blob/File)",
"x/x;x=\"˜\";bonus=x (Blob/File)",
"x/x;™=x;bonus=x (Blob/File)",
"x/x;x=™;bonus=x (Blob/File)",
"x/x;x=\"™\";bonus=x (Blob/File)",
"x/x;š=x;bonus=x (Blob/File)",
"x/x;x=š;bonus=x (Blob/File)",
"x/x;x=\"š\";bonus=x (Blob/File)",
"x/x;›=x;bonus=x (Blob/File)",
"x/x;x=›;bonus=x (Blob/File)",
"x/x;x=\"›\";bonus=x (Blob/File)",
"x/x;œ=x;bonus=x (Blob/File)",
"x/x;x=œ;bonus=x (Blob/File)",
"x/x;x=\"œ\";bonus=x (Blob/File)",
"x/x;=x;bonus=x (Blob/File)",
"x/x;x=;bonus=x (Blob/File)",
"x/x;x=\"\";bonus=x (Blob/File)",
"x/x;ž=x;bonus=x (Blob/File)",
"x/x;x=ž;bonus=x (Blob/File)",
"x/x;x=\"ž\";bonus=x (Blob/File)",
"x/x;Ÿ=x;bonus=x (Blob/File)",
"x/x;x=Ÿ;bonus=x (Blob/File)",
"x/x;x=\"Ÿ\";bonus=x (Blob/File)",
"x/x; =x;bonus=x (Blob/File)",
"x/x;x= ;bonus=x (Blob/File)",
"x/x;x=\" \";bonus=x (Blob/File)",
"x/x;¡=x;bonus=x (Blob/File)",
"x/x;x=¡;bonus=x (Blob/File)",
"x/x;x=\"¡\";bonus=x (Blob/File)",
"x/x;¢=x;bonus=x (Blob/File)",
"x/x;x=¢;bonus=x (Blob/File)",
"x/x;x=\"¢\";bonus=x (Blob/File)",
"x/x;£=x;bonus=x (Blob/File)",
"x/x;x=£;bonus=x (Blob/File)",
"x/x;x=\"£\";bonus=x (Blob/File)",
"x/x;¤=x;bonus=x (Blob/File)",
"x/x;x=¤;bonus=x (Blob/File)",
"x/x;x=\"¤\";bonus=x (Blob/File)",
"x/x;¥=x;bonus=x (Blob/File)",
"x/x;x=¥;bonus=x (Blob/File)",
"x/x;x=\"¥\";bonus=x (Blob/File)",
"x/x;¦=x;bonus=x (Blob/File)",
"x/x;x=¦;bonus=x (Blob/File)",
"x/x;x=\"¦\";bonus=x (Blob/File)",
"x/x;§=x;bonus=x (Blob/File)",
"x/x;x=§;bonus=x (Blob/File)",
"x/x;x=\"§\";bonus=x (Blob/File)",
"x/x;¨=x;bonus=x (Blob/File)",
"x/x;x=¨;bonus=x (Blob/File)",
"x/x;x=\"¨\";bonus=x (Blob/File)",
"x/x;©=x;bonus=x (Blob/File)",
"x/x;x=©;bonus=x (Blob/File)",
"x/x;x=\"©\";bonus=x (Blob/File)",
"x/x;ª=x;bonus=x (Blob/File)",
"x/x;x=ª;bonus=x (Blob/File)",
"x/x;x=\"ª\";bonus=x (Blob/File)",
"x/x;«=x;bonus=x (Blob/File)",
"x/x;x=«;bonus=x (Blob/File)",
"x/x;x=\"«\";bonus=x (Blob/File)",
"x/x;¬=x;bonus=x (Blob/File)",
"x/x;x=¬;bonus=x (Blob/File)",
"x/x;x=\"¬\";bonus=x (Blob/File)",
"x/x;­=x;bonus=x (Blob/File)",
"x/x;x=­;bonus=x (Blob/File)",
"x/x;x=\"­\";bonus=x (Blob/File)",
"x/x;®=x;bonus=x (Blob/File)",
"x/x;x=®;bonus=x (Blob/File)",
"x/x;x=\"®\";bonus=x (Blob/File)",
"x/x;¯=x;bonus=x (Blob/File)",
"x/x;x=¯;bonus=x (Blob/File)",
"x/x;x=\"¯\";bonus=x (Blob/File)",
"x/x;°=x;bonus=x (Blob/File)",
"x/x;x=°;bonus=x (Blob/File)",
"x/x;x=\"°\";bonus=x (Blob/File)",
"x/x;±=x;bonus=x (Blob/File)",
"x/x;x=±;bonus=x (Blob/File)",
"x/x;x=\"±\";bonus=x (Blob/File)",
"x/x;²=x;bonus=x (Blob/File)",
"x/x;x=²;bonus=x (Blob/File)",
"x/x;x=\"²\";bonus=x (Blob/File)",
"x/x;³=x;bonus=x (Blob/File)",
"x/x;x=³;bonus=x (Blob/File)",
"x/x;x=\"³\";bonus=x (Blob/File)",
"x/x;´=x;bonus=x (Blob/File)",
"x/x;x=´;bonus=x (Blob/File)",
"x/x;x=\"´\";bonus=x (Blob/File)",
"x/x;µ=x;bonus=x (Blob/File)",
"x/x;x=µ;bonus=x (Blob/File)",
"x/x;x=\"µ\";bonus=x (Blob/File)",
"x/x;¶=x;bonus=x (Blob/File)",
"x/x;x=¶;bonus=x (Blob/File)",
"x/x;x=\"¶\";bonus=x (Blob/File)",
"x/x;·=x;bonus=x (Blob/File)",
"x/x;x=·;bonus=x (Blob/File)",
"x/x;x=\"·\";bonus=x (Blob/File)",
"x/x;¸=x;bonus=x (Blob/File)",
"x/x;x=¸;bonus=x (Blob/File)",
"x/x;x=\"¸\";bonus=x (Blob/File)",
"x/x;¹=x;bonus=x (Blob/File)",
"x/x;x=¹;bonus=x (Blob/File)",
"x/x;x=\"¹\";bonus=x (Blob/File)",
"x/x;º=x;bonus=x (Blob/File)",
"x/x;x=º;bonus=x (Blob/File)",
"x/x;x=\"º\";bonus=x (Blob/File)",
"x/x;»=x;bonus=x (Blob/File)",
"x/x;x=»;bonus=x (Blob/File)",
"x/x;x=\"»\";bonus=x (Blob/File)",
"x/x;¼=x;bonus=x (Blob/File)",
"x/x;x=¼;bonus=x (Blob/File)",
"x/x;x=\"¼\";bonus=x (Blob/File)",
"x/x;½=x;bonus=x (Blob/File)",
"x/x;x=½;bonus=x (Blob/File)",
"x/x;x=\"½\";bonus=x (Blob/File)",
"x/x;¾=x;bonus=x (Blob/File)",
"x/x;x=¾;bonus=x (Blob/File)",
"x/x;x=\"¾\";bonus=x (Blob/File)",
"x/x;¿=x;bonus=x (Blob/File)",
"x/x;x=¿;bonus=x (Blob/File)",
"x/x;x=\"¿\";bonus=x (Blob/File)",
"x/x;À=x;bonus=x (Blob/File)",
"x/x;x=À;bonus=x (Blob/File)",
"x/x;x=\"À\";bonus=x (Blob/File)",
"x/x;Á=x;bonus=x (Blob/File)",
"x/x;x=Á;bonus=x (Blob/File)",
"x/x;x=\"Á\";bonus=x (Blob/File)",
"x/x;Â=x;bonus=x (Blob/File)",
"x/x;x=Â;bonus=x (Blob/File)",
"x/x;x=\"Â\";bonus=x (Blob/File)",
"x/x;Ã=x;bonus=x (Blob/File)",
"x/x;x=Ã;bonus=x (Blob/File)",
"x/x;x=\"Ã\";bonus=x (Blob/File)",
"x/x;Ä=x;bonus=x (Blob/File)",
"x/x;x=Ä;bonus=x (Blob/File)",
"x/x;x=\"Ä\";bonus=x (Blob/File)",
"x/x;Å=x;bonus=x (Blob/File)",
"x/x;x=Å;bonus=x (Blob/File)",
"x/x;x=\"Å\";bonus=x (Blob/File)",
"x/x;Æ=x;bonus=x (Blob/File)",
"x/x;x=Æ;bonus=x (Blob/File)",
"x/x;x=\"Æ\";bonus=x (Blob/File)",
"x/x;Ç=x;bonus=x (Blob/File)",
"x/x;x=Ç;bonus=x (Blob/File)",
"x/x;x=\"Ç\";bonus=x (Blob/File)",
"x/x;È=x;bonus=x (Blob/File)",
"x/x;x=È;bonus=x (Blob/File)",
"x/x;x=\"È\";bonus=x (Blob/File)",
"x/x;É=x;bonus=x (Blob/File)",
"x/x;x=É;bonus=x (Blob/File)",
"x/x;x=\"É\";bonus=x (Blob/File)",
"x/x;Ê=x;bonus=x (Blob/File)",
"x/x;x=Ê;bonus=x (Blob/File)",
"x/x;x=\"Ê\";bonus=x (Blob/File)",
"x/x;Ë=x;bonus=x (Blob/File)",
"x/x;x=Ë;bonus=x (Blob/File)",
"x/x;x=\"Ë\";bonus=x (Blob/File)",
"x/x;Ì=x;bonus=x (Blob/File)",
"x/x;x=Ì;bonus=x (Blob/File)",
"x/x;x=\"Ì\";bonus=x (Blob/File)",
"x/x;Í=x;bonus=x (Blob/File)",
"x/x;x=Í;bonus=x (Blob/File)",
"x/x;x=\"Í\";bonus=x (Blob/File)",
"x/x;Î=x;bonus=x (Blob/File)",
"x/x;x=Î;bonus=x (Blob/File)",
"x/x;x=\"Î\";bonus=x (Blob/File)",
"x/x;Ï=x;bonus=x (Blob/File)",
"x/x;x=Ï;bonus=x (Blob/File)",
"x/x;x=\"Ï\";bonus=x (Blob/File)",
"x/x;Ð=x;bonus=x (Blob/File)",
"x/x;x=Ð;bonus=x (Blob/File)",
"x/x;x=\"Ð\";bonus=x (Blob/File)",
"x/x;Ñ=x;bonus=x (Blob/File)",
"x/x;x=Ñ;bonus=x (Blob/File)",
"x/x;x=\"Ñ\";bonus=x (Blob/File)",
"x/x;Ò=x;bonus=x (Blob/File)",
"x/x;x=Ò;bonus=x (Blob/File)",
"x/x;x=\"Ò\";bonus=x (Blob/File)",
"x/x;Ó=x;bonus=x (Blob/File)",
"x/x;x=Ó;bonus=x (Blob/File)",
"x/x;x=\"Ó\";bonus=x (Blob/File)",
"x/x;Ô=x;bonus=x (Blob/File)",
"x/x;x=Ô;bonus=x (Blob/File)",
"x/x;x=\"Ô\";bonus=x (Blob/File)",
"x/x;Õ=x;bonus=x (Blob/File)",
"x/x;x=Õ;bonus=x (Blob/File)",
"x/x;x=\"Õ\";bonus=x (Blob/File)",
"x/x;Ö=x;bonus=x (Blob/File)",
"x/x;x=Ö;bonus=x (Blob/File)",
"x/x;x=\"Ö\";bonus=x (Blob/File)",
"x/x;×=x;bonus=x (Blob/File)",
"x/x;x=×;bonus=x (Blob/File)",
"x/x;x=\"×\";bonus=x (Blob/File)",
"x/x;Ø=x;bonus=x (Blob/File)",
"x/x;x=Ø;bonus=x (Blob/File)",
"x/x;x=\"Ø\";bonus=x (Blob/File)",
"x/x;Ù=x;bonus=x (Blob/File)",
"x/x;x=Ù;bonus=x (Blob/File)",
"x/x;x=\"Ù\";bonus=x (Blob/File)",
"x/x;Ú=x;bonus=x (Blob/File)",
"x/x;x=Ú;bonus=x (Blob/File)",
"x/x;x=\"Ú\";bonus=x (Blob/File)",
"x/x;Û=x;bonus=x (Blob/File)",
"x/x;x=Û;bonus=x (Blob/File)",
"x/x;x=\"Û\";bonus=x (Blob/File)",
"x/x;Ü=x;bonus=x (Blob/File)",
"x/x;x=Ü;bonus=x (Blob/File)",
"x/x;x=\"Ü\";bonus=x (Blob/File)",
"x/x;Ý=x;bonus=x (Blob/File)",
"x/x;x=Ý;bonus=x (Blob/File)",
"x/x;x=\"Ý\";bonus=x (Blob/File)",
"x/x;Þ=x;bonus=x (Blob/File)",
"x/x;x=Þ;bonus=x (Blob/File)",
"x/x;x=\"Þ\";bonus=x (Blob/File)",
"x/x;ß=x;bonus=x (Blob/File)",
"x/x;x=ß;bonus=x (Blob/File)",
"x/x;x=\"ß\";bonus=x (Blob/File)",
"x/x;à=x;bonus=x (Blob/File)",
"x/x;x=à;bonus=x (Blob/File)",
"x/x;x=\"à\";bonus=x (Blob/File)",
"x/x;á=x;bonus=x (Blob/File)",
"x/x;x=á;bonus=x (Blob/File)",
"x/x;x=\"á\";bonus=x (Blob/File)",
"x/x;â=x;bonus=x (Blob/File)",
"x/x;x=â;bonus=x (Blob/File)",
"x/x;x=\"â\";bonus=x (Blob/File)",
"x/x;ã=x;bonus=x (Blob/File)",
"x/x;x=ã;bonus=x (Blob/File)",
"x/x;x=\"ã\";bonus=x (Blob/File)",
"x/x;ä=x;bonus=x (Blob/File)",
"x/x;x=ä;bonus=x (Blob/File)",
"x/x;x=\"ä\";bonus=x (Blob/File)",
"x/x;å=x;bonus=x (Blob/File)",
"x/x;x=å;bonus=x (Blob/File)",
"x/x;x=\"å\";bonus=x (Blob/File)",
"x/x;æ=x;bonus=x (Blob/File)",
"x/x;x=æ;bonus=x (Blob/File)",
"x/x;x=\"æ\";bonus=x (Blob/File)",
"x/x;ç=x;bonus=x (Blob/File)",
"x/x;x=ç;bonus=x (Blob/File)",
"x/x;x=\"ç\";bonus=x (Blob/File)",
"x/x;è=x;bonus=x (Blob/File)",
"x/x;x=è;bonus=x (Blob/File)",
"x/x;x=\"è\";bonus=x (Blob/File)",
"x/x;é=x;bonus=x (Blob/File)",
"x/x;x=é;bonus=x (Blob/File)",
"x/x;x=\"é\";bonus=x (Blob/File)",
"x/x;ê=x;bonus=x (Blob/File)",
"x/x;x=ê;bonus=x (Blob/File)",
"x/x;x=\"ê\";bonus=x (Blob/File)",
"x/x;ë=x;bonus=x (Blob/File)",
"x/x;x=ë;bonus=x (Blob/File)",
"x/x;x=\"ë\";bonus=x (Blob/File)",
"x/x;ì=x;bonus=x (Blob/File)",
"x/x;x=ì;bonus=x (Blob/File)",
"x/x;x=\"ì\";bonus=x (Blob/File)",
"x/x;í=x;bonus=x (Blob/File)",
"x/x;x=í;bonus=x (Blob/File)",
"x/x;x=\"í\";bonus=x (Blob/File)",
"x/x;î=x;bonus=x (Blob/File)",
"x/x;x=î;bonus=x (Blob/File)",
"x/x;x=\"î\";bonus=x (Blob/File)",
"x/x;ï=x;bonus=x (Blob/File)",
"x/x;x=ï;bonus=x (Blob/File)",
"x/x;x=\"ï\";bonus=x (Blob/File)",
"x/x;ð=x;bonus=x (Blob/File)",
"x/x;x=ð;bonus=x (Blob/File)",
"x/x;x=\"ð\";bonus=x (Blob/File)",
"x/x;ñ=x;bonus=x (Blob/File)",
"x/x;x=ñ;bonus=x (Blob/File)",
"x/x;x=\"ñ\";bonus=x (Blob/File)",
"x/x;ò=x;bonus=x (Blob/File)",
"x/x;x=ò;bonus=x (Blob/File)",
"x/x;x=\"ò\";bonus=x (Blob/File)",
"x/x;ó=x;bonus=x (Blob/File)",
"x/x;x=ó;bonus=x (Blob/File)",
"x/x;x=\"ó\";bonus=x (Blob/File)",
"x/x;ô=x;bonus=x (Blob/File)",
"x/x;x=ô;bonus=x (Blob/File)",
"x/x;x=\"ô\";bonus=x (Blob/File)",
"x/x;õ=x;bonus=x (Blob/File)",
"x/x;x=õ;bonus=x (Blob/File)",
"x/x;x=\"õ\";bonus=x (Blob/File)",
"x/x;ö=x;bonus=x (Blob/File)",
"x/x;x=ö;bonus=x (Blob/File)",
"x/x;x=\"ö\";bonus=x (Blob/File)",
"x/x;÷=x;bonus=x (Blob/File)",
"x/x;x=÷;bonus=x (Blob/File)",
"x/x;x=\"÷\";bonus=x (Blob/File)",
"x/x;ø=x;bonus=x (Blob/File)",
"x/x;x=ø;bonus=x (Blob/File)",
"x/x;x=\"ø\";bonus=x (Blob/File)",
"x/x;ù=x;bonus=x (Blob/File)",
"x/x;x=ù;bonus=x (Blob/File)",
"x/x;x=\"ù\";bonus=x (Blob/File)",
"x/x;ú=x;bonus=x (Blob/File)",
"x/x;x=ú;bonus=x (Blob/File)",
"x/x;x=\"ú\";bonus=x (Blob/File)",
"x/x;û=x;bonus=x (Blob/File)",
"x/x;x=û;bonus=x (Blob/File)",
"x/x;x=\"û\";bonus=x (Blob/File)",
"x/x;ü=x;bonus=x (Blob/File)",
"x/x;x=ü;bonus=x (Blob/File)",
"x/x;x=\"ü\";bonus=x (Blob/File)",
"x/x;ý=x;bonus=x (Blob/File)",
"x/x;x=ý;bonus=x (Blob/File)",
"x/x;x=\"ý\";bonus=x (Blob/File)",
"x/x;þ=x;bonus=x (Blob/File)",
"x/x;x=þ;bonus=x (Blob/File)",
"x/x;x=\"þ\";bonus=x (Blob/File)",
"x/x;ÿ=x;bonus=x (Blob/File)",
"x/x;x=ÿ;bonus=x (Blob/File)",
"x/x;x=\"ÿ\";bonus=x (Blob/File)",
"TEXT/HTML;CHARSET=GBK (Request/Response)",
"text/html;charset= \";charset=GBK (Request/Response)",
"text/html;charset=\";charset=foo\";charset=GBK (Request/Response)",
"text/html;charset=\"\";charset=GBK (Request/Response)",
"text/html;charset=\";charset=GBK (Request/Response)",
"!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz/!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz;!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz=!#$%&'*+-.^_`|~0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz (Request/Response)",
"x/x;x=\"\t !\\\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\\\]^_`abcdefghijklmnopqrstuvwxyz{|}~€‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ\" (Request/Response)",
"text/html;test=ÿ;charset=gbk (Request/Response)",
"x/x;,=x;bonus=x (Request/Response)",
"x/x;x=,;bonus=x (Request/Response)",
"x/x;x=€;bonus=x (Request/Response)",
"x/x;x=\"€\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=‚;bonus=x (Request/Response)",
"x/x;x=\"‚\";bonus=x (Request/Response)",
"x/x;x=ƒ;bonus=x (Request/Response)",
"x/x;x=\"ƒ\";bonus=x (Request/Response)",
"x/x;x=„;bonus=x (Request/Response)",
"x/x;x=\"„\";bonus=x (Request/Response)",
"x/x;x=…;bonus=x (Request/Response)",
"x/x;x=\"…\";bonus=x (Request/Response)",
"x/x;x=†;bonus=x (Request/Response)",
"x/x;x=\"†\";bonus=x (Request/Response)",
"x/x;x=‡;bonus=x (Request/Response)",
"x/x;x=\"‡\";bonus=x (Request/Response)",
"x/x;x=ˆ;bonus=x (Request/Response)",
"x/x;x=\"ˆ\";bonus=x (Request/Response)",
"x/x;x=‰;bonus=x (Request/Response)",
"x/x;x=\"‰\";bonus=x (Request/Response)",
"x/x;x=Š;bonus=x (Request/Response)",
"x/x;x=\"Š\";bonus=x (Request/Response)",
"x/x;x=‹;bonus=x (Request/Response)",
"x/x;x=\"‹\";bonus=x (Request/Response)",
"x/x;x=Œ;bonus=x (Request/Response)",
"x/x;x=\"Œ\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=Ž;bonus=x (Request/Response)",
"x/x;x=\"Ž\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=‘;bonus=x (Request/Response)",
"x/x;x=\"‘\";bonus=x (Request/Response)",
"x/x;x=’;bonus=x (Request/Response)",
"x/x;x=\"’\";bonus=x (Request/Response)",
"x/x;x=“;bonus=x (Request/Response)",
"x/x;x=\"“\";bonus=x (Request/Response)",
"x/x;x=”;bonus=x (Request/Response)",
"x/x;x=\"”\";bonus=x (Request/Response)",
"x/x;x=•;bonus=x (Request/Response)",
"x/x;x=\"•\";bonus=x (Request/Response)",
"x/x;x=–;bonus=x (Request/Response)",
"x/x;x=\"–\";bonus=x (Request/Response)",
"x/x;x=—;bonus=x (Request/Response)",
"x/x;x=\"—\";bonus=x (Request/Response)",
"x/x;x=˜;bonus=x (Request/Response)",
"x/x;x=\"˜\";bonus=x (Request/Response)",
"x/x;x=™;bonus=x (Request/Response)",
"x/x;x=\"™\";bonus=x (Request/Response)",
"x/x;x=š;bonus=x (Request/Response)",
"x/x;x=\"š\";bonus=x (Request/Response)",
"x/x;x=›;bonus=x (Request/Response)",
"x/x;x=\"›\";bonus=x (Request/Response)",
"x/x;x=œ;bonus=x (Request/Response)",
"x/x;x=\"œ\";bonus=x (Request/Response)",
"x/x;x=;bonus=x (Request/Response)",
"x/x;x=\"\";bonus=x (Request/Response)",
"x/x;x=ž;bonus=x (Request/Response)",
"x/x;x=\"ž\";bonus=x (Request/Response)",
"x/x;x=Ÿ;bonus=x (Request/Response)",
"x/x;x=\"Ÿ\";bonus=x (Request/Response)",
"x/x;x= ;bonus=x (Request/Response)",
"x/x;x=\" \";bonus=x (Request/Response)",
"x/x;x=¡;bonus=x (Request/Response)",
"x/x;x=\"¡\";bonus=x (Request/Response)",
"x/x;x=¢;bonus=x (Request/Response)",
"x/x;x=\"¢\";bonus=x (Request/Response)",
"x/x;x=£;bonus=x (Request/Response)",
"x/x;x=\"£\";bonus=x (Request/Response)",
"x/x;x=¤;bonus=x (Request/Response)",
"x/x;x=\"¤\";bonus=x (Request/Response)",
"x/x;x=¥;bonus=x (Request/Response)",
"x/x;x=\"¥\";bonus=x (Request/Response)",
"x/x;x=¦;bonus=x (Request/Response)",
"x/x;x=\"¦\";bonus=x (Request/Response)",
"x/x;x=§;bonus=x (Request/Response)",
"x/x;x=\"§\";bonus=x (Request/Response)",
"x/x;x=¨;bonus=x (Request/Response)",
"x/x;x=\"¨\";bonus=x (Request/Response)",
"x/x;x=©;bonus=x (Request/Response)",
"x/x;x=\"©\";bonus=x (Request/Response)",
"x/x;x=ª;bonus=x (Request/Response)",
"x/x;x=\"ª\";bonus=x (Request/Response)",
"x/x;x=«;bonus=x (Request/Response)",
"x/x;x=\"«\";bonus=x (Request/Response)",
"x/x;x=¬;bonus=x (Request/Response)",
"x/x;x=\"¬\";bonus=x (Request/Response)",
"x/x;x=­;bonus=x (Request/Response)",
"x/x;x=\"­\";bonus=x (Request/Response)",
"x/x;x=®;bonus=x (Request/Response)",
"x/x;x=\"®\";bonus=x (Request/Response)",
"x/x;x=¯;bonus=x (Request/Response)",
"x/x;x=\"¯\";bonus=x (Request/Response)",
"x/x;x=°;bonus=x (Request/Response)",
"x/x;x=\"°\";bonus=x (Request/Response)",
"x/x;x=±;bonus=x (Request/Response)",
"x/x;x=\"±\";bonus=x (Request/Response)",
"x/x;x=²;bonus=x (Request/Response)",
"x/x;x=\"²\";bonus=x (Request/Response)",
"x/x;x=³;bonus=x (Request/Response)",
"x/x;x=\"³\";bonus=x (Request/Response)",
"x/x;x=´;bonus=x (Request/Response)",
"x/x;x=\"´\";bonus=x (Request/Response)",
"x/x;x=µ;bonus=x (Request/Response)",
"x/x;x=\"µ\";bonus=x (Request/Response)",
"x/x;x=¶;bonus=x (Request/Response)",
"x/x;x=\"¶\";bonus=x (Request/Response)",
"x/x;x=·;bonus=x (Request/Response)",
"x/x;x=\"·\";bonus=x (Request/Response)",
"x/x;x=¸;bonus=x (Request/Response)",
"x/x;x=\"¸\";bonus=x (Request/Response)",
"x/x;x=¹;bonus=x (Request/Response)",
"x/x;x=\"¹\";bonus=x (Request/Response)",
"x/x;x=º;bonus=x (Request/Response)",
"x/x;x=\"º\";bonus=x (Request/Response)",
"x/x;x=»;bonus=x (Request/Response)",
"x/x;x=\"»\";bonus=x (Request/Response)",
"x/x;x=¼;bonus=x (Request/Response)",
"x/x;x=\"¼\";bonus=x (Request/Response)",
"x/x;x=½;bonus=x (Request/Response)",
"x/x;x=\"½\";bonus=x (Request/Response)",
"x/x;x=¾;bonus=x (Request/Response)",
"x/x;x=\"¾\";bonus=x (Request/Response)",
"x/x;x=¿;bonus=x (Request/Response)",
"x/x;x=\"¿\";bonus=x (Request/Response)",
"x/x;x=À;bonus=x (Request/Response)",
"x/x;x=\"À\";bonus=x (Request/Response)",
"x/x;x=Á;bonus=x (Request/Response)",
"x/x;x=\"Á\";bonus=x (Request/Response)",
"x/x;x=Â;bonus=x (Request/Response)",
"x/x;x=\"Â\";bonus=x (Request/Response)",
"x/x;x=Ã;bonus=x (Request/Response)",
"x/x;x=\"Ã\";bonus=x (Request/Response)",
"x/x;x=Ä;bonus=x (Request/Response)",
"x/x;x=\"Ä\";bonus=x (Request/Response)",
"x/x;x=Å;bonus=x (Request/Response)",
"x/x;x=\"Å\";bonus=x (Request/Response)",
"x/x;x=Æ;bonus=x (Request/Response)",
"x/x;x=\"Æ\";bonus=x (Request/Response)",
"x/x;x=Ç;bonus=x (Request/Response)",
"x/x;x=\"Ç\";bonus=x (Request/Response)",
"x/x;x=È;bonus=x (Request/Response)",
"x/x;x=\"È\";bonus=x (Request/Response)",
"x/x;x=É;bonus=x (Request/Response)",
"x/x;x=\"É\";bonus=x (Request/Response)",
"x/x;x=Ê;bonus=x (Request/Response)",
"x/x;x=\"Ê\";bonus=x (Request/Response)",
"x/x;x=Ë;bonus=x (Request/Response)",
"x/x;x=\"Ë\";bonus=x (Request/Response)",
"x/x;x=Ì;bonus=x (Request/Response)",
"x/x;x=\"Ì\";bonus=x (Request/Response)",
"x/x;x=Í;bonus=x (Request/Response)",
"x/x;x=\"Í\";bonus=x (Request/Response)",
"x/x;x=Î;bonus=x (Request/Response)",
"x/x;x=\"Î\";bonus=x (Request/Response)",
"x/x;x=Ï;bonus=x (Request/Response)",
"x/x;x=\"Ï\";bonus=x (Request/Response)",
"x/x;x=Ð;bonus=x (Request/Response)",
"x/x;x=\"Ð\";bonus=x (Request/Response)",
"x/x;x=Ñ;bonus=x (Request/Response)",
"x/x;x=\"Ñ\";bonus=x (Request/Response)",
"x/x;x=Ò;bonus=x (Request/Response)",
"x/x;x=\"Ò\";bonus=x (Request/Response)",
"x/x;x=Ó;bonus=x (Request/Response)",
"x/x;x=\"Ó\";bonus=x (Request/Response)",
"x/x;x=Ô;bonus=x (Request/Response)",
"x/x;x=\"Ô\";bonus=x (Request/Response)",
"x/x;x=Õ;bonus=x (Request/Response)",
"x/x;x=\"Õ\";bonus=x (Request/Response)",
"x/x;x=Ö;bonus=x (Request/Response)",
"x/x;x=\"Ö\";bonus=x (Request/Response)",
"x/x;x=×;bonus=x (Request/Response)",
"x/x;x=\"×\";bonus=x (Request/Response)",
"x/x;x=Ø;bonus=x (Request/Response)",
"x/x;x=\"Ø\";bonus=x (Request/Response)",
"x/x;x=Ù;bonus=x (Request/Response)",
"x/x;x=\"Ù\";bonus=x (Request/Response)",
"x/x;x=Ú;bonus=x (Request/Response)",
"x/x;x=\"Ú\";bonus=x (Request/Response)",
"x/x;x=Û;bonus=x (Request/Response)",
"x/x;x=\"Û\";bonus=x (Request/Response)",
"x/x;x=Ü;bonus=x (Request/Response)",
"x/x;x=\"Ü\";bonus=x (Request/Response)",
"x/x;x=Ý;bonus=x (Request/Response)",
"x/x;x=\"Ý\";bonus=x (Request/Response)",
"x/x;x=Þ;bonus=x (Request/Response)",
"x/x;x=\"Þ\";bonus=x (Request/Response)",
"x/x;x=ß;bonus=x (Request/Response)",
"x/x;x=\"ß\";bonus=x (Request/Response)",
"x/x;x=à;bonus=x (Request/Response)",
"x/x;x=\"à\";bonus=x (Request/Response)",
"x/x;x=á;bonus=x (Request/Response)",
"x/x;x=\"á\";bonus=x (Request/Response)",
"x/x;x=â;bonus=x (Request/Response)",
"x/x;x=\"â\";bonus=x (Request/Response)",
"x/x;x=ã;bonus=x (Request/Response)",
"x/x;x=\"ã\";bonus=x (Request/Response)",
"x/x;x=ä;bonus=x (Request/Response)",
"x/x;x=\"ä\";bonus=x (Request/Response)",
"x/x;x=å;bonus=x (Request/Response)",
"x/x;x=\"å\";bonus=x (Request/Response)",
"x/x;x=æ;bonus=x (Request/Response)",
"x/x;x=\"æ\";bonus=x (Request/Response)",
"x/x;x=ç;bonus=x (Request/Response)",
"x/x;x=\"ç\";bonus=x (Request/Response)",
"x/x;x=è;bonus=x (Request/Response)",
"x/x;x=\"è\";bonus=x (Request/Response)",
"x/x;x=é;bonus=x (Request/Response)",
"x/x;x=\"é\";bonus=x (Request/Response)",
"x/x;x=ê;bonus=x (Request/Response)",
"x/x;x=\"ê\";bonus=x (Request/Response)",
"x/x;x=ë;bonus=x (Request/Response)",
"x/x;x=\"ë\";bonus=x (Request/Response)",
"x/x;x=ì;bonus=x (Request/Response)",
"x/x;x=\"ì\";bonus=x (Request/Response)",
"x/x;x=í;bonus=x (Request/Response)",
"x/x;x=\"í\";bonus=x (Request/Response)",
"x/x;x=î;bonus=x (Request/Response)",
"x/x;x=\"î\";bonus=x (Request/Response)",
"x/x;x=ï;bonus=x (Request/Response)",
"x/x;x=\"ï\";bonus=x (Request/Response)",
"x/x;x=ð;bonus=x (Request/Response)",
"x/x;x=\"ð\";bonus=x (Request/Response)",
"x/x;x=ñ;bonus=x (Request/Response)",
"x/x;x=\"ñ\";bonus=x (Request/Response)",
"x/x;x=ò;bonus=x (Request/Response)",
"x/x;x=\"ò\";bonus=x (Request/Response)",
"x/x;x=ó;bonus=x (Request/Response)",
"x/x;x=\"ó\";bonus=x (Request/Response)",
"x/x;x=ô;bonus=x (Request/Response)",
"x/x;x=\"ô\";bonus=x (Request/Response)",
"x/x;x=õ;bonus=x (Request/Response)",
"x/x;x=\"õ\";bonus=x (Request/Response)",
"x/x;x=ö;bonus=x (Request/Response)",
"x/x;x=\"ö\";bonus=x (Request/Response)",
"x/x;x=÷;bonus=x (Request/Response)",
"x/x;x=\"÷\";bonus=x (Request/Response)",
"x/x;x=ø;bonus=x (Request/Response)",
"x/x;x=\"ø\";bonus=x (Request/Response)",
"x/x;x=ù;bonus=x (Request/Response)",
"x/x;x=\"ù\";bonus=x (Request/Response)",
"x/x;x=ú;bonus=x (Request/Response)",
"x/x;x=\"ú\";bonus=x (Request/Response)",
"x/x;x=û;bonus=x (Request/Response)",
"x/x;x=\"û\";bonus=x (Request/Response)",
"x/x;x=ü;bonus=x (Request/Response)",
"x/x;x=\"ü\";bonus=x (Request/Response)",
"x/x;x=ý;bonus=x (Request/Response)",
"x/x;x=\"ý\";bonus=x (Request/Response)",
"x/x;x=þ;bonus=x (Request/Response)",
"x/x;x=\"þ\";bonus=x (Request/Response)",
"x/x;x=ÿ;bonus=x (Request/Response)",
"x/x;x=\"ÿ\";bonus=x (Request/Response)"
],
"charset-parameter.window.html": [
"text/html;charset=gbk",
"TEXT/HTML;CHARSET=GBK",
"text/html;charset=gbk(",
"text/html;x=(;charset=gbk",
"text/html;charset=gbk;charset=windows-1255",
"text/html;charset=();charset=GBK",
"text/html;charset =gbk",
"text/html ;charset=gbk",
"text/html; charset=gbk",
"text/html;charset= gbk",
"text/html;charset= \"gbk\"",
"text/html;charset=\u000bgbk",
"text/html;charset=\fgbk",
"text/html;\u000bcharset=gbk",
"text/html;\fcharset=gbk",
"text/html;charset='gbk'",
"text/html;charset='gbk",
"text/html;charset=gbk'",
"text/html;charset=';charset=GBK",
"text/html;test;charset=gbk",
"text/html;test=;charset=gbk",
"text/html;';charset=gbk",
"text/html;\";charset=gbk",
"text/html ; ; charset=gbk",
"text/html;;;;charset=gbk",
"text/html;charset= \";charset=GBK",
"text/html;charset=\";charset=foo\";charset=GBK",
"text/html;charset=\"gbk\"",
"text/html;charset=\"gbk",
"text/html;charset=gbk\"",
"text/html;charset=\" gbk\"",
"text/html;charset=\"gbk \"",
"text/html;charset=\"\\ gbk\"",
"text/html;charset=\"\\g\\b\\k\"",
"text/html;charset=\"gbk\"x",
"text/html;charset=\"\";charset=GBK",
"text/html;charset=\";charset=GBK",
"text/html;charset={gbk}",
"text/html;0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789=x;charset=gbk",
"text/html;test=ÿ;charset=gbk"
]
},
"media": {
"media-sniff.window.html": false
}
}
}