Skip to content
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

clarify log message #651

Merged
merged 1 commit into from
Apr 18, 2018
Merged

clarify log message #651

merged 1 commit into from
Apr 18, 2018

Conversation

willingc
Copy link
Collaborator

@willingc willingc commented Apr 17, 2018

The existing message log message can be misinterpreted to read that zero of 244 "scheduled for deletion" pods were deleted and implies that 244 more pods need deletion.

[I 2018-04-17 15:01:34 culler:143] Culling pods older than 06:00:00
[I 2018-04-17 15:01:34 culler:161] Deleted 0/244 pods

I understand that if one has context of the number of total pods then it may not be confusing. But if you don't know if there are 5000 pods or 244, it is easy to misinterpret. Recommend change:

[I 2018-04-17 15:01:34 culler:143] Culling pods older than 06:00:00
[I 2018-04-17 15:01:34 culler:161] Deleted 0 pods. Pod count=244

@willingc willingc requested a review from minrk April 17, 2018 16:53
@choldgraf
Copy link
Member

+1, this always confuses me :-)

@minrk minrk merged commit f06a7af into jupyterhub:master Apr 18, 2018
@willingc willingc deleted the log-deletepod branch April 18, 2018 13:13
@manics manics mentioned this pull request Aug 15, 2018
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants