dybyte commented on PR #9818: URL: https://github.com/apache/seatunnel/pull/9818#issuecomment-3343808338
The Paimon privilege error logs were actually caused by intentional exceptions in specific tests, so I misinterpreted them earlier. However, the issue of Paimon CI jobs being canceled still remains. Even after merging recent commits, the problem has not been resolved. One thing I noticed is that `updatePipelineState(PipelineStatus.CANCELING)` did not complete for some reason, which I suspect may be due to resource limitations in the CI environment. Therefore, I’m fine with closing this PR for now. ``` com.hazelcast.spi.impl.operationexecutor.slowoperationdetector.SlowOperationDetector - [localhost]:5801 [seatunnel] [5.1] Slow operation detected: org.apache.seatunnel.engine.server.checkpoint.operation.CheckpointErrorReportOperation 2025-09-27T11:08:52.6438740Z [] 2025-09-27 11:08:52,643 INFO tc.seatunnel-engine:openjdk:8 - STDERR: org.apache.seatunnel.engine.server.dag.physical.SubPlan.updatePipelineState(SubPlan.java:340) 2025-09-27T11:08:52.6439782Z [] 2025-09-27 11:08:52,643 INFO tc.seatunnel-engine:openjdk:8 - STDERR: org.apache.seatunnel.engine.server.dag.physical.SubPlan.handleCheckpointError(SubPlan.java:601) 2025-09-27T11:08:52.6441346Z [] 2025-09-27 11:08:52,643 INFO tc.seatunnel-engine:openjdk:8 - STDERR: org.apache.seatunnel.engine.server.master.JobMaster.lambda$handleCheckpointError$8(JobMaster.java:595) 2025-09-27T11:08:52.6442371Z [] 2025-09-27 11:08:52,643 INFO tc.seatunnel-engine:openjdk:8 - STDERR: org.apache.seatunnel.engine.server.master.JobMaster$$Lambda$3006/1161858620.accept(Unknown Source) 2025-09-27T11:08:52.6443175Z [] 2025-09-27 11:08:52,643 INFO tc.seatunnel-engine:openjdk:8 - STDERR: java.util.ArrayList.forEach(ArrayList.java:1259) 2025-09-27T11:08:52.6443990Z [] 2025-09-27 11:08:52,643 INFO tc.seatunnel-engine:openjdk:8 - STDERR: org.apache.seatunnel.engine.server.master.JobMaster.handleCheckpointError(JobMaster.java:592) ``` -- 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]
