Uh oh!
There was an error while loading. Please reload this page.
HBASE-29838 Run Hadoop Check as a GitHub Action - #7651
Conversation
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ndimiduk
commented
Jan 20, 2026
Looks like we occupied the runner for 6h and then it was aborted. |
Apache9
commented
Jan 20, 2026
https://infra.apache.org/github-actions-policy.html The policy here does not say about the 6 hours timeout... We can ask infra about the rules and the size of the github runners, our jenkins runners finished in "343m 23s", which was very close to 6 hours, so if the machine of the github runner is weaker, the build will be very easy to cost more than 6 hours... |
ndimiduk
commented
Jan 20, 2026
My action itself has |
ndimiduk
commented
Jan 20, 2026
or not. 6h is GH's hard limit, https://docs.github.com/en/actions/reference/limits |
Apache9
commented
Jan 21, 2026
Then maybe we should try self hosted github runners? For self hosted runners the execution time limit is 5 days... |
1829212 to
352a9a1Comparendimiduk
commented
Jan 23, 2026
Yes we should bring this back to our CI discussions with Infra. Maybe we can borrow from the pool of new Jenkins workers while we continue to build this out. Yetus is supposed to provide smart, selective detection of module changes when it decided which tests to run. I think the new .github directory broke that for this run, so I've pushed a change to exclude it, maybe that will help. I'm also going to see if I can manually parallelize the unit test runs -- maybe break out three separate checks for the three main unit test groups or something like that. |
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Apache9
commented
Jan 23, 2026
Maybe we could split the UTs run as a seperated github check? Or even more, we could split the UTs run as two seperated check, one has -PrunDevTests(for small/medium tests) and one has -PrunLargeTests(for large tests). |
ndimiduk
commented
Jan 23, 2026
Yep, that's exactly my thinking as well. Landing these other cleanup issues and I'll be back. |
352a9a1 to
adfd056Compare
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
ndimiduk
commented
Jan 23, 2026
Okay this is better. Module selection chose only hbase-examples for running the unit tests. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
ndimiduk
commented
Jan 23, 2026
Looking over out last successful nightly on master, the Large tests on hbase-server still took 7h. I'm looking for other ways to partition this up. |
adfd056 to
ad51411Compare
This comment has been minimized.
This comment has been minimized.
ndimiduk
commented
Feb 3, 2026
I spot-checked the tests run by large waves 1 and 3 (2 is still running) and they look to contain only the expected tests. I think we're good here. Any other comments @Apache9 ? |
This comment has been minimized.
This comment has been minimized.
0c5a250 to
4fbb099Compare
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Uh oh!
There was an error while loading. Please reload this page.
4fbb099 to
571a79dCompare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
571a79d to
2dcbbd0Compare
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Uh oh!
There was an error while loading. Please reload this page.
e05c8d1 to
add8096Compare
This comment has been minimized.
This comment has been minimized.
Apache-HBase
commented
Feb 5, 2026
(!) A patch to the testing environment has been detected. |
1 similar comment
Apache-HBase
commented
Feb 5, 2026
(!) A patch to the testing environment has been detected. |
Apache-HBase
commented
Feb 5, 2026
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Feb 5, 2026
🎊 +1 overall
This message was automatically generated. |
Apache9
left a comment
There was a problem hiding this comment.
I think the current one is enough to be merged so we can disable the jenkins pre commit job.
There are still problems like mvninstall is still present in unit check, and the job summary for unit check still needs improvement, etc. Can file new issues for improving.
Thanks @ndimiduk for the great work!
Signed-off-by: Duo Zhang <zhangduo@apache.org>
add8096 to
8ec8770CompareUh oh!
There was an error while loading. Please reload this page.
No description provided.