Skip to content

PGO not working due to Y2K22 bug #12261

Closed
@miniksa

Description

@miniksa

When the new year rolled over, the PGO Nuget no longer worked.

This is because NuGet.exe uses a SIGNED 32bit integer to represent version information.

However, this system was building the version number out of today's date and time.

When we hit 2022... we ended up with something that was over 21billion and therefore outside the limits of a 32 bit signed integer.

The solution is to move the version information with the date into the freeform text portion of the version (the prerelease field of Nuget packages) and set the previous one to a fixed number (and update our detection scripts to compensate for which package is the newest)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-BuildIssues pertaining to the build system, CI, infrastructure, metaIssue-BugIt either shouldn't be doing this or needs an investigation.Product-MetaThe product is the management of the products.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions