RFR: 1691: Run Jcheck twice in CheckRun if .jcheck/conf has changed [v3]

Magnus Ihse Bursie ihse at openjdk.org
Thu Dec 8 18:36:35 UTC 2022

On Thu, 8 Dec 2022 18:13:39 GMT, Zhao Song <zsong at openjdk.org> wrote:

>> When a pr is created, pr bot will run jcheck to check whether this commit is good. However, currently, we only run jcheck with the configuration from the target branch. Sometimes, user wants to modify jcheck configuration and accidentally messes up the format. In this case, pr bot would not be able to find this problem. After this commit with badly formatted jcheck configuration integrated, all the jcheck will fail and our bot gets stuck into a retry loop.
>> In this patch, if jcheck configuration file is updated, the bot will run jcheck twice, once with the configuration in the target and once with the new one in the source. So if the new configuration has any problem, it will became an integration blocker.
> Zhao Song has updated the pull request incrementally with one additional commit since the last revision:
>   fix problems

Are we sure we are not painting ourselves in a corner were a change in .jcheck/conf is impossible to do since it will fail either before or after applying? I can't really think of such example, but maybe I'm just not trying hard enough.


PR: https://git.openjdk.org/skara/pull/1439

More information about the skara-dev mailing list