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

Upgrade rust to 1.85.0 #11443

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

KavyaSree2610
Copy link
Contributor

@KavyaSree2610 KavyaSree2610 commented Dec 13, 2024

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 (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/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?

  • Upgrade rust to 1.85.0
Change Log
  • Upgrade to 1.85.0
  • Drop unnecessary patches
  • Remove expand-yaml-anchors tool in %check
  • Remove and skip some failing ptests
Does this affect the toolchain?

NO

Associated issues
Links to CVEs
Test Methodology
  • Pipeline build:

@KavyaSree2610 KavyaSree2610 changed the base branch from 2.0 to main December 19, 2024 07:01
@microsoft-github-policy-service microsoft-github-policy-service bot added the main PR Destined for main label Dec 19, 2024
@KavyaSree2610 KavyaSree2610 changed the title Upgrade rust Upgrade rust to 1.83.0 Dec 19, 2024
@KavyaSree2610 KavyaSree2610 marked this pull request as ready for review December 20, 2024 04:59
@KavyaSree2610 KavyaSree2610 requested a review from a team as a code owner December 20, 2024 04:59
@KavyaSree2610 KavyaSree2610 force-pushed the kkaitepalli/upgrade-rust-2.0 branch from 703b56e to 700c956 Compare February 28, 2025 07:11
@KavyaSree2610 KavyaSree2610 changed the title Upgrade rust to 1.83.0 Upgrade rust to 1.85.0 Feb 28, 2025
@@ -114,6 +118,7 @@ export CXXFLAGS="`echo " %{build_cxxflags} " | sed 's/ -g//'`"
sh ./configure \
Copy link
Collaborator

Choose a reason for hiding this comment

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

in the BuildRequires: above can we take an explicit dependency on the libz and in the vendor tarball generation for this can we explicitly remove any vendored source for zlib. We want to make sure that rust takes a dependency on the system zlib and not the internally vendored one. I believe this is already working implicitly, goal is to make it explicit
Bug 44559508: [2.0][3.0] [Rust] Remove vendored system libs from uploaded source tarball

@Stevenjin8
Copy link

@jslobodzian @KavyaSree2610 is there anything I can do to help move this forward?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
main PR Destined for main Packaging
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants