Skip to content

Devise a scheme for managing WARP versions #340

@V-FEXrt

Description

@V-FEXrt

The team recently has encountered test issues with varied WARP versions. Using System Version seems to be the wrong approach.

Offline discussions have mostly landed on the following proposal that needs to be finalized and staffed.

  • Have a periodic cron job that runs with the latest version of warp to highlight incoming breakages
  • Have a periodic cron job that runs with the last known good version of warp to ensure LKG stays good
  • Have premerge tests run against LKG to minimize infra breakages for incoming PRs
  • Use a cmake script to set/enforce LKG version for local development

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Active

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions