DanielLeens commented on issue #12483:
URL: https://github.com/apache/seatunnel/issues/12483#issuecomment-6217829505

   Classification: I / CI workload-routing and capacity evidence.
   
   Thank you for supplying measured shard outcomes. The two capped shards on 
separate JDK legs support the conclusion that the immediate problem is workload 
imbalance, not a single flaky timeout. The round-robin module split also 
explains why simply raising one timeout would not be a durable fix.
   
   This remains one fork run, so please add the raw workflow links and at least 
one comparable upstream or independent run to the dev@ discussion before 
changing the default engine set. The decision needs the reduced-set coverage 
risk, the full nightly backstop, and the proposed full-e2e override documented 
together.
   
   No implementation should begin from this issue alone. PR #12650 is unrelated 
to the routing proposal and currently has a failed Build, so it is not evidence 
that the proposed engine-set change is ready.
   


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