Hi Fabrizio, thank you for checking. Images and kie-tools probably don't use build-chain tool (1), that is why it is working properly there. The problem looks to be related to how build-chain is doing GitHub API calls to find out a branch in a fork for a PR. There is a suspicion that something changed in GitHub APIs. build-chain is written in TypeScript. I am not proficient in it, so if there is someone that works with TypeScript willing to take a look too, it would be very helpful.
Best regards, Tibor (1) https://github.com/kiegroup/github-action-build-chain Dňa st 6. 3. 2024, 12:19 Fabrizio Antonangeli <[email protected]> napísal(a): > Hi, > I would like to share my "troubleshooting" trying to help. > Checking for instance this check on Drools [1], under "Java and maven > setup/Checking > out the ref" I see that the checkout command is: > "/usr/bin/git checkout --progress --force -B main refs/remotes/origin/main" > > But in my PR [2] in KIE-Tools, under "Checking @ GitHub default/Checking > out the ref" the checkout command is: > "/usr/bin/git checkout --progress --force refs/remotes/pull/2167/merge" > Which is right and the failures are related to my code. > > I can see also Kogito-images is running the right command in this check > [3]: > "/usr/bin/git checkout --progress --force refs/remotes/pull/1751/merge" > > > 1: > > https://github.com/apache/incubator-kie-drools/actions/runs/8158851882/job/22301732802 > 2: > > https://github.com/apache/incubator-kie-tools/actions/runs/8160619804/job/22307579461?pr=2167 > 3: > > https://github.com/apache/incubator-kie-kogito-images/actions/runs/8128917643/job/22235253380 > > On Wed, Mar 6, 2024 at 10:26 AM Yeser Amer <[email protected]> wrote: > > > Quick update > > > > It seems this issue affects other KIE repos as well. > > > > Please DO NOT MERGE any PR until the team finds a solution for that > issue. > > > > Thank you. > > > > On 2024/03/06 08:30:17 Tibor Zimányi wrote: > > > Hi everyone, > > > > > > it was found (thanks Toshiya), that the PR checks started to run the > > > apache/main branches of the repositories, instead of the PR check > > branches. > > > See example log from a PR: > > > > > > [INFO] Checking if apache/incubator-kie-drools is forked to > > > baldimir/incubator-kie-drools > > > [INFO] Fork baldimir/incubator-kie-drools does not exist. Trying to > find > > a > > > fork with a different name in baldimir > > > [INFO] Fork baldimir/drools found from apache/incubator-kie-drools > > > [INFO] apache/incubator-kie-drools checked out > > > > > > This means that the PR checks are green all the time and are not > properly > > > testing the changes. Currently it is being investigated, what caused > this > > > problem. It looks like it started to happen somewhere around 27th to > 28th > > > February. So please don't merge any PRs until further notice as there > is > > no > > > guarantee that the code changes are not breaking anything in the > > codebase. > > > Sorry for the disturbance, hopefully this gets resolved soon. > > > > > > Best regards, > > > Tibor > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
