[
https://issues.apache.org/jira/browse/TEZ-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080098#comment-18080098
]
Raghav Aggarwal commented on TEZ-4355:
--------------------------------------
[~abstractdog] , I was thinking maybe the following can be done:
# Upload build-tools docker image in tez docker registry. I think this will
save both time and compute by not building docker image repeatedly.
# Build the complete project with fresh m2 repo -> Generate spotbugs,
checkstyle, javadocs, codespell etc *only on diff patch* -> RUN UT on complete
project irrespective of content of PR
# Possibly print yetus like summary at end.
I haven't explored much on optimizing the stages but the current CI is prone to
errors. Let me know if its something that I can help by picking this task or
reviewing the current PR. _From my POV this is very high priority task —
unless, of course, we're actively looking forward to the thrill of a ticking
timebomb going off in prod._
> Unit test precommit improvements - full coverage
> ------------------------------------------------
>
> Key: TEZ-4355
> URL: https://issues.apache.org/jira/browse/TEZ-4355
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 1. What about running all unit tests in precommit? With the current precommit
> load in Tez project, it's worth trying (however it needs some flakiness fixes)
> 2. Run tests in splits in a parallel fashion: 2 different, deterministic
> splits could be a) tez-tests module vs. b) all the rest
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
