Repository navigation
New cache format for cms-bot v2 - #2891
Conversation
|
A new Pull Request was created by @iarspider for branch master. @akritkbehera, @cmsbuild, @iarspider, @raoatifshad, @smuzaffar can you please review it and eventually sign? Thanks. |
|
cms-bot internal usage |
|
Pull request #2891 was updated. |
|
thanks @iarspider for looking in to this. How this change will behave for existing PRs processed already processby v2? I hope this change will change re-write the bot cache ... right? |
Yes - unless the bot stops early (e.g. if it encounters commits from the future). |
|
Is it expected that new v2 will always go back to get files e.g. https://cmssdt.cern.ch/jenkins/job/cms-bot/2181120/console I see that bot is again calling get files I thought that is base sha and PR sha are not changed then bot will re-use the previously cached files info |
|
Pull request #2891 was updated. |
|
also looks like every time bot process a PR then its cache comment is edited ( I guess when comment is compressed ), see cms-data/MagneticField-Interpolation#6 where comments are edited 3 times . I guess if you compare the uncompressed comment contents then you might be able to avoid the editting |
|
Checking. It should reuse existing cache if it exists. |
|
Pull request #2891 was updated. |
I can't reproduce the problem with this branch - see https://cmssdt.cern.ch/jenkins/job/cms-bot/2181343/console: It also doesn't overwrite the cache: |
|
I opened new cms-data/MagneticField-Interpolation#7 which was processed by new v2 bot but then a new bot job started with v1 https://cmssdt.cern.ch/jenkins/job/cms-bot/2181354/parameters/ and think that caused the re-processing of files and comments. I will check why 2nd job was started with v1 |
|
yes if new bot v2 process ( e.g. https://cmssdt.cern.ch/jenkins/job/cms-bot/2181356/console ) the same PR then it does not re-read files and also does not edit the comment. Problem is that for some of the github web hooks we do not know the PR details ( e.g. when we update commit status) and we end up using v1 |
|
looks good, properly processed PR cms-data/MagneticField-Interpolation#8 . For more testing , lets get this merged and use it for already opened PRs with v2 |
|
@iarspider , do you have any pending changes or can I go ahead and merge it? |
|
@iarspider , looks like new bot does not recognize |
I will push a fix for that in a moment.
I think the error message is the same in v1, no? |
|
Pull request #2891 was updated. |
may be yes, but this should be fixed. error is for test parameters and they key there is |
|
@smuzaffar sure. Feel free to merge this once the checks pass. |
|
Pull request #2891 was updated. |
No description provided.