RFR: 1707: Bot warns about "No .jcheck/conf found" when it should not [v6]
Zhao Song
zsong at openjdk.org
Tue Dec 6 21:44:04 UTC 2022
> In [SKARA-1393](https://bugs.openjdk.org/browse/SKARA-1393), I added some checks to ensure the target branch of a pr contains valid jcheck configuration. This change went live on November 28, however, some users found that the warning of "No .jcheck/conf found" printed after they integrated their pr. After more investigation, I am thinking it's maybe a GitLab bug. Since when the issue happens, GitLab will always return "Commit Not Found", so we could have a temporary workaround right now.
>
> For GitLab REST API:
> If commit not found, it will return "404 Commit Not Found"
>
> If file not found it will return "404 File Not Found"
>
> For Github REST API:
> If commit not found, it will return "No commit found for the ref "
>
> If file not found it will return "Not Found"
Zhao Song has updated the pull request incrementally with one additional commit since the last revision:
fix problems
-------------
Changes:
- all: https://git.openjdk.org/skara/pull/1435/files
- new: https://git.openjdk.org/skara/pull/1435/files/2adf3643..15bf695a
Webrevs:
- full: https://webrevs.openjdk.org/?repo=skara&pr=1435&range=05
- incr: https://webrevs.openjdk.org/?repo=skara&pr=1435&range=04-05
Stats: 67 lines in 12 files changed: 8 ins; 19 del; 40 mod
Patch: https://git.openjdk.org/skara/pull/1435.diff
Fetch: git fetch https://git.openjdk.org/skara pull/1435/head:pull/1435
PR: https://git.openjdk.org/skara/pull/1435
More information about the skara-dev
mailing list