aglinxinyuan opened a new issue, #6503: URL: https://github.com/apache/texera/issues/6503
## Motivation #6487 was a Windows-only regression that CI could not catch: the hadoop-common bumps #6201 (3.3.1 → 3.4.3) and #6227 (→ 3.5.0) made every local Iceberg write require `winutils.exe`, breaking all workflow executions on Windows dev machines — while `ubuntu-latest` and `macos-latest` CI stayed green. See the discussion in #6488. ## Proposal Add a small Windows CI leg that exercises the OS-sensitive paths, so dependency bumps that break Windows development fail in the PR instead of on a dev machine weeks later. A minimal starting point: | | | |---|---| | Runner | `windows-latest` | | Scope | `WorkflowCore` unit tests (or just the file-system-sensitive specs, e.g. `IcebergUtilSpec` + `WinutilsFreeLocalFileSystemSpec`) | | Would it have caught #6487? | Yes — the regression test added in #6488 fails on a stock Windows runner without the fix | Notes / open questions: - A full `build / amber` Windows leg is likely too heavy (Windows runners are slower and billed at 2x; amber integration tests spawn Python workers via `signal.SIGKILL`, which does not exist on Windows), so scoping to unit tests of the storage/file-system layer keeps the cost low. - A Windows leg would also cover the Windows-only branches that Linux-based Codecov runs cannot execute. - Could run on `main` + dependency-labeled PRs only, if PR latency is a concern. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
