Use the right dataconnect directory every time #31706
joehannode-test.yml
on: push
Matrix: unit
Matrix: check-json-schema
Matrix: check-package-lock-vsce
Matrix: check-package-lock
Matrix: lint
Matrix: vscode_integration
Matrix: vscode_unit
Matrix: integration-windows
Matrix: integration
Annotations
12 errors and 9 warnings
|
unit (20)
Canceling since a higher priority waiting request for 'CI Tests-push-jh-init-datadir' exists
|
|
unit (20)
The operation was canceled.
|
|
unit (18)
Canceling since a higher priority waiting request for 'CI Tests-push-jh-init-datadir' exists
|
|
unit (18)
The operation was canceled.
|
|
vscode_integration (18)
Canceling since a higher priority waiting request for 'CI Tests-push-jh-init-datadir' exists
|
|
vscode_integration (18)
The operation was canceled.
|
|
vscode_unit (18)
Canceling since a higher priority waiting request for 'CI Tests-push-jh-init-datadir' exists
|
|
vscode_unit (18)
The operation was canceled.
|
|
vscode_integration (20)
Canceling since a higher priority waiting request for 'CI Tests-push-jh-init-datadir' exists
|
|
vscode_integration (20)
The operation was canceled.
|
|
vscode_unit (20)
Canceling since a higher priority waiting request for 'CI Tests-push-jh-init-datadir' exists
|
|
vscode_unit (20)
The operation was canceled.
|
|
check-package-lock-vsce (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
check-package-lock (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
check-json-schema (20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
vscode_integration (18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
vscode_integration (18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
vscode_integration (18)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
vscode_integration (20)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
vscode_integration (20)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
vscode_integration (20)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|