ym0506 commented on issue #38298: URL: https://github.com/apache/shardingsphere/issues/38298#issuecomment-4001324402
I investigated this issue and compared failed/successful jobs in the same run: https://github.com/apache/shardingsphere/actions/runs/22547669595 The failed jobs hit `actions/checkout` with: `fatal: remote error: upload-pack: not our ref 48ffae5acbd53e554a99fe93ebd0cf6572a5a6a5` while other matrix jobs in the same run succeeded. So this looks like an intermittent synthetic-merge checkout problem, not a test-code regression. I’d like to propose a small workflow fix in `e2e-sql.yml`: - for `pull_request`, checkout by PR merge ref (`refs/pull/<number>/merge`) instead of relying on the synthetic merge SHA fetch path - keep `workflow_dispatch` behavior unchanged This still validates against merged-with-base state, but should reduce accidental `not our ref` failures. I can open a PR scoped to E2E-SQL first. -- 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]
