-
Notifications
You must be signed in to change notification settings - Fork 28
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
Log output understanding question #159
Comments
@mobilutz thanks for raising the issue. 👍 The bit you quoted is referring to other messages that come from L113 in the same file. Basically, the command displayed below the message you are quoting would run all the test files assigned to a particular CI node, while the previous commands run just subsets of those (as retrieved from the API queue on each request). We agree the turn of phrase is not particularly legible there. I'm going to prepare a change for this shortly. :-) |
Doesn't the case statement prevent the output of L113 and L115 at the same time? But 👍🏻 and thanks on a wording change to make it more understandable! |
Yes, it does. However, we expect this code to usually be run multiple times in the Queue Mode, resulting in multiple outputs (with the one from L115 coming last) - hence the reference to the commands "above". :-) |
@mobilutz We've released a new knapsack_pro version 3.1.1 with updated messages. |
I am seeing output from this line in our CI logs, and want to know what it means:
It comes form here:
knapsack_pro-ruby/lib/knapsack_pro/runners/queue/rspec_runner.rb
Line 115 in 3aa4192
There seems to be something wrong with this sentence, especially here:
... fetched from API queue then above after each request ...
I would like to support, but I don't know what exactly this sentence means.
The text was updated successfully, but these errors were encountered: