Fixes #39315 - Change rake task 'verbose' parameter#938
Conversation
44c5754 to
2c8fc02
Compare
|
Before After Well it does change things, but according to the source it shouldn't be necessary? Have you found out why it doesn't work anymore? |
I have relied on the bug explanation tbh: https://projects.theforeman.org/issues/39248 While this PR sure does not redesign or modernize the test suite, it at least unblocks the failing CI tests. |
Something along the way seems to interpret the Looking at the Before and After output, it seems to me that the IMHO this PR fixes the pipeline for now so 👍 |
|
@nadjaheitmann which rake version are you using? ruby/rake@5886caa fixed a regression in Rake 13.4.0/13.4.1. |
In this run, we have the pipeline failing and use rake 13.4.2: https://github.com/theforeman/smart-proxy/actions/runs/25096463025/job/73534458532#step:5:243 I started that run on this branch but with the fix commit reverted to double-check the issue was actually solved by the fix. |
|
Reading through the issue description, @ogajduse proposed a fix directly in ci-reporter/ci_reporter_test_unit#13 which is closer to the root cause of the problem than this PR which is more targeted at resolving the symptoms. But it is very unlikely to be merged given the project has not received any changes during the last 10 years. |
|
@adamruzicka @ekohl I can see that pipelines are still broken. Should this be merged as a temporary solution for the pipeline to turn green or is there some other effort coming in soonish, that will supersede this PR? |
|
Not blocking this merge (since it's easy to cherry pick), but longer term we should evaluate migrating from test-unit to minitest which aligns with foreman. Having a common testing framework is IMHO a good thing. We previously discussed that briefly on Matrix, but that gets lost easily so noting it here. |
In that case, I'd recommend creating a new Redmine issue as the one it's currently linked to aims to implement the long-term solution. |
Good enough if I change 'Fixes' to 'Refs'? It literally fixes what is written in the title :) |
But then the text proposes a completely different solution which leaves it in a weird place.
I'm not sure if it wouldn't confuse prprocessor. I'd opt for a separate issue, even if just to stay on the safe side. |
The verbose option does not work anymore, so we have to explicitly pass the '--verbose' option now.
2c8fc02 to
f0185df
Compare
I created a new issue and just copied over part of the issue description. IMO, it makes sense to change the title of https://projects.theforeman.org/issues/39248 to something more fitting, e.g.
I'd assume it would be fine :) Now, we might need to remove the PR from the 'old' issue manually. I don't think it is updated automatically, is it? Edit: I was able to delete the PR from issue 39248 . |
|
Thank you @nadjaheitmann ! |
|
Backported to 3.19-stable in #942 |
The verbose option does not work anymore, so we have to explicitly pass the '--verbose' option now.