Skip to content

Correctly log how long it took to close transports#1539

Merged
michaelbaamonde merged 1 commit intoelastic:masterfrom
michaelbaamonde:fix-close-transports-logging-bug
Jul 8, 2022
Merged

Correctly log how long it took to close transports#1539
michaelbaamonde merged 1 commit intoelastic:masterfrom
michaelbaamonde:fix-close-transports-logging-bug

Conversation

@michaelbaamonde
Copy link
Copy Markdown
Contributor

The load driver incorrectly logs a negative number when reporting how long it took to shut down transports. Example:

2022-07-07 14:49:27,475 ActorAddr-(T|:37235)/PID:2900742 esrally.driver.driver INFO Total time to close transports: -0.000971 seconds.

This PR fixes this, resulting in logs like this:

2022-07-07 14:56:28,700 ActorAddr-(T|:40609)/PID:2902950 esrally.driver.driver INFO Total time to close transports: 0.000797 seconds.

@michaelbaamonde michaelbaamonde added bug Something's wrong :misc Changes that don't affect users directly: linter fixes, test improvements, etc. cleanup Linter changes, reformatting, removal of unused code etc. labels Jul 7, 2022
@michaelbaamonde michaelbaamonde requested a review from pquentin July 7, 2022 15:02
Copy link
Copy Markdown
Member

@pquentin pquentin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, so this was the issue! I've always wondered. Thanks.

@michaelbaamonde michaelbaamonde merged commit 3d8d7bc into elastic:master Jul 8, 2022
@pquentin pquentin added this to the 2.7.0 milestone Nov 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something's wrong cleanup Linter changes, reformatting, removal of unused code etc. :misc Changes that don't affect users directly: linter fixes, test improvements, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants