Théo FIDRY

>AFAIK, I was unable to use that option. How come? 🤔

Indeed, unfortunately the docs are not versioned :/

Related https://github.com/composer/composer/issues/11325

I think it is still useful to display the logging for the requirement checker for debugging purposes though. Would be putting via an environment variable acceptable?

>Say you in the future add the ability to make a self-executing PHAR In this case I think you make sure that the shipped PHP version contains the required versions...

Could you try to enable the extra logging (for the log file) and run it with both no parallel and parallel and compare the results for a mutant that has...

>From a DX perspective I'm wondering whether we can improve this by detecting the situation. I think the easiest way would be to have tests running in parallel in the...

I'll check this ASAP, but I would highly recommend Behat to do a smoke test of the PHAR at least, e.g. calling `behat.phar --version`, as part of the CI

Looking at [this](https://github.com/stof/Behat/blob/7470472ccbb346928a248cf86fa1222cf28f3460/.github/workflows/build.yml#L104C61-L104C65) it's not really worth for me to try to investigate this any further. I'm happy to help if there is issues with upgrading, but I'm not willing...

Hmm I'm looking at the produced PHAR there is definitely something _very_ weird, need to check some more. It's the sort of error that if it was produced on the...