[
https://issues.apache.org/jira/browse/FLINK-33254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775543#comment-17775543
]
Matthias Pohl edited comment on FLINK-33254 at 10/16/23 6:17 AM:
-----------------------------------------------------------------
I also reverted copying the build artifacts and checked the build times:
||Run||Licence Checker||e2e1 compile||e2e2 compile||flink-python
tests||flink-table tests||flink-connect tests||flink-tests tests||M2
Caching||Build artifact||
|[Run @5437c3b|https://github.com/XComp/flink/actions/runs/6510559714]|1h
40m|34m 45s|58m 3s|<error>|<error>|<error>|<error>|(x)|(/)|
|...| | | | | | | | | |
|[Run @54eefec|https://github.com/XComp/flink/actions/runs/6524656877]|40m
19s|7m 40s|8m 17s|<error>|<error>|<error>|<error>|(/)|(/)|
|[Run @4706d3|https://github.com/XComp/flink/actions/runs/6524929361]|56m
50s|6m 46s|7m 45s|<error>|<error>|<error>|<error>|(/)|(/)|
|[Run @d0a31ae|https://github.com/XComp/flink/actions/runs/6525041368]|43m
42s|6m 53s|8m 22s|1h 23m 23s|2h 13m 21s|30m 36s|1h 17m 54s|(/)|(/)|
|[Run @d5e9188|https://github.com/XComp/flink/actions/runs/6525150610]|38m
38s|7m 18s|7m 39s|1h 25m 21s|2h 1m 13s|35m 54s|1h 29m 37s|(/)|(/)|
|[Run
@f9d5d1e|https://github.com/XComp/flink/actions/runs/6525266999]|<error>|15m
17s|15m 42s|1h 42m 18s|2h 0m 3s|48m 45s|1h 14m 51s|(/)|(x)|
|[Run @8c71a90|https://github.com/XComp/flink/actions/runs/6525933101]|51m
5s|15m 57s|14m 28s|1h 29m 18s|2h 17m 27s|40m 35s|1h 23m 35s|(/)|(x)|
|[Run @b0ca2d0|https://github.com/XComp/flink/actions/runs/6525957588]|46m
41s|14m 11s|15m 39s|1h 34m 5s|2h 14m 53s|43m 9s|1h 52m 23s|(/)|(x)|
|[Run @f879cf4|https://github.com/XComp/flink/actions/runs/6529672916]| | | | |
| | | | |
|[Run @21aceb7|https://github.com/XComp/flink/actions/runs/6529754573]| | | | |
| | | | |
This feature has some effects on the e2e tests, at least. The runtime of the
other test modules were to volatile to come up with a conclusion. But it
doesn't hurt to utilize the build artifacts there as well. ¯_(ツ)_/¯
was (Author: mapohl):
I also reverted copying the build artifacts and checked the build times:
||Run||Licence Checker||e2e1 compile||e2e2 compile||flink-python
tests||flink-table tests||flink-connect tests||flink-tests tests||M2
Caching||Build artifact||
|[Run @5437c3b|https://github.com/XComp/flink/actions/runs/6510559714]|1h
40m|34m 45s|58m 3s|<error>|<error>|<error>|<error>|(x)|(/)|
|...|
|[Run @54eefec|https://github.com/XComp/flink/actions/runs/6524656877]|40m
19s|7m 40s|8m 17s|<error>|<error>|<error>|<error>|(/)|(/)|
|[Run @4706d3|https://github.com/XComp/flink/actions/runs/6524929361]|56m
50s|6m 46s|7m 45s|<error>|<error>|<error>|<error>|(/)|(/)|
|[Run @d0a31ae|https://github.com/XComp/flink/actions/runs/6525041368]|43m
42s|6m 53s|8m 22s|1h 23m 23s|2h 13m 21s|30m 36s|1h 17m 54s|(/)|(/)|
|[Run @d5e9188|https://github.com/XComp/flink/actions/runs/6525150610]|38m
38s|7m 18s|7m 39s|1h 25m 21s|2h 1m 13s|35m 54s|1h 29m 37s|(/)|(/)|
|[Run
@f9d5d1e|https://github.com/XComp/flink/actions/runs/6525266999]|<error>|15m
17s|15m 42s|1h 42m 18s|2h 0m 3s|48m 45s|1h 14m 51s|(/)|(x)|
|[Run @8c71a90|https://github.com/XComp/flink/actions/runs/6525933101]|51m
5s|15m 57s|14m 28s|1h 29m 18s|2h 17m 27s|40m 35s|1h 23m 35s|(/)|(x)|
|[Run @b0ca2d0|https://github.com/XComp/flink/actions/runs/6525957588]|46m
41s|14m 11s|15m 39s|1h 34m 5s|2h 14m 53s|43m 9s|1h 52m 23s|(/)|(x)|
This feature has some effects on the e2e tests, at least. The runtime of the
other test modules were to volatile to come up with a conclusion. But it
doesn't hurt to utilize the build artifacts there as well. ¯\_(ツ)_/¯
> Improve speed of compile step
> -----------------------------
>
> Key: FLINK-33254
> URL: https://issues.apache.org/jira/browse/FLINK-33254
> Project: Flink
> Issue Type: Sub-task
> Reporter: Matthias Pohl
> Priority: Major
>
> There were issues with the compilation step where I initially thought that
> it's due to the parallelization of the compilation (which is odd). This issue
> is about investigating how to do the compilation and forwarding the artifacts
> in the right way to the downstream jobs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
