-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow customising the bisect formatter #2978
Comments
Can you monkey patch |
That's still monkey patch... Just wondering if there is a more official way or should be an official support for this 😅 |
Eventually, if there's demand. I can't really remember this request popping up while I contribute to RSpec. It would be wonderful to describe your use case. |
@pirj thanks for your reply. The use case for us is to build a flaky test analyzer, which we first took out failed spec batches and put each one of them to our CI nodes with It would be nice if the bisect runner can have the same ability as normal runner to take formatters to register on different notifications and act on them accordingly. But since I am the only one request it for now, it's reasonable to just monkey patch the code on our end 👍 |
I think this is a reasonable request, the bisect formatter is not the same api as our normal formatters, but the same principles could be used to make this happen. I'm not sure it will be a priority for anyone on the core team but if you'd like to work on it @tubaxenor I'm happy to help review it. |
I can try spend some time and work on this later this month, thanks for reopen this 🙇 |
Currently bisect runner has 2 formatters: https://github.com/rspec/rspec-core/blob/main/lib/rspec/core/invocations.rb#L46-L47
Since they are not configurable, currently we can only parse the result from either stdout or monkey patch the formatter's
bisect_repro_command
method to get therepro
from bisect notifier: https://github.com/rspec/rspec-core/blob/main/lib/rspec/core/bisect/coordinator.rb#L35Is it currently possible to add customized formatters to bisect runner? Or is it ok to put up a PR to support this feature?
The text was updated successfully, but these errors were encountered: