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

perftest: Upgrade to 24.01.0 version #8674

Merged
merged 2 commits into from
Apr 3, 2024
Merged

Conversation

jcamposeco
Copy link
Contributor

@jcamposeco jcamposeco commented Apr 2, 2024

Upgrade perftest to 24.01.0

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
  • Update src package
Does this affect the toolchain?

NO

Associated issues

NA

Links to CVEs
Test Methodology

@jcamposeco jcamposeco marked this pull request as ready for review April 3, 2024 01:12
@jcamposeco jcamposeco requested a review from a team as a code owner April 3, 2024 01:12
@@ -36,8 +35,12 @@ chmod -x runme
%doc README runme
%license COPYING
%_bindir/*
%_mandir/man1/*.1*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be marked %doc as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think is only related to documentation. From what I found in Azure Linux repo, %doc is not used for manfiles, they are placed in the %files section only.
I will try to find any official documentation on this though.

@jcamposeco jcamposeco requested a review from anphel31 April 3, 2024 01:41
@jcamposeco jcamposeco merged commit e627cbb into 3.0-dev Apr 3, 2024
14 checks passed
@jcamposeco jcamposeco deleted the juan/update_perftest branch April 3, 2024 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants