denoland-deno/tests/testdata/test/sanitizer/ops_sanitizer_unstable.out

⚠️ The `--trace-ops` flag is deprecated and will be removed in Deno 2.0.
Use the `--trace-leaks` flag instead.
Check [WILDCARD]/ops_sanitizer_unstable.ts
running 2 tests from [WILDCARD]/ops_sanitizer_unstable.ts
no-op ... ok ([WILDCARD])
leak interval ... FAILED ([WILDCARD])

 ERRORS 

leak interval => [WILDCARD]/ops_sanitizer_unstable.ts:[WILDCARD]
error: Leaks detected:
  - An interval was started in this test, but never completed. This is often caused by not calling `clearInterval`. The operation was started here:
    at [WILDCARD]
    at setInterval ([WILDCARD])
    at fn ([WILDCARD]/ops_sanitizer_unstable.ts:[WILDCARD])
    at [WILDCARD]

 FAILURES 

leak interval => [WILDCARD]/ops_sanitizer_unstable.ts:[WILDCARD]

FAILED | 1 passed | 1 failed ([WILDCARD])

error: Test failed
chore(cli): rename `--trace-ops` to `--trace-leaks` (#22598) As we add tracing to more types of runtime activity, `--trace-ops` is less useful of a name. `--trace-leaks` better reflects that this feature traces both ops and timers, and will eventually trace resource opening as well. This keeps `--trace-ops` as an alias for `--trace-leaks`, but prints a warning to the console suggesting migration to `--trace-leaks`. One test continues to use `--trace-ops` to test the deprecation warning. --------- Signed-off-by: Matt Mastracci <matthew@mastracci.com> 2024-02-28 11:12:43 -05:00			⚠️ The `--trace-ops` flag is deprecated and will be removed in Deno 2.0.
			Use the `--trace-leaks` flag instead.
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_unstable.ts`
			`running 2 tests from [WILDCARD]/ops_sanitizer_unstable.ts`
feat(test): Improve testing report output (#14255) Following changes were done in this commit: - remove "test" prefix before each test - use gray color for "running N tests from ..." prompt - use relative path or remote URL instead of full URL in "running N tests from ..." prompt - in "failures" section, add file path/remote URL before the test name Co-authored-by: Yoshiya Hinosawa <stibium121@gmail.com> 2022-04-11 12:27:17 -04:00			`no-op ... ok ([WILDCARD])`
			`leak interval ... FAILED ([WILDCARD])`
feat: provide ops details for ops sanitizer failures (#12188) 2021-10-11 11:00:33 -04:00
feat(test): change "failures:" headers in test report (#14490) 2022-05-09 04:56:13 -04:00			`ERRORS`
feat: provide ops details for ops sanitizer failures (#12188) 2021-10-11 11:00:33 -04:00
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			`leak interval => [WILDCARD]/ops_sanitizer_unstable.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			- An interval was started in this test, but never completed. This is often caused by not calling `clearInterval`. The operation was started here:
feat(test): improved op sanitizer errors + traces (#13676) This commit improves the error messages for the `deno test` async op sanitizer. It does this in two ways: - it uses handwritten error messages for each op that could be leaking - it includes traces showing where each op was started This "async op tracing" functionality is a new feature in deno_core. It likely has a significant performance impact, which is why it is only enabled in tests. 2022-02-16 13:53:17 -05:00			`at [WILDCARD]`
			`at setInterval ([WILDCARD])`
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 fn ([WILDCARD]/ops_sanitizer_unstable.ts:[WILDCARD])`
feat: provide ops details for ops sanitizer failures (#12188) 2021-10-11 11:00:33 -04:00			`at [WILDCARD]`

feat(test): change "failures:" headers in test report (#14490) 2022-05-09 04:56:13 -04:00			`FAILURES`
feat: provide ops details for ops sanitizer failures (#12188) 2021-10-11 11:00:33 -04:00
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			`leak interval => [WILDCARD]/ops_sanitizer_unstable.ts:[WILDCARD]`
feat: provide ops details for ops sanitizer failures (#12188) 2021-10-11 11:00:33 -04:00
feat(test): update test summary report (#14629) 2022-06-14 14:51:49 -04:00			`FAILED \| 1 passed \| 1 failed ([WILDCARD])`
feat: provide ops details for ops sanitizer failures (#12188) 2021-10-11 11:00:33 -04:00
			`error: Test failed`