I've added e2e test for it with maxNumberOfProcess: 2, jobSize: 1 on 4 files for it b53b595 with kaizen 1, it seems cause error on CI (applied 2 rules), while working on locally.

Ref https://github.com/rectorphp/rector-src/actions/runs/16101183170/job/45430530419?pr=7046

It can possibly due to on CI, the cache overlapped call

I got it, it seems due to default CI use MemoryCacheStorage, I updated to use FileCacheStorage on e2e config and it seems working ok now 👍 https://github.com/rectorphp/rector-src/actions/runs/16101393029/job/45431005381?pr=7046

All checks have passed 🎉 @gharlan @TomasVotruba it is ready for review.

@TomasVotruba let's merge to have faster feedback to test ;)

Thanks! I tried it in my project (via rector/rector dev-main, which is already updated: rectorphp/rector@c243796).

The first run of rector process --kaizen=1 now works correctly 👍 Only one rule is applied. In my case that rule changed 16 files of 747.

$ rector process --kaizen=1
[EXPERIMENTAL] Running Kaizen mode. Only first 1 rule will be applied

 747/747 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%16 files with change

[...]

 [OK] 16 files have been changed by Rector

But the next run only "looks" at the 16 changed files:

$ rector process --kaizen=1
[EXPERIMENTAL] Running Kaizen mode. Only first 1 rule will be applied

 16/16 [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓] 100%

 [OK] Rector is done!

@gharlan thank you for verify, that's expected, or we may need to force clear cache when --kaizen used.

The combination with --clear-cache is needed for now, and we can discuss about whether cache need to be cleared when kaizen is used.

Please create new feature request for that so this can be discussed further.

nvm, I created PR for that :)

• [Kaizen] No need filter unchanged files when --kaizen is used #7050

This pull request has been automatically locked because it has been closed for 150 days. Please open a new PR if you want to continue the work.