u70b3 commented on PR #67158:
URL: https://github.com/apache/doris/pull/67158#issuecomment-5460826656
Hi @Gabriel39 — I believe this change inadvertently breaks Paimon prebuilt
reuse on the current CI build image, which is now failing the COMPILE and
performance pipelines of PRs merged with master.
Failure (before any compilation starts):
```
Paimon build fingerprint does not match selected inputs
Arrow/Paimon thirdparty libraries need to be rebuilt ...
Cannot rebuild thirdparty libraries:
/var/local/thirdparty/build-thirdparty.sh is missing.
DORIS_THIRDPARTY=/var/local/thirdparty is an install-only or incomplete
prefix.
```
Analysis:
- On current master, `paimon_build_fingerprint` computes
`9887cf1ec13106da4250f8d7ea931a258879089c`, matching the updated
`PAIMON_LEGACY_COMPATIBLE_SEMANTIC_FINGERPRINT` — that part is correct.
- However, the prebuilt marker installed in the current build image
(`apache/doris:build-env-ldb-toolchain-latest`, digest `sha256:5d474521b72d…`)
is still the *previous* semantic fingerprint
`cb82e41ba46f534e611cdd52e66b53c227d49bf8`, which is not in
`PAIMON_LEGACY_BUILD_FINGERPRINTS` (`2bbf52e7…`, `dbb6ca6e…`), so
`paimon_prebuilt_valid` now rejects it.
- Pinpoint by elimination: the same image digest passed the same pipeline
one day earlier (pre-#67158 checkout: expected == `cb82e41ba` == installed
marker, direct match), and fails today (installed ∉ {`9887cf1ec`, 2bbf52e7…,
dbb6ca6e…}).
Suggested fix: since the dependency-ordering change does not alter the
installed artifacts (as the commit message notes), the old semantic marker
should remain accepted — add `cb82e41ba46f534e611cdd52e66b53c227d49bf8` to
`PAIMON_LEGACY_BUILD_FINGERPRINTS` (with a comment noting it is a semantic
marker), or republish the prebuilt stamped with the new semantic fingerprint
and roll it into the build image.
Example failing builds on TeamCity: COMPILE 1034233, performance 1034228
(both on a PR merged with master after this change). Happy to send the one-line
PR if that helps.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
