New edition of process_pr#2626
Conversation
87a48fb to
f94d70c
Compare
|
Pull request #2626 was updated. |
3 similar comments
|
Pull request #2626 was updated. |
|
Pull request #2626 was updated. |
|
Pull request #2626 was updated. |
e539998 to
5fc68a2
Compare
|
Pull request #2626 was updated. |
8e05b86 to
c964451
Compare
|
Pull request #2626 was updated. |
4 similar comments
|
Pull request #2626 was updated. |
|
Pull request #2626 was updated. |
|
Pull request #2626 was updated. |
|
Pull request #2626 was updated. |
396bbf0 to
8df9ee8
Compare
|
@iarspider , does new bot properly check for |
|
@smuzaffar not exactly. I was assuming that PyGithub handles that "under the hood", but after examining the library code I see that it only reacts to limit being exceeded. I will prepare and push a change to add a few rate limit checks in critical places. |
|
I have squased the PR, will work on rate limit later. |
|
@raoatifshad , I see in jenkins job https://cmssdt.cern.ch/jenkins/job/cms-bot/1945425/console can you please check if bot has seen |
|
FYI @iarspider #2626 (comment) (new bot is keep on triggering code-checks for cms-sw/cmssw#49771 ) |
|
For now I have added |
|
Checking. |
@smuzaffar as discussed today. I have put new code into new file (
process_pr_v2.py), will replace oldprocess_prbefore merging.It doesn't yet do everything - for example, it won't detect when tests are complete, I will implement it later.
We can also use this opportunity to implement our own handling of commit statuses (I have a draft cgi handler for this) that we should discuss offline.