voonhous opened a new issue, #19910:
URL: https://github.com/apache/hudi/issues/19910

   Part of #19524. Baseline is master run 
[34314808833](https://github.com/apache/hudi/actions/runs/34314808833): 615 
runner-minutes over 19 test jobs, longest job 77 min, two trips through the 
runner queue per run.
   
   | PR | change | runner-min per run | critical runtime | status |
   |---|---|---|---|---|
   | #19890 | flatten the job graph, path filter at the trigger | 615 -> 617 
(unchanged) | second queue hop gone (median 1 min, p90 82 min) | measured, 
ready to merge |
   | #19892 | two surefire forks, DeltaStreamer split, jobs resharded by 
measured time | 615 -> 577 | longest job 77 -> 41 min | measured, ready to 
merge after #19890 |
   | #19906 | test Spark sessions at 2 shuffle partitions, AQE off | 577 -> 
~547 (Spark lanes 447 -> 417, mean of two runs) | no change inside noise | 
measured, third run pending |
   | #19909 | one full build per module and lane: flink-2 filter, docker build 
trim, examples-spark trim | expected ~-34 | longest job 39 -> ~35 | first run 
in progress |
   | #19905 | Maven build cache | - | - | closed: the repository's Actions 
cache store keeps nothing |
   
   Expected once the four open PRs merge: about 615 -> 510 runner-minutes 
(-17%), longest job 77 -> ~35 min (-55%), one queue hop.
   
   Deferred, with reasons on record:
   - method-level test concurrency: 
https://github.com/apache/hudi/pull/18201#issuecomment-5633539153
   - path scoping between the Spark and engine workflows (~11% of 
runner-minutes, needs a path-to-lane map)
   - pinning six transitive version ranges (junit, junit-dep, json-smart, grpc 
x3) to remove metadata checks against jitpack.io and cloudera; one 16-minute 
stall observed
   - running test-common-and-other-modules outside its 2024 container 
(maintenance, not time)
   


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