Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DAOS-16872 cq: Bump GHA versions #15693

Draft
wants to merge 1 commit into
base: release/2.6
Choose a base branch
from

Conversation

daltonbohning
Copy link
Contributor

Run-GHA: true
Test-tag: always_passes

Required-githooks: true

Before requesting gatekeeper:

  • Two review approvals and any prior change requests have been resolved.
  • Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
  • Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
  • Commit messages follows the guidelines outlined here.
  • Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

  • You are the appropriate gatekeeper to be landing the patch.
  • The PR has 2 reviews by people familiar with the code, including appropriate owners.
  • Githooks were used. If not, request that user install them and check copyright dates.
  • Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
  • All builds have passed. Check non-required builds for any new compiler warnings.
  • Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
  • If applicable, the PR has addressed any potential version compatibility issues.
  • Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
  • Extra checks if forced landing is requested
    • Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
    • No new NLT or valgrind warnings. Check the classic view.
    • Quick-build or Quick-functional is not used.
  • Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

- Bump github/codeql-action from 3.24.9 to 3.27.7 (#15589)
- Bump github/codeql-action from 3.27.7 to 3.27.9 (#15618)
- Bump github/codeql-action from 3.27.9 to 3.28.0 (#15662)
- Bump thollander/actions-comment-pull-request from 2 to 3 (#15590)
- Bump aquasecurity/trivy-action from 0.28.0 to 0.29.0 (#15591)
- Bump codespell-project/actions-codespell to latest (#15592)
- Bump EnricoMi/publish-unit-test-result-action from 1.17 to 2.7 (#15593)
- Bump EnricoMi/publish-unit-test-result-action from 2.7.0 to 2.18.0 (#15660)
- Bump isort/isort-action from 1.1.0 to 1.1.1 (#15594)
- Bump phoenix-actions/test-reporting from 10 to 15 (#15617)
- Bump actions/setup-python from 5.1.0 to 5.3.0 (#15661)

Run-GHA: true
Test-tag: always_passes

Required-githooks: true

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: Dalton Bohning <[email protected]>
@daltonbohning daltonbohning added the unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving. label Jan 7, 2025
@daltonbohning daltonbohning self-assigned this Jan 7, 2025
Copy link

github-actions bot commented Jan 7, 2025

Ticket title is 'Dependabot GHA updates 2024-12-11'
Status is 'Awaiting backport'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-16872

@github-actions github-actions bot added the priority Ticket has high priority (automatically managed) label Jan 7, 2025
- uses: isort/isort-action@f14e57e1d457956c45a19c05a89cccdf087846e5 # v1.1.0
- name: Install extra python packages
run: python3 -m pip install --requirement utils/cq/requirements.txt
- name: Run isort

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 2: pipCommand not pinned by hash
Click Remediation section below to solve this issue
Copy link

github-actions bot commented Jan 7, 2025

Functional on EL 8.8 Test Results

 3 tests   3 ✅  28s ⏱️
11 suites  0 💤
11 files    0 ❌

Results for commit 7cfd60d.

Copy link

github-actions bot commented Jan 7, 2025

Functional Hardware Medium Test Results

28 tests   28 ✅  19s ⏱️
 7 suites   0 💤
 7 files     0 ❌

Results for commit 7cfd60d.

Copy link

github-actions bot commented Jan 7, 2025

Functional Hardware Medium Verbs Provider Test Results

28 tests   28 ✅  18s ⏱️
 7 suites   0 💤
 7 files     0 ❌

Results for commit 7cfd60d.

Copy link

github-actions bot commented Jan 7, 2025

Functional Hardware Large Test Results

52 tests   52 ✅  20s ⏱️
11 suites   0 💤
11 files     0 ❌

Results for commit 7cfd60d.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority Ticket has high priority (automatically managed) unclean-cherry-pick Indicates that a cherry-pick had merge conflicts that needed resolving.
Development

Successfully merging this pull request may close these issues.

1 participant