Skip to content

Fixes #4001 - Migrate Core Profile TCK runners to use new managed Piranha container #4164

Fixes #4001 - Migrate Core Profile TCK runners to use new managed Piranha container

Fixes #4001 - Migrate Core Profile TCK runners to use new managed Piranha container #4164

Triggered via pull request September 21, 2024 19:31
Status Success
Total duration 10m 46s
Artifacts

build.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (21, ubuntu-latest)
This action is running on a pull_request event for a fork repository. It cannot do anything useful like creating check runs or pull request comments. To run the action on fork repository pull requests, see https://github.com/EnricoMi/publish-unit-test-result-action/blob/v1.20/README.md#support-fork-repositories-and-dependabot-branches
build (22, ubuntu-latest)
This action is running on a pull_request event for a fork repository. It cannot do anything useful like creating check runs or pull request comments. To run the action on fork repository pull requests, see https://github.com/EnricoMi/publish-unit-test-result-action/blob/v1.20/README.md#support-fork-repositories-and-dependabot-branches
codeql
The following actions use a deprecated Node.js version and will be forced to run on node20: github/codeql-action/init@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
codeql
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/