Skip to content

fix: iterator is not pointer #270

fix: iterator is not pointer

fix: iterator is not pointer #270

Triggered via pull request January 15, 2025 02:48
Status Success
Total duration 16m 8s
Artifacts

check.yml

on: pull_request
Check clang-format
39s
Check clang-format
Matrix: Build and test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
Build and test (clang)
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Build and test (gcc)
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Check clang-format
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636
Build and test (clang)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636
Build and test (clang)
Unable to validate code scanning workflow: error: getWorkflow() failed: Error: Expected to find a code scanning workflow file at /__w/fcitx5/fcitx5/.github/workflows/check.yml, but no such file existed. This can happen if the currently running workflow checks out a branch that doesn't contain the corresponding workflow file.
Build and test (gcc)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see /~https://github.com/actions/runner-images/issues/10636
Build and test (gcc)
Unable to validate code scanning workflow: error: getWorkflow() failed: Error: Expected to find a code scanning workflow file at /__w/fcitx5/fcitx5/.github/workflows/check.yml, but no such file existed. This can happen if the currently running workflow checks out a branch that doesn't contain the corresponding workflow file.