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

Failure events not being recorded #979

Closed
ghost opened this issue Mar 14, 2019 · 5 comments
Closed

Failure events not being recorded #979

ghost opened this issue Mar 14, 2019 · 5 comments

Comments

@ghost
Copy link

ghost commented Mar 14, 2019

Description of issue

I have locust 0.9.0 installed in a OracleLinux7 Docker image along with Python 2.7 with all dependencies. When I run this image in a container on Mac-OS, all events (both success and failure) are recorded and counted in the summary report properly. Failures also appear with detail information at the end of the summary report. Exporting the same image to a OracleLinux7 system and running it in a Docker container results in different behavior. No failures are reported and everything appears as a success in the summary report. No failures appear in the summary. However, viewing the Grafana metrics there are indeed failures appearing which are reported by the application under test. All tests are run against the same server and application. The only obvious difference is differing Docker versions on the host.

Expected behavior

Regardless of where the Docker image is run, Locust reports should reliably show success and failure metrics.

Actual behavior

Summary information is correct running the Docker image in a container under Mac-OS but missing information when the same Docker image is run in a container on Oraclelinux.

Environment settings

  • OS: OracleLinux7 in the Docker image
  • Python version: 2.7
  • Locust version: 0.9.0
@cgoldberg
Copy link
Member

not enough info.

@ghost
Copy link
Author

ghost commented Mar 18, 2019

What info is needed?

@cgoldberg
Copy link
Member

@ghost ghost closed this as completed Mar 19, 2019
@ghost
Copy link
Author

ghost commented Mar 19, 2019

Unable to provide a reproducible example because the issue only appears on a proprietary server.

@cgoldberg
Copy link
Member

sorry, it's not possible for us to be of any further help.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants