-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Flaky test TestReadRotatingFiles/MoveCreateTimestamped #1382
Comments
@djaglowski also failing TestReadRotatingFiles/CopyTruncateSequential and TestReadRotatingFiles/CopyTruncateTimestamped, see https://app.circleci.com/pipelines/github/open-telemetry/opentelemetry-collector-contrib/5531/workflows/0f13b749-d13c-4d69-9e25-1716c98cf061/jobs/42181
|
@djaglowski It failed again: https://app.circleci.com/pipelines/github/open-telemetry/opentelemetry-collector-contrib/5663/workflows/da080a18-0c5e-43de-9c71-e78b9563f0c8/jobs/43566 Can you have a look? We need a robust solution that is not timing or machine performance dependent. |
@tigrannajaryan I'll have another PR shortly. This test is something of a performance test, so I think that perhaps it does not really belong here. However, there are correctness aspects that I think can be preserved by substantially slowing down file rotation and reducing the number of lines written. This should still demonstrate the capability of handling file rotation correctly while also being orders of magnitude less sensitive to blips in underlying file system performance. Ultimately, I don't see a way to make this perfectly non-deterministic, but I think these changes will put it in line with any other test that has a fundamental dependendency on disk IO within a limited timeframe. The performance aspect of this can be duplicated later in the testbed, where longer file lifespans along with perhaps a trivial but non-zero margin of error would allow for acceptable stability. |
@tigrannajaryan My understanding of the root cause was incorrect. I will have a closer look at this tomorrow. |
* migrating CircleCI jobs to GitHub Actions * using container matrix instead * prevent entire workflow from stopping if one go version job fails * updating github ci to use setup-go * updating changelog
Occurred for #1348 here:
https://app.circleci.com/pipelines/github/open-telemetry/opentelemetry-collector-contrib/5514/workflows/72a3a765-14bf-447a-a710-31de95350478/jobs/41996
cc @djaglowski
The text was updated successfully, but these errors were encountered: