@Jason Gross Are you triggering the comment posting even before the pipeline for the head commit is finished? If yes, that could explain why.
The double reporting also happened in https://github.com/coq/coq/pull/14272.
It'll report again every time the overall pipeline status check is finished. If a job fails and then someone restarts the job, when it finishes the second time, this will trigger a second comment. Perhaps that's what happened? Note that the lack of "you may want to wait" message indicates that coqbot believed both the base and head pipeline checks finished when it was posting each comment.
I checked the first example, and it doesn't look like there was any job that was restarted.
Could it be that the GitLab webhook was delivered twice?
I thought Matthieu said that he manually restarted the job at https://github.com/coq/coq/pull/9711#issuecomment-850409440 ?
Indeed, my strategy for checking that there was no reply was not correct.
Last updated: Mar 02 2024 at 17:02 UTC