SEPURI-SAI-KRISHNA commented on PR #12495:
URL: https://github.com/apache/seatunnel/pull/12495#issuecomment-6011353304

   Rebased on `dev` to clear a conflict, head is now `8c7553d27`. The merge was 
needed because #12403 (AES functions) and #12335 (vector buffers) landed in the 
same three files this PR touches. Only one conflict, competing imports in 
`VectorFunctionTest`, resolved by keeping both. The PR diff is unchanged line 
for line, and the module is green locally at `Tests run: 1228, Failures: 0`.
   
   **Build is red on that head, and none of it is from this change.** Breakdown 
of run `37272080837`, with durations checked against the `backend.yml` limits:
   
   | job | outcome | detail |
   | --- | --- | --- |
   | `Build website` | cancelled | 90.2 min against a 90 minute limit, so a 
timeout. #12614 is the fix |
   | `engine-v2-it (11)` | failure | infrastructure, not a test: the log ends 
with "The runner has received a shutdown signal" and step 5 cancelled. Zero 
failing tests in it |
   | `unit-test (8, ubuntu-latest)` | failure | 
`SavePointTest.testSavePointButJobGoingToFail`, `expected: <RUNNING> but was: 
<FAILED>` at `SavePointTest.java:89` |
   
   On that last one: it is in `seatunnel-engine-server`, which this PR does not 
touch, and the other three `unit-test` legs passed. I checked our four previous 
runs and `unit-test` was green on every leg in all of them, so this is a first 
occurrence rather than something recurring. I did not find an upstream issue 
for it, and I am not going to call it a known flake on one sighting.
   
   What is green and relevant: all four `transform-v2-it` legs, part-1 and 
part-2 on both JDK 8 and 11, which are the integration tests for the module 
this PR changes.
   
   Happy to rerun the two failed jobs if that is useful.
   


-- 
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]

Reply via email to