foster/denoland-deno
0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-10-31 09:14:20 -04:00
Code Issues Wiki Activity
denoland-deno/cli/tests/testdata/test/ops_sanitizer_unstable.out

25 lines
767 B
Text
Raw Normal View History

feat: provide ops details for ops sanitizer failures (#12188)
2021-10-11 11:00:33 -04:00
Check [WILDCARD]/testdata/test/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
running 2 tests from test/ops_sanitizer_unstable.ts
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
failures:
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
test/ops_sanitizer_unstable.ts > leak interval
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
Test case is leaking async ops.
feat: provide ops details for ops sanitizer failures (#12188)
2021-10-11 11:00:33 -04:00
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
- 1 async operation to sleep for a duration was started in this test, but never completed. This is often caused by not cancelling a `setTimeout` or `setInterval` call. The operation was started here:
at [WILDCARD]
at setInterval ([WILDCARD])
at [WILDCARD]/testdata/test/ops_sanitizer_unstable.ts:3:3
feat: provide ops details for ops sanitizer failures (#12188)
2021-10-11 11:00:33 -04:00
at [WILDCARD]
failures:
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
test/ops_sanitizer_unstable.ts
feat: provide ops details for ops sanitizer failures (#12188)
2021-10-11 11:00:33 -04:00
leak interval
test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out ([WILDCARD])
error: Test failed
Copy permalink