The GitHub Actions job "Required Checks" on texera.git/backport/7996-enable-checkpoint-serialization-v1.2 has failed. Run started by GitHub user github-actions[bot] (triggered by github-actions[bot]).
Head commit for run: a25868b36b256b519603afe4e761e6b53bf40abf / anthonychengit <[email protected]> fix(amber): enable checkpoint serialization (#7996) ### What changes were proposed in this PR? Make <code>CheckpointState</code> implement <code>Serializable</code>, so the existing Kryo binding can persist worker checkpoints. Before: finalize checkpoint → serialize <code>CheckpointState</code> → no matching binding → <code>NotSerializableException</code> After: finalize checkpoint → Kryo binding → flush/close → restore the original checkpoint payload The regression test uses a real worker write path, stores a non-empty Unicode payload, reads the record back from sequential storage, and asserts the returned size and restored value. Two existing write-branch tests now await successful completion instead of discarding failures. ### Any related issues, documentation, discussions? Closes #7907 ### How was this PR tested? Added positive persistence/round-trip coverage while retaining the existing estimate-only and checkpoint-isolation cases. ~~~powershell $env:STORAGE_JDBC_URL='jdbc:postgresql://localhost:15432/texera_codex_jooq?currentSchema=texera_db,public' $env:STORAGE_JDBC_USERNAME='postgres' $env:STORAGE_JDBC_PASSWORD='' sbt "WorkflowExecutionService/testOnly org.apache.texera.amber.engine.architecture.worker.promisehandlers.FinalizeCheckpointHandlerSpec" sbt "scalafixAll --check" "scalafmtCheckAll" ~~~ Result: 6 tests passed; Scalafix and Scalafmt checks passed. The focused suite used an isolated embedded PostgreSQL database and port. ### Was this PR authored or co-authored using generative AI tooling? (backported from commit be5144325e9f61b46387faf9ebcf77090e64185e) Generated-by: OpenAI Codex (GPT-5) Report URL: https://github.com/apache/texera/actions/runs/33292089352 With regards, GitHub Actions via GitBox
