yuqi1129 commented on PR #13049: URL: https://github.com/apache/gravitino/pull/13049#issuecomment-6186524425
I pushed fixes on top of your commits (no force push): - `dc6dd18` Merge main. This resolves the `build.yml` conflict, and the core test lanes and coverage job added in #13517 now run on the synced fork checkout. - `a59b13c` Use the ASF-allowlisted paths-filter pin in web UI tests - `7864fca` Run fork CI for a push made before its pull request is opened; build timeout 180m - `bd9f86d` Mirror fork CI re-runs and reduce status sweep API calls - `6d173da` Run the scheduled Lance compatibility matrix only upstream These match what I verified in the sandbox (see my comment above). Fork CI runs for this head: - [Full run](https://github.com/yuqi1129/gravitino/actions/runs/38666821869): 41 jobs passed and 6 were skipped, including the new core test lanes and the coverage job. - [Code-only change](https://github.com/yuqi1129/gravitino/actions/runs/38678728825) (one Java file in `core`, no PR opened yet): the base was inferred correctly. build, the core lanes, coverage and all core-dependent ITs ran and passed. Unrelated jobs (web UI, charts, contrib catalog, MCP) were skipped. The job durations match the same jobs on apache PR runs (same `ubuntu-latest` / `ubuntu-22.04` runners). The slowest is BackendIT mysql at about 100 min. Your fork's Actions had been disabled by GitHub, so this push didn't trigger a run there. It is enabled now, and the next push will run there. -- 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]
