The GitHub Actions job "Oak Segment Consensus" on 
jackrabbit-oak.git/reconcile/poc-into-trunk has failed.
Run started by GitHub user somarc (triggered by somarc).

Head commit for run:
6a700aad4e952b117bb47bd6a721e86856bd27de / somarc 
<[email protected]>
Reconcile post-promotion feature work into the Somarc product mainline

Merge feature/blockchain-aem-poc (0a988e29f1) into origin/trunk (307e98e333).
The 50 consensus commits made on the feature branch after the Sep-20
promotion now build on the trunk's Apache Oak 2.7 / Java 17 baseline instead of
the stale oak-parent 1.93-SNAPSHOT anchor the feature branch still declared.

Outside oak-segment-consensus the result is identical to origin/trunk: the
promotion's POM alignment (2.7-SNAPSHOT parents, 2.7.0-somarc-SNAPSHOT module
versions, ${oak.version} dependencies), the IPFS DataStore move to
org.apache.jackrabbit.oak.spi.blob.data and the CI workflow are kept.

Overlapping designs were unified rather than stacked:
- Rejection: one class, MutationRejectedException (trunk), with the feature
  branch's cause-chain check; InvalidProposalException is removed.
- Clock: MutationAuditMetadata.appliedAt (Aeron command timestamp, trunk) plus
  the feature branch's applied-log watermark in the same Oak merge.
- Apply failure: the feature branch's engine-level fail-stop (FATAL agent
  termination) with trunk's latch, 503 route and unhealthy reason; node-local
  failures surface as ReplicatedApplyException.
- Genesis: trunk's genesis v2 (parameter-free trigger, Aeron time, configured
  bootstrap member, digest seal, verified-genesis health gate) applied only from
  the log, recording the watermark; GenesisInitializer verifies only.
- Term: the dispatcher keeps the term provider, now Aeron's leadershipTermId in
  log order, which the watermark and LogStoreGuard depend on.
- AppliedLogPosition.NONE covers nothing.

Validation: oak-segment-consensus 1,397 unit tests on the merged tree.

Report URL: https://github.com/apache/jackrabbit-oak/actions/runs/37248926673

With regards,
GitHub Actions via GitBox

Reply via email to