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

Values on the 'Requests Per Seconds' graph are incrementing each time I go into the same TeamCity build job run #29

Open
ChristopherCombes opened this issue Aug 6, 2020 · 2 comments

Comments

@ChristopherCombes
Copy link

Each time I view the same TeamCity build job in TeamCity the values on the 'Requests Per Seconds' graph increment. For example, I have a build job run called #0.1.0-US78726-Performance-Stress-Thread-Start-Analysis.1+230 at 6 Aug 13:4. I viewed the Requests Per Seconds graph and the 1st value of the graph was 1. In TeamCity I then clicked 'Artifacts'. 'More', 'Performance Statistics' and 'Show charts: Server Response Time & Requests Per Seconds >>', the Requests Per Seconds graph was shown again but each value in the graph was incremented. For example, the 1st value on the graph was now 2.

Initially I saw this issue in Chrome. Tried clearing cache. This didn't resolve the issue. Have also seen the issue in Internet Explorer too, so doesn't look like it is browser specific

Version of TeamCity being used is TeamCity Enterprise 2019.2.2 (build 71923).

@ChristopherCombes
Copy link
Author

Have managed to workaround the issue by
a) Restarting my PC and logging back on
b) Then opening Chrome, clearing cache, relogging back onto TeamCity

However I am still seeing the issue issue if I then move off the 'Performance Statistics' page and then move back onto it (without going through the workaround process)

@ChristopherCombes
Copy link
Author

Hmmmm - this morning tried the workaround of rebooting my PC and it didn't resolve the issue (ie the figures on the 'Requests Per Seconds' graph were still incorrectly incremented when I viewed them). What did get the figures to the correct values was viewing the 'Requests Per Seconds' graph for a different build job run and then viewing the 'Requests Per Seconds' graph for the original build job run again

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

No branches or pull requests

1 participant