foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-29 16:30:56 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/tests/testdata/test/sanitizer/ops_sanitizer_multiple_timeout_tests.out

46 lines
2 KiB
Text
Raw Normal View History

chore(cli): pre-factor the sanitizer tests (#22436) Moving tests around so that we can make #22413 smaller
2024-02-16 12:49:42 -05:00
Check [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts
running 2 tests from [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts
test 1 ... FAILED ([WILDCARD])
test 2 ... FAILED ([WILDCARD])
ERRORS
test 1 => [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD]
refactor(cli): move op sanitizer to Rust (#22413) The format of the sanitizers will change a little bit: - If multiple async ops leak and traces are on, we repeat the async op header once per stack trace. - All leaks are aggregated under a "Leaks detected:" banner as the new timers are eventually going to be added, and these are neither ops nor resources. - `1 async op` is now `An async op` - If ops and resources leak, we show both (rather than op leaks masking resources) Follow-on to https://github.com/denoland/deno/pull/22226
2024-02-16 16:22:12 -05:00
error: Leaks detected:
perf(cli): use new deno_core timers (#22569) Improves #19100 Fixes #20356 Replaces #20428 Changes made in deno_core to support this: - [x] Errors must be handled in setTimeout callbacks - [x] Microtask ordering is not-quite-right - [x] Timer cancellation must be checked right before dispatch - [x] Timer sanitizer - [x] Move high-res timer to deno_core - [x] Timers need opcall tracing
2024-03-01 13:15:18 -05:00
- A timer was started in this test, but never completed. This is often caused by not calling `clearTimeout`. The operation was started here:
chore(cli): pre-factor the sanitizer tests (#22436) Moving tests around so that we can make #22413 smaller
2024-02-16 12:49:42 -05:00
at [WILDCARD]
at setTimeout ([WILDCARD])
at test ([WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD])
at [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:8:27
at [WILDCARD]
perf(cli): use new deno_core timers (#22569) Improves #19100 Fixes #20356 Replaces #20428 Changes made in deno_core to support this: - [x] Errors must be handled in setTimeout callbacks - [x] Microtask ordering is not-quite-right - [x] Timer cancellation must be checked right before dispatch - [x] Timer sanitizer - [x] Move high-res timer to deno_core - [x] Timers need opcall tracing
2024-03-01 13:15:18 -05:00
- A timer was started in this test, but never completed. This is often caused by not calling `clearTimeout`. The operation was started here:
chore(cli): pre-factor the sanitizer tests (#22436) Moving tests around so that we can make #22413 smaller
2024-02-16 12:49:42 -05:00
at [WILDCARD]
at setTimeout ([WILDCARD])
at test ([WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD])
at [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:8:27
at [WILDCARD]
test 2 => [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD]
refactor(cli): move op sanitizer to Rust (#22413) The format of the sanitizers will change a little bit: - If multiple async ops leak and traces are on, we repeat the async op header once per stack trace. - All leaks are aggregated under a "Leaks detected:" banner as the new timers are eventually going to be added, and these are neither ops nor resources. - `1 async op` is now `An async op` - If ops and resources leak, we show both (rather than op leaks masking resources) Follow-on to https://github.com/denoland/deno/pull/22226
2024-02-16 16:22:12 -05:00
error: Leaks detected:
perf(cli): use new deno_core timers (#22569) Improves #19100 Fixes #20356 Replaces #20428 Changes made in deno_core to support this: - [x] Errors must be handled in setTimeout callbacks - [x] Microtask ordering is not-quite-right - [x] Timer cancellation must be checked right before dispatch - [x] Timer sanitizer - [x] Move high-res timer to deno_core - [x] Timers need opcall tracing
2024-03-01 13:15:18 -05:00
- A timer was started in this test, but never completed. This is often caused by not calling `clearTimeout`. The operation was started here:
chore(cli): pre-factor the sanitizer tests (#22436) Moving tests around so that we can make #22413 smaller
2024-02-16 12:49:42 -05:00
at [WILDCARD]
at setTimeout ([WILDCARD])
at test ([WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD])
at [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:10:27
at [WILDCARD]
perf(cli): use new deno_core timers (#22569) Improves #19100 Fixes #20356 Replaces #20428 Changes made in deno_core to support this: - [x] Errors must be handled in setTimeout callbacks - [x] Microtask ordering is not-quite-right - [x] Timer cancellation must be checked right before dispatch - [x] Timer sanitizer - [x] Move high-res timer to deno_core - [x] Timers need opcall tracing
2024-03-01 13:15:18 -05:00
- A timer was started in this test, but never completed. This is often caused by not calling `clearTimeout`. The operation was started here:
chore(cli): pre-factor the sanitizer tests (#22436) Moving tests around so that we can make #22413 smaller
2024-02-16 12:49:42 -05:00
at [WILDCARD]
at setTimeout ([WILDCARD])
at test ([WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD])
at [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:10:27
at [WILDCARD]
FAILURES
test 1 => [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD]
test 2 => [WILDCARD]/ops_sanitizer_multiple_timeout_tests.ts:[WILDCARD]
FAILED | 0 passed | 2 failed ([WILDCARD])
error: Test failed
Copy permalink