starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[PR #10267] [CLOSED] Run Helix tests on PR as we keep missing failures #27975

New Issue
Open
opened 2026-01-31 09:25:29 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:25:29 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/10267
Author: @miniksa
Created: 5/28/2021
Status: ❌ Closed

Base: main ← Head: dev/miniksa/helix-on-pr

📝 Commits (2)

  • 0ed2d34 Temporarily suspend rolling build. Move helix testing to PR build since they keep silently breaking.
  • 0264839 Merge remote-tracking branch 'origin/main' into dev/miniksa/helix-on-pr

📊 Changes

1 file changed (+12 additions, -13 deletions)

View changed files

📝 build/pipelines/ci.yml (+12 -13)

📄 Description

Run Helix tests on PR as we keep missing failures

References

  • Cannot be completed until after #10266 is fixed.

PR Checklist

  • Closes outstanding problem with unnoticed failed builds on mainline commits.
  • I worked here
  • If this PR build passes and has the Helix test line, it's good to go.
  • I've discussed this with @DHowett and @zadjii-msft in Teams already.

Detailed Description of the Pull Request / Additional comments

  • I have tried multiple times to get the rolling builds to email on failure. It's not worked
  • When we set the policy of not running Helix tests on PR... we had significantly lower horsepower machines and a smaller pool and turn around times were terrible. Now there is more space and capacity.
  • When this policy was set, we had fewer tests that had to run in Helix and several other testing limitations. These are gone now with updated OS builds on the test machines.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/10267 **Author:** [@miniksa](https://github.com/miniksa) **Created:** 5/28/2021 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dev/miniksa/helix-on-pr` --- ### 📝 Commits (2) - [`0ed2d34`](https://github.com/microsoft/terminal/commit/0ed2d3436874aba64a2bf4d47038de34b21bf707) Temporarily suspend rolling build. Move helix testing to PR build since they keep silently breaking. - [`0264839`](https://github.com/microsoft/terminal/commit/02648398f7f4a6ae85e634660c2655ba14b2275f) Merge remote-tracking branch 'origin/main' into dev/miniksa/helix-on-pr ### 📊 Changes **1 file changed** (+12 additions, -13 deletions) <details> <summary>View changed files</summary> 📝 `build/pipelines/ci.yml` (+12 -13) </details> ### 📄 Description Run Helix tests on PR as we keep missing failures ## References - Cannot be completed until after #10266 is fixed. ## PR Checklist * [x] Closes outstanding problem with unnoticed failed builds on mainline commits. * [x] I worked here * [ ] If this PR build passes and has the Helix test line, it's good to go. * [x] I've discussed this with @DHowett and @zadjii-msft in Teams already. ## Detailed Description of the Pull Request / Additional comments - I have tried multiple times to get the rolling builds to email on failure. It's not worked - When we set the policy of not running Helix tests on PR... we had significantly lower horsepower machines and a smaller pool and turn around times were terrible. Now there is more space and capacity. - When this policy was set, we had fewer tests that had to run in Helix and several other testing limitations. These are gone now with updated OS builds on the test machines. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:25:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#27975
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?