We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
With the new logging of long running subtasks its sometimes unlcear, why a line was logged e.g.
myvm20 > ApacheBase > Rebuild myvm20 > ApacheBase > Rebuild [total=43.88s, verify=0.00s, update=43.88s, sub=NaN] myvm20 > ApacheBase [total=43.88s, verify=0.00s, update=NaN, sub=43.88s]
I think we should mark it more visible whether it was logged due to long running update/verify or due to something really was changed.
The text was updated successfully, but these errors were encountered:
With --predict-only: Not distinguishable, since update=NaN is always there.
--predict-only
Sorry, something went wrong.
No branches or pull requests
With the new logging of long running subtasks its sometimes unlcear, why a line was logged e.g.
I think we should mark it more visible whether it was logged due to long running update/verify or due to something really was changed.
The text was updated successfully, but these errors were encountered: