Added 0 check before writeThroughpt calculation to prevent divide bytes written by 0

[Fred1155]

Motivation and Context

WRITE_THROUGHPUT metric is calculated to Double.Infinity, which cannot be emitted to EMF and is not true. This happen because when first byte time and last byte time are the same, we are dividing bytes written by 0.

Modifications

Added 0 check before bytespersec is invoked for writethroughpt

Testing

Added test case.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
24 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
1.5% Duplication on New Code

See analysis details on SonarQube Cloud