You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Route auxiliary Copilot jobs to self-hosted Linux and make existing native Linux/macOS/Windows routes explicit. Preserve their platform coverage and native toolchains; only Docker workloads require Apple Silicon. Keep the legacy inactive stale workflow inactive.
This is repository CI maintenance requested by the maintainer. Use the installed chore workflow and its Action-managed branch. No application feature, public API, release or deployment is requested.
Current issues or inefficiencies
Some generated auxiliary workflows still select GitHub-hosted Ubuntu even though the repository is configured for the shared self-hosted runner pool. Broad platform selectors may place native jobs on incompatible machines. Docker is available on Apple Silicon, but not on the Linux/Windows VMs or old Intel Mac.
Expected impact
All repository workflows select reviewed self-hosted Linux, macOS or Windows runners according to their dependencies. Preserve tests and required check names. Validate YAML/actionlint and actual affected CI; merge only after all applicable checks pass and a complete review has no unresolved findings. No new unit tests are needed for selector-only configuration changes.
Alternatives considered
GitHub-hosted runners are outside the maintainer's requested routing. Installing Docker on the VMs or old Mac is unavailable. Preserve existing native architecture coverage where required.
Additional context or comments
Installed Copilot: 3.10.2, consumed through @V3. Scope is runner placement and directly required environment compatibility. Preserve consumer setup actions and existing application/deployment behavior.
changed the title [-]Align repository workflows with shared self-hosted runners[/-][+]🔧 - Align repository workflows with shared self hosted runners[/+]on Oct 23, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try /copilot help to see the available commands, or mention @vypbot with your question.
He encontrado un segundo problema real en los runners ARM64 compartidos al validar #159: los emuladores de dos jobs usan un Netsim común aunque el SDK y el AVD sean privados. El primer job terminó sus tests y el runner limpió su proceso netsimd a las19:10:52Z; el otro emulador37.2.12 perdió la conexión Wi-Fi y abortó a las19:10:54Z en grpc::internal::CallbackWithSuccessTag, confirmado por el crash report nativo de macOS. Después falló la siguiente instalación por device-not-found.
#159 añade una mitigación limitada al entorno CI: ANDROID_EMULATOR_FEATURES=-WiFiPacketStream. Conserva la ruta Wi-Fi anterior y todas las pruebas; no cambia el emulador global, los listeners ni los timeouts. Se validará con ambos casos de integración Android sobre el nuevo head antes de mergear.
Completed on master and develop through #156, #157, #158, #159 and #160. All workflow selectors use the reviewed vypdev self-hosted Linux/macOS/Windows pool, and both Copilot PR lanes are isolated by PR number. Copilot consumes the published 3.10.3 through @v3.
#159 passed 36 applicable checks and #160 passed all 42 applicable checks; both native reviews were complete with zero unresolved findings. The complete develop matrix passed, including modern/legacy Android examples with workspace/pub-cache native sources, iOS/macOS SwiftPM and CocoaPods, Linux, Windows, web, CLI and publication dry runs. No Android test retry was needed in #160.
Develop now contains ba72a2e9866b03a323b136d0f073bd74f47e7d1f, whose tree exactly matches the tested merge preview (61a8be1e). Only four CI files changed from the preceding develop; pending application work and the existing credential-health workflow were preserved. The shared Android preparation avoids the observed Netsim Wi-Fi abort; Windows retains failure-only native diagnostics without masking the original failure.
Activity
[-]Align repository workflows with shared self-hosted runners[/-][+]🔧 - Align repository workflows with shared self hosted runners[/+]vypbot commentedon Oct 23, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.vypbot commentedon Oct 24, 2026
Issue closed: synchronization recommendation retired
No branch synchronization is required for this closed issue.
The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.
efraespada commentedon Oct 24, 2026
He encontrado un segundo problema real en los runners ARM64 compartidos al validar #159: los emuladores de dos jobs usan un Netsim común aunque el SDK y el AVD sean privados. El primer job terminó sus tests y el runner limpió su proceso netsimd a las19:10:52Z; el otro emulador37.2.12 perdió la conexión Wi-Fi y abortó a las19:10:54Z en grpc::internal::CallbackWithSuccessTag, confirmado por el crash report nativo de macOS. Después falló la siguiente instalación por device-not-found.
Evidencia: job que limpió Netsim https://github.com/vypdev/zstandard/actions/runs/40122433112/job/120956695449 y job afectado https://github.com/vypdev/zstandard/actions/runs/40122433112/job/120956695431 .
#159 añade una mitigación limitada al entorno CI: ANDROID_EMULATOR_FEATURES=-WiFiPacketStream. Conserva la ruta Wi-Fi anterior y todas las pruebas; no cambia el emulador global, los listeners ni los timeouts. Se validará con ambos casos de integración Android sobre el nuevo head antes de mergear.
vypbot commentedon Oct 24, 2026
Issue closed: synchronization recommendation retired
No branch synchronization is required for this closed issue.
The previous recommendation is historical. Issue closure does not certify that the branches are synchronized.
efraespada commentedon Oct 24, 2026
Completed on master and develop through #156, #157, #158, #159 and #160. All workflow selectors use the reviewed vypdev self-hosted Linux/macOS/Windows pool, and both Copilot PR lanes are isolated by PR number. Copilot consumes the published 3.10.3 through
@v3.#159 passed 36 applicable checks and #160 passed all 42 applicable checks; both native reviews were complete with zero unresolved findings. The complete develop matrix passed, including modern/legacy Android examples with workspace/pub-cache native sources, iOS/macOS SwiftPM and CocoaPods, Linux, Windows, web, CLI and publication dry runs. No Android test retry was needed in #160.
Develop now contains
ba72a2e9866b03a323b136d0f073bd74f47e7d1f, whose tree exactly matches the tested merge preview (61a8be1e). Only four CI files changed from the preceding develop; pending application work and the existing credential-health workflow were preserved. The shared Android preparation avoids the observed Netsim Wi-Fi abort; Windows retains failure-only native diagnostics without masking the original failure.