Conversation
|
@microsoft-github-policy-service agree |
|
There appear to be a number of legitimate feature test failures for that port; I'm not sure whether that's a change vs. the status quo though. Please investigate whether those are expected failures on the part of the port (in which case those features should probably be guarded with a Thanks for the update submission! |
|
AI review: vcpkg CI Failure ReportBuild: #129921 Summary
Total: 7 failed jobs, 0 REGRESSION lines. The core 🔴 Issue 1: Version Validation ErrorTriplet: x86-windows (affects all triplets — x86 just runs validation first)
🔴 Issue 2: Go-Dependent Features Fail on All Non-Windows TripletsTriplets: x64-linux, arm64-osx, x64-android, arm64-android, arm-neon-android arm64-osx: Go Not Found
x64-linux: Go Permission Denied
ImpactThe core However, these baseline entries only cover
🟡 Issue 3: Feature Baseline Coverage GapTriplets: x64-linux, arm-neon-android, arm64-android, x64-android, arm64-osx The Go-dependent features ( Since Go is unavailable on all non-Windows CI agents, the baseline needs to cover all affected triplets.
ℹ️ Notes
Required Actions for PR Author
|
Add three new failure pattern categories: - Category 16: Version validation failures (missing x-add-version) - Category 17: Missing build tools in CI (Go, Java, Rust) - Category 18: Feature baseline coverage gaps across triplets Document feature test artifact structure (issue_body.md + tested-spec.txt) and add corresponding notes, formatting rules, and common patterns. Co-authored-by: Copilot <[email protected]>
Thanks. I've added the non-windows Go-based features to |
Windows build support has been added to
arrow-adbcas part of this PR:apache/arrow-adbc#2858
arrowis not needed as a dependency for corearrow-adbc, mainlynanoarrow.Patches no longer needed as a result of new changes to
arrow-adbcfrom above PR../vcpkg x-add-version --alland committing the result.