Skip to content

chore(deps): update angular dependencies - abandoned #10694

chore(deps): update angular dependencies - abandoned

chore(deps): update angular dependencies - abandoned #10694

Triggered via pull request August 23, 2024 08:48
Status Failure
Total duration 1h 5m 57s
Artifacts 11

main.yml

on: pull_request
Matrix: checks / test
it-tests  /  prepare-verdaccio
2m 14s
it-tests / prepare-verdaccio
e2e-tests  /  e2e-tests
5m 3s
e2e-tests / e2e-tests
documentation-pr  /  build
3m 14s
documentation-pr / build
Matrix: it-tests / it-tests
documentation-pr  /  deploy-on-azure-static-webapp
0s
documentation-pr / deploy-on-azure-static-webapp
documentation-main  /  deploy-on-azure-static-webapp
documentation-main / deploy-on-azure-static-webapp
publish-packages  /  publish-extensions
publish-packages / publish-extensions
Fit to window
Zoom out
Zoom in

Annotations

28 errors and 8 warnings
checks / test (ubuntu-latest)
Process completed with exit code 1.
checks / test (windows-latest)
Process completed with exit code 1.
new otter application › should build empty app: packages/@o3r/core/schematics/index.it.spec.ts#L28
expect(received).not.toThrow() Error name: "Error" Error message: "Command failed: npm exec ng add @o3r/core@~999 -- --preset all --project-name test-app --skip-confirmation STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_21_004Z-debug-0.log· OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_21_004Z-debug-0.log " 100 | // Yarn doesn't log errors on stderr, so we need to get them from stdout to have them in the reports 101 | // eslint-disable-next-line @typescript-eslint/restrict-template-expressions > 102 | throw new Error(`Command failed: ${args.join(' ') }\nSTDERR:\n${err.stderr?.toString() || ''}\nOUTPUT:\n${err.output?.toString() || ''}`); | ^ 103 | } 104 | } 105 | at execCmd (packages/@o3r/test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (packages/@o3r/test-helpers/src/utilities/package-manager.ts:163:10) at packages/@o3r/core/schematics/index.it.spec.ts:28:36 at Object.<anonymous> (.yarn/cache/expect-npm-29.7.0-62e9f7979e-63f97bc51f.zip/node_modules/expect/build/toThrowMatchers.js:74:11) at Object.throwingMatcher [as toThrow] (.yarn/cache/expect-npm-29.7.0-62e9f7979e-63f97bc51f.zip/node_modules/expect/build/index.js:320:21) at Object.<anonymous> (packages/@o3r/core/schematics/index.it.spec.ts:28:177) at Object.<anonymous> (schematics/index.it.spec.ts:28:177)
ng add eslint-config › should add eslint-config to an application: packages/@o3r/test-helpers/src/utilities/package-manager.ts#L102
Command failed: npm exec ng add @o3r/eslint-config-otter@~999 -- --skip-confirmation --project-name test-app STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_20_966Z-debug-0.log OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_20_966Z-debug-0.log at execCmd (../test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (../test-helpers/src/utilities/package-manager.ts:163:10) at Object.<anonymous> (schematics/index.it.spec.ts:22:23)
ng add eslint-config › should add eslint-config to a library: packages/@o3r/test-helpers/src/utilities/package-manager.ts#L102
Command failed: npm exec ng add @o3r/eslint-config-otter@~999 -- --skip-confirmation --project-name test-lib STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_21_997Z-debug-0.log OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_21_997Z-debug-0.log at execCmd (../test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (../test-helpers/src/utilities/package-manager.ts:163:10) at Object.<anonymous> (schematics/index.it.spec.ts:51:23)
aggregate migration scripts › should create migration scripts including lib content: .pnp.cjs#L63224
ENOENT: no such file or directory, open '/home/runner/work/otter/it-tests/test-app-extractors-aggregate-migration-scripts/angular.json' at NodeFS.readFileSync (../../../.pnp.cjs:63224:24) at makeCallSync.subPath.subPath (../../../.pnp.cjs:63917:26) at ZipOpenFS.makeCallSync (../../../.pnp.cjs:64039:14) at ZipOpenFS.readFileSync (../../../.pnp.cjs:63916:17) at VirtualFS.readFileSync (../../../.pnp.cjs:62830:24) at PosixFS.readFileSync (../../../.pnp.cjs:62830:24) at NodePathFS.readFileSync (../../../.pnp.cjs:62830:24) at Object.<anonymous> (builders/aggregate-migration-scripts/index.it.spec.ts:63:48)
ng add testing › should add testing to an application: packages/@o3r/test-helpers/src/utilities/package-manager.ts#L102
Command failed: npm exec ng add @o3r/testing@~999 -- --skip-confirmation --project-name test-app STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_54_560Z-debug-0.log OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_54_560Z-debug-0.log at execCmd (../test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (../test-helpers/src/utilities/package-manager.ts:163:10) at Object.<anonymous> (schematics/index.it.spec.ts:24:23)
ng add testing › should add testing to an application and fixture to component: packages/@o3r/test-helpers/src/utilities/package-manager.ts#L102
Command failed: npm exec ng add @o3r/testing@~999 -- --skip-confirmation --project-name test-app STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_56_919Z-debug-0.log OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_56_919Z-debug-0.log at execCmd (../test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (../test-helpers/src/utilities/package-manager.ts:163:10) at Object.<anonymous> (schematics/index.it.spec.ts:45:23)
ng add otter localization › should add localization to an application: packages/@o3r/localization/schematics/index.it.spec.ts#L23
expect(received).not.toThrow() Error name: "Error" Error message: "Command failed: npm exec ng add @o3r/localization@~999 -- --skip-confirmation --project-name test-app STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_57_291Z-debug-0.log· OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_57_291Z-debug-0.log " 100 | // Yarn doesn't log errors on stderr, so we need to get them from stdout to have them in the reports 101 | // eslint-disable-next-line @typescript-eslint/restrict-template-expressions > 102 | throw new Error(`Command failed: ${args.join(' ') }\nSTDERR:\n${err.stderr?.toString() || ''}\nOUTPUT:\n${err.output?.toString() || ''}`); | ^ 103 | } 104 | } 105 | at execCmd (packages/@o3r/test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (packages/@o3r/test-helpers/src/utilities/package-manager.ts:163:10) at packages/@o3r/localization/schematics/index.it.spec.ts:23:36 at Object.<anonymous> (.yarn/cache/expect-npm-29.7.0-62e9f7979e-63f97bc51f.zip/node_modules/expect/build/toThrowMatchers.js:74:11) at Object.throwingMatcher [as toThrow] (.yarn/cache/expect-npm-29.7.0-62e9f7979e-63f97bc51f.zip/node_modules/expect/build/index.js:320:21) at Object.<anonymous> (packages/@o3r/localization/schematics/index.it.spec.ts:23:174) at Object.<anonymous> (schematics/index.it.spec.ts:23:174)
ng add otter localization › should add localization to a library: packages/@o3r/localization/schematics/index.it.spec.ts#L48
expect(received).not.toThrow() Error name: "Error" Error message: "Command failed: npm exec ng add @o3r/localization@~999 -- --skip-confirmation --project-name test-lib STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_58_876Z-debug-0.log· OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_58_876Z-debug-0.log " 100 | // Yarn doesn't log errors on stderr, so we need to get them from stdout to have them in the reports 101 | // eslint-disable-next-line @typescript-eslint/restrict-template-expressions > 102 | throw new Error(`Command failed: ${args.join(' ') }\nSTDERR:\n${err.stderr?.toString() || ''}\nOUTPUT:\n${err.output?.toString() || ''}`); | ^ 103 | } 104 | } 105 | at execCmd (packages/@o3r/test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (packages/@o3r/test-helpers/src/utilities/package-manager.ts:163:10) at packages/@o3r/localization/schematics/index.it.spec.ts:48:36 at Object.<anonymous> (.yarn/cache/expect-npm-29.7.0-62e9f7979e-63f97bc51f.zip/node_modules/expect/build/toThrowMatchers.js:74:11) at Object.throwingMatcher [as toThrow] (.yarn/cache/expect-npm-29.7.0-62e9f7979e-63f97bc51f.zip/node_modules/expect/build/index.js:320:21) at Object.<anonymous> (packages/@o3r/localization/schematics/index.it.spec.ts:48:174) at Object.<anonymous> (schematics/index.it.spec.ts:48:174)
check metadata migration › should not throw: packages/@o3r/test-helpers/src/utilities/package-manager.ts#L102
Command failed: npm exec ng add @o3r/extractors@~999 -- --skip-confirmation --project-name test-app STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_57_218Z-debug-0.log OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_57_218Z-debug-0.log at execCmd (../test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (../test-helpers/src/utilities/package-manager.ts:163:10) at initTest (builders/metadata-check/index.it.spec.ts:78:21) at Object.<anonymous> (builders/metadata-check/index.it.spec.ts:148:11)
check metadata migration › should throw because no migration data: packages/@o3r/test-helpers/src/utilities/package-manager.ts#L102
Command failed: npm exec ng add @o3r/extractors@~999 -- --skip-confirmation --project-name test-app STDERR: npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_58_881Z-debug-0.log OUTPUT: ,,npm error could not determine executable to run npm error A complete log of this run can be found in: /home/runner/work/otter/otter/.cache/test-app/npm-cache/_logs/2024-08-23T08_58_58_881Z-debug-0.log at execCmd (../test-helpers/src/utilities/package-manager.ts:102:11) at packageManagerExec (../test-helpers/src/utilities/package-manager.ts:163:10) at initTest (builders/metadata-check/index.it.spec.ts:78:21) at Object.<anonymous> (builders/metadata-check/index.it.spec.ts:161:11)
Create new otter project command › should generate a project with an application: packages/@o3r/create/src/index.it.spec.ts#L36
expect(received).not.toThrow() Error name: "Error" Error message: "Command failed: npm create @o3r@~999 my-project -- --package-manager npm --skip-confirmation --yarn-version 4.4.0 STDERR: - Installing packages (npm)... ✔ Packages installed successfully. npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: [email protected] npm error Found: @angular-devkit/[email protected] npm error node_modules/@angular-devkit/schematics npm error dev @angular-devkit/schematics@\"~18.1.0\" from the root project npm error npm error Could not resolve dependency: npm error peer @angular-devkit/schematics@\"~18.2.0\" from @o3r/[email protected] npm error node_modules/@o3r/schematics npm error dev @o3r/schematics@\"^999.0.1724001595271\" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error D:\\a\\otter\\otter\\.cache\\test-app\\npm-cache\\_logs\\2024-08-23T09_05_22_964Z-eresolve-report.txt npm error A complete log of this run can be found in: D:\\a\\otter\\otter\\.cache\\test-app\\npm-cache\\_logs\\2024-08-23T09_05_22_964Z-debug-0.log npm error code 6 npm error path D:\\a\\otter\\it-tests\\test-create-app npm error command failed npm error command C:\\Windows\\system32\\cmd.exe /d /s /c create my-project --package-manager npm --skip-confirmation --yarn-version 4.4.0 npm error A complete log of this run can be found in: D:\\a\\otter\\otter\\.cache\\test-app\\npm-cache\\_logs\\2024-08-23T09_05_08_800Z-debug-0.log· OUTPUT: , > npx > create my-project --package-manager npm --skip-confirmation --yarn-version 4.4.0··· &BPPPB & &BPGB& #Y7!!!!!J# &#BGP5YYJJ??????????JJYY5PG#& P7!!!!7JG #!!!!!!!!!7Y5J?7!!!!!!!!!!!!!!!!!!!!!!!!!!!7?JPB5!!!!!!!!!G #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!~5 BJ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!?5 &?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!7B G?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!75& #J!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!?B P7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Y& &Y!!!!!!!!!!!!7??!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!777!!!!!!!!!!!!!?# &?!!!!!!!!!!!!J&J&#7!!!!!!!!7?Y5PPPP55J7!!!!!!!!!5B?&P!!!!!!!!!!!!!7B &?!!!!!!!!!!!!!?B##P!!!!!!!!!5 &?!!!!!!!!Y&&&P!!!!!!!!!!!!!!!B J!!!!!!!!J7!!!!!!7!!!!!!!!!!!7YB& BY!!!!!!!!!!777!!!!!!!?7!!!!!!!7# P!!!!!!!!YB!!!!!!!!!!!!!!!!!!!!!!7JY5YJ?!!!!!!!!!!!!!!!!!!!!!!YG!!!!!!!!J &7!!!!!!!!GG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!J&7!!!!!!!!B B!!!!!!!!!Y&7!!!!!!!!!!!!!!!!!!77JY5PPP5YJ?7!!!!!!!!!!!!!!!!!!!BG!!!!!!!!!Y B!!!!!!!!!!P#Y7!!!!!!!!!!!!7JY5P5YJ????JJY5PP5J?!!!!!!!!!!!!!JBG7!!!!!!!!!J B!!!!!!!!!!!?PG5J?7777?JY5PPYJ7!!!!!!!!!!!!!7J5PPPYJ?77!77?5GBY!!!!!!!!!!!5 J!!!!!!!!!!!!7JY555555YJ?7!!!!!!!!!!!!!!!!!!!!!7?JY5555555Y?!!!!!!!!!!!!!# #?!!!!!!!!!!!!!!!!!!!!!!!!!!!!7JYJJJ?JJJYY?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!P &J!!!!!!!!!!!!!!!!!!!!!!!!!!!!7?JYYYYJ??7!!!!!!!!!!!!!!!!!!!!!!!!!!!!7G G?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!75& BY?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!7JG& #PYJ?7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!77?YPB& &BPPB &Y7JYYYJ7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!7?YYYJ??B #?!!!!?P B7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!5 Y!!!!!!!?B P!!!!!!!!7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Create new otter project command › should generate a project with a library: packages/@o3r/create/src/index.it.spec.ts#L60
expect(received).not.toThrow() Error name: "Error" Error message: "Command failed: npm create @o3r@~999 my-project -- --package-manager npm --skip-confirmation --yarn-version 4.4.0 STDERR: - Installing packages (npm)... ✔ Packages installed successfully. npm error code ERESOLVE npm error ERESOLVE unable to resolve dependency tree npm error npm error While resolving: [email protected] npm error Found: @angular-devkit/[email protected] npm error node_modules/@angular-devkit/schematics npm error dev @angular-devkit/schematics@\"~18.1.0\" from the root project npm error npm error Could not resolve dependency: npm error peer @angular-devkit/schematics@\"~18.2.0\" from @o3r/[email protected] npm error node_modules/@o3r/schematics npm error dev @o3r/schematics@\"^999.0.1724001595271\" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error D:\\a\\otter\\otter\\.cache\\test-app\\npm-cache\\_logs\\2024-08-23T09_05_47_648Z-eresolve-report.txt npm error A complete log of this run can be found in: D:\\a\\otter\\otter\\.cache\\test-app\\npm-cache\\_logs\\2024-08-23T09_05_47_648Z-debug-0.log npm error code 6 npm error path D:\\a\\otter\\it-tests\\test-create-app1 npm error command failed npm error command C:\\Windows\\system32\\cmd.exe /d /s /c create my-project --package-manager npm --skip-confirmation --yarn-version 4.4.0 npm error A complete log of this run can be found in: D:\\a\\otter\\otter\\.cache\\test-app\\npm-cache\\_logs\\2024-08-23T09_05_28_169Z-debug-0.log· OUTPUT: , > npx > create my-project --package-manager npm --skip-confirmation --yarn-version 4.4.0··· &BPPPB & &BPGB& #Y7!!!!!J# &#BGP5YYJJ??????????JJYY5PG#& P7!!!!7JG #!!!!!!!!!7Y5J?7!!!!!!!!!!!!!!!!!!!!!!!!!!!7?JPB5!!!!!!!!!G #!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!~5 BJ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!?5 &?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!7B G?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!75& #J!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!?B P7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Y& &Y!!!!!!!!!!!!7??!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!777!!!!!!!!!!!!!?# &?!!!!!!!!!!!!J&J&#7!!!!!!!!7?Y5PPPP55J7!!!!!!!!!5B?&P!!!!!!!!!!!!!7B &?!!!!!!!!!!!!!?B##P!!!!!!!!!5 &?!!!!!!!!Y&&&P!!!!!!!!!!!!!!!B J!!!!!!!!J7!!!!!!7!!!!!!!!!!!7YB& BY!!!!!!!!!!777!!!!!!!?7!!!!!!!7# P!!!!!!!!YB!!!!!!!!!!!!!!!!!!!!!!7JY5YJ?!!!!!!!!!!!!!!!!!!!!!!YG!!!!!!!!J &7!!!!!!!!GG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!J&7!!!!!!!!B B!!!!!!!!!Y&7!!!!!!!!!!!!!!!!!!77JY5PPP5YJ?7!!!!!!!!!!!!!!!!!!!BG!!!!!!!!!Y B!!!!!!!!!!P#Y7!!!!!!!!!!!!7JY5P5YJ????JJY5PP5J?!!!!!!!!!!!!!JBG7!!!!!!!!!J B!!!!!!!!!!!?PG5J?7777?JY5PPYJ7!!!!!!!!!!!!!7J5PPPYJ?77!77?5GBY!!!!!!!!!!!5 J!!!!!!!!!!!!7JY555555YJ?7!!!!!!!!!!!!!!!!!!!!!7?JY5555555Y?!!!!!!!!!!!!!# #?!!!!!!!!!!!!!!!!!!!!!!!!!!!!7JYJJJ?JJJYY?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!P &J!!!!!!!!!!!!!!!!!!!!!!!!!!!!7?JYYYYJ??7!!!!!!!!!!!!!!!!!!!!!!!!!!!!7G G?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!75& BY?!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!7JG& #PYJ?7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!77?YPB& &BPPB &Y7JYYYJ7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!7?YYYJ??B #?!!!!?P B7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!5 Y!!!!!!!?B P!!!!!!!!7!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
it-tests / it-tests (windows-latest, npm, o3r-project-with-app)
Process completed with exit code 1.
new otter application with apis-manager ► new otter application with apis-manager should add apis-manager to existing application ► new otter application with apis-manager should add apis-manager to existing application: @o3r/apis-manager/dist-test/it-report.xml#L0
Failed test found in: @o3r/apis-manager/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/apis-manager@~999 -- --skip-confirmation --project-name test-app
new Angular application ► new Angular application should add Otter Application to existing Angular app ► new Angular application should add Otter Application to existing Angular app: @o3r/application/dist-test/it-report.xml#L0
Failed test found in: @o3r/application/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/application@~999 -- --project-name test-app --skip-confirmation
check metadata migration ► check metadata migration should not throw ► check metadata migration should not throw: @o3r/components/dist-test/it-report.xml#L0
Failed test found in: @o3r/components/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/extractors@~999 -- --skip-confirmation --project-name test-app
check metadata migration ► check metadata migration should throw because no migration data ► check metadata migration should throw because no migration data: @o3r/components/dist-test/it-report.xml#L0
Failed test found in: @o3r/components/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/extractors@~999 -- --skip-confirmation --project-name test-app
check metadata migration ► check metadata migration should throw because migration data invalid ► check metadata migration should throw because migration data invalid: @o3r/components/dist-test/it-report.xml#L0
Failed test found in: @o3r/components/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/extractors@~999 -- --skip-confirmation --project-name test-app
check metadata migration ► check metadata migration should throw because breaking changes are not allowed ► check metadata migration should throw because breaking changes are not allowed: @o3r/components/dist-test/it-report.xml#L0
Failed test found in: @o3r/components/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/extractors@~999 -- --skip-confirmation --project-name test-app
new otter application with configuration ► new otter application with configuration should add configuration to an application ► new otter application with configuration should add configuration to an application: @o3r/configuration/dist-test/it-report.xml#L0
Failed test found in: @o3r/configuration/dist-test/it-report.xml Error: Error: Command failed: npm exec ng add @o3r/configuration@~999 -- --skip-confirmation --project-name test-app
checks / test (ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
checks / test (windows-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
it-tests / it-tests (ubuntu-latest, npm, o3r-project-with-app)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
it-tests / it-tests (windows-latest, npm, o3r-project-with-app)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
it-tests / it-tests (ubuntu-latest, yarn, o3r-project-with-app)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
it-tests / it-tests (windows-latest, yarn, o3r-project-with-app)
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
it-tests / it-tests (windows-latest, yarn, o3r-project-with-app)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@a8a3f3ad30e3422c9c7b888a15615d19a852ae32. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "it-reports-ubuntu-latest-npm", "it-reports-ubuntu-latest-yarn", "it-reports-windows-latest-npm", "it-reports-windows-latest-yarn", "ut-reports-ubuntu-latest", "ut-reports-windows-latest". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
dist Expired
35.1 MB
documentation Expired
84.2 MB
it-reports-ubuntu-latest-npm Expired
168 KB
it-reports-ubuntu-latest-yarn Expired
16.7 KB
it-reports-windows-latest-npm Expired
24.8 KB
it-reports-windows-latest-yarn Expired
16.7 KB
it-tests-ubuntu-latest-npm Expired
563 MB
it-tests-windows-latest-npm Expired
1.33 MB
ut-reports-ubuntu-latest Expired
334 KB
ut-reports-windows-latest Expired
334 KB
verdaccio Expired
14.8 MB