Closed alex-kovshovik closed 1 year ago
Hi @alex-kovshovik
Thanks for reporting the problem.
I found out it's caused by RSpec::Core::RakeTask
that we use in Regular Mode. It works in verbose mode by default.
https://stackoverflow.com/a/26299828/905697
I prepared an improvement here.
I'll get back to you when we release it publicly.
Wow @ArturT, I didn't expect your response so fast! Thank you so much!
@alex-kovshovik Please update the knapsack_pro gem to 3.9.0 version. It respects the warn level and suppresses the RSpec command on the output.
Thank you @ArturT, we just upgraded and it works!
We (Decisely) use knapsack_pro gem for a long time (years now), and it's been solid! We never had issues with KnapsackPro service being down, never had problems with running older versions of the gem. This is the best open-source solution to spread our large test suite across nodes in our GitLab CI. Thank you!
The one issue that's not really a bug, it's just an annoyance: we have a lot of spec files, and when KnutsackPro runs them using
rake spec
- it outputs all these file names to STDOUT, which in our case is several pages out output. So whenever a test fails in CI, a developer must scroll a lot to find it in the CI output.I changed the KnapsackPro logging level to "warn" with
KNAPSACK_PRO_LOG_LEVEL: "warn"
and it helped, but stillbundle exec rails knapsack_pro:rspec
prints out ALL file names.Question: How can I suppress the output of the file names?
Example output:
Thank you!