Since 1-2 days ago, we don't get any CI jobs from pull requests to the opam archive. @Enrico Tassi do you know what's going on?
Hum no. @Théo Zimmermann any clue? Is it related to the recent coqbot changes?
There were several problems that were reported and that were fixed already so let me know if this is still the case with new of updated PRs.
@Théo Zimmermann I just opened a new opam archive PR, still no CI: https://github.com/coq/opam-coq-archive/pull/1403
on the other hand, it looks like this commit got a CI run on merge: https://github.com/coq/opam-coq-archive/commit/b206d27e4c03596ab3bb07c3967c0783bb96526e
ah, now my force-pushed PR started its CI, let me see if it persists
hmm, maybe this is related to GitLab pipeline/job limitations?
it looks like the jobs are being run, but nothing is reported back on GitHub: https://gitlab.com/coq/opam-coq-archive/-/pipelines
OK I know what the issue is.
FTR here it is: coqbot used to push status checks as a normal user. Now it supports posting them as a GitHub App (but also the old method for backward compatibility). The GitHub App was installed on the Coq repository but only given access to the Coq repository and not the opam-coq-archive repository. Thus, attempts to push status checks (as an App) for the latter were rejected. I fixed this by extending the installation of the App and I've resent a few webhooks to make sure that was it.
This topic was moved here from #Coq devs & plugin devs > opam archive CI seems dead by Théo Zimmermann
that makes sense, thanks for the fix, I thought I was going to spend the week cross-referencing between GitHub and GitLab
When you see such issues, feel free to ping me immediately.
sure, now that I know how it works at a high level. I just review the PRs and merge over here...
Last updated: Jan 31 2023 at 09:01 UTC