2021-10-11 09:45:02 -04:00
|
|
|
[WILDCARD]
|
2022-04-16 15:51:55 -04:00
|
|
|
running 3 tests from ./test/steps/failing_steps.ts
|
2022-04-11 12:27:17 -04:00
|
|
|
nested failure ...
|
|
|
|
|
step 1 ...
|
|
|
|
|
inner 1 ... FAILED ([WILDCARD])
|
2022-05-04 19:15:54 -04:00
|
|
|
error: Error: Failed.
|
2022-04-16 13:51:12 -04:00
|
|
|
throw new Error("Failed.");
|
|
|
|
|
^
|
2021-10-11 09:45:02 -04:00
|
|
|
at [WILDCARD]/failing_steps.ts:[WILDCARD]
|
|
|
|
|
[WILDCARD]
|
2022-04-11 12:27:17 -04:00
|
|
|
inner 2 ... ok ([WILDCARD])
|
2022-07-15 13:09:22 -04:00
|
|
|
step 1 ... FAILED ([WILDCARD])
|
|
|
|
|
nested failure ... FAILED ([WILDCARD])
|
2022-04-11 12:27:17 -04:00
|
|
|
multiple test step failures ...
|
|
|
|
|
step 1 ... FAILED ([WILDCARD])
|
2022-05-04 19:15:54 -04:00
|
|
|
error: Error: Fail.
|
2022-04-16 13:51:12 -04:00
|
|
|
throw new Error("Fail.");
|
|
|
|
|
^
|
2021-10-11 09:45:02 -04:00
|
|
|
[WILDCARD]
|
2022-04-11 12:27:17 -04:00
|
|
|
step 2 ... FAILED ([WILDCARD])
|
2022-05-04 19:15:54 -04:00
|
|
|
error: Error: Fail.
|
2022-04-16 13:51:12 -04:00
|
|
|
await t.step("step 2", () => Promise.reject(new Error("Fail.")));
|
|
|
|
|
^
|
2021-10-11 09:45:02 -04:00
|
|
|
at [WILDCARD]/failing_steps.ts:[WILDCARD]
|
|
|
|
|
[WILDCARD]
|
2022-07-15 13:09:22 -04:00
|
|
|
multiple test step failures ... FAILED ([WILDCARD])
|
2022-04-11 12:27:17 -04:00
|
|
|
failing step in failing test ...
|
|
|
|
|
step 1 ... FAILED ([WILDCARD])
|
2022-05-04 19:15:54 -04:00
|
|
|
error: Error: Fail.
|
2022-04-16 13:51:12 -04:00
|
|
|
throw new Error("Fail.");
|
|
|
|
|
^
|
2021-10-11 09:45:02 -04:00
|
|
|
at [WILDCARD]/failing_steps.ts:[WILDCARD]
|
|
|
|
|
at [WILDCARD]
|
2022-07-15 13:09:22 -04:00
|
|
|
failing step in failing test ... FAILED ([WILDCARD])
|
2021-10-11 09:45:02 -04:00
|
|
|
|
2022-05-09 04:56:13 -04:00
|
|
|
ERRORS
|
2021-10-11 09:45:02 -04:00
|
|
|
|
2022-05-04 19:15:54 -04:00
|
|
|
nested failure => ./test/steps/failing_steps.ts:[WILDCARD]
|
|
|
|
|
error: Error: 1 test step failed.
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
at runTest (internal:cli/40_testing.js:[WILDCARD])
|
|
|
|
|
at async runTests (internal:cli/40_testing.js:[WILDCARD])
|
2021-10-11 09:45:02 -04:00
|
|
|
|
2022-05-04 19:15:54 -04:00
|
|
|
multiple test step failures => ./test/steps/failing_steps.ts:[WILDCARD]
|
|
|
|
|
error: Error: 2 test steps failed.
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
at runTest (internal:cli/40_testing.js:[WILDCARD])
|
|
|
|
|
at async runTests (internal:cli/40_testing.js:[WILDCARD])
|
2021-10-11 09:45:02 -04:00
|
|
|
|
2022-05-04 19:15:54 -04:00
|
|
|
failing step in failing test => ./test/steps/failing_steps.ts:[WILDCARD]
|
|
|
|
|
error: Error: Fail test.
|
2022-04-16 13:51:12 -04:00
|
|
|
throw new Error("Fail test.");
|
|
|
|
|
^
|
2021-10-11 09:45:02 -04:00
|
|
|
at [WILDCARD]/failing_steps.ts:[WILDCARD]
|
|
|
|
|
|
2022-05-09 04:56:13 -04:00
|
|
|
FAILURES
|
2021-10-11 09:45:02 -04:00
|
|
|
|
2022-05-04 19:15:54 -04:00
|
|
|
nested failure => ./test/steps/failing_steps.ts:[WILDCARD]
|
|
|
|
|
multiple test step failures => ./test/steps/failing_steps.ts:[WILDCARD]
|
|
|
|
|
failing step in failing test => ./test/steps/failing_steps.ts:[WILDCARD]
|
2021-10-11 09:45:02 -04:00
|
|
|
|
2022-06-14 14:51:49 -04:00
|
|
|
FAILED | 0 passed (1 step) | 3 failed (5 steps) ([WILDCARD])
|
2021-10-11 09:45:02 -04:00
|
|
|
|
|
|
|
|
error: Test failed
|