Remove Tiger SDK jobs + reenable Windows CI #5095
Conversation
LoopedBard3
changed the title
There was a problem hiding this comment.
Pull request overview
This PR claims to "Remove the Tiger SDK jobs (Windows and Ubuntu) as we have gotten a bit of overlap with the Viper machines," but the actual code changes contradict this description. The changes primarily enable Tiger SDK jobs in the public jobs section by uncommenting previously disabled machine configurations, while also cleaning up commented-out Tiger SDK references in the private jobs section where Viper machine equivalents already exist.
Changes:
- Uncommented/enabled multiple Tiger SDK job configurations (
win-x64,win-x86,ubuntu-x64) in the public jobs section - Removed commented-out Tiger SDK references from private jobs section where Viper machines are already configured
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| jobTemplate: /eng/pipelines/templates/run-scenarios-job.yml | ||
| buildMachines: | ||
| #- win-x64 | ||
| - win-x64 |
There was a problem hiding this comment.
The PR description states "Remove the Tiger SDK jobs" but this change actually enables/uncomments the win-x64 job. This appears to be re-enabling Tiger SDK jobs rather than removing them. Please verify if the PR description is accurate or if the code changes need to be revised.
LoopedBard3
changed the title
LoopedBard3
changed the title
|
Almost all failures are related to net10.0, will remove net10.0 builds in another PR shortly at which point we can more easily fix any other errors. Looking at the non-net10 micro windows error the run ran successfully and it was an issue with the send to helix connection. Merging. |
2 participants
Remove the Tiger SDK jobs (Windows and Ubuntu) as we have gotten a bit of overlap with the Viper machines. Also reenable previously disabled Windows CI jobs.