[internal/otelarrow] Flaky test disabled: TestIntegrationMemoryLimited #34719
Labels
Comments
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Since both hits are on Windows /label os:windows |
FYI: To add a label using automation, the |
|
Will take a look. |
|
I would like to recommend #34794, and if that fails I'll be glad to disable the test on Windows. Without trying to fix this, I'm not sure how we'd ever resolve it. |
|
Many test failures in Windows are due to the scheduling and the default time tick resolution being different than *nix. The sleep added in #34794 seems a reasonable try. |
|
I have added one Skip to this test, will leave this issue open. |
jmacd
changed the title
jpkrohling
added a commit
that referenced
this issue
Aug 27, 2024
…34794) **Description:** Fixes the causes of flakiness in most cases by using a callback to terminate the test without resorting to sleep statements. There is still one flaky test that for reasons not understood, does not pass. Fortunately, it fails in a repeatable way, and I will debug as part of #34719. **Link to tracking Issue:** #34719 --------- Signed-off-by: Juraci Paixão Kröhling <[email protected]> Co-authored-by: Juraci Paixão Kröhling <[email protected]>
codeboten
added a commit
that referenced
this issue
Sep 6, 2024
**Description:** Restore a skipped test, after understanding the nature of the problem. The problem was mostly addressed in #34794, which left the test disabled. The test had been flaky because while testing for an out-of-memory condition, the test could fail for timeout or other reason. To make the test more reliable, this now waits until at least one ArrowTraces span has been received by both components. After one span is available, it checks that the expected log messages are present on both sides. **Link to tracking Issue:** Fixes #34719. **Testing:** ✅ --------- Co-authored-by: Curtis Robert <[email protected]> Co-authored-by: Alex Boten <[email protected]>
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this issue
Sep 12, 2024
…pen-telemetry#34794) **Description:** Fixes the causes of flakiness in most cases by using a callback to terminate the test without resorting to sleep statements. There is still one flaky test that for reasons not understood, does not pass. Fortunately, it fails in a repeatable way, and I will debug as part of open-telemetry#34719. **Link to tracking Issue:** open-telemetry#34719 --------- Signed-off-by: Juraci Paixão Kröhling <[email protected]> Co-authored-by: Juraci Paixão Kröhling <[email protected]>
f7o
pushed a commit
to f7o/opentelemetry-collector-contrib
that referenced
this issue
Sep 12, 2024
**Description:** Restore a skipped test, after understanding the nature of the problem. The problem was mostly addressed in open-telemetry#34794, which left the test disabled. The test had been flaky because while testing for an out-of-memory condition, the test could fail for timeout or other reason. To make the test more reliable, this now waits until at least one ArrowTraces span has been received by both components. After one span is available, it checks that the expected log messages are present on both sides. **Link to tracking Issue:** Fixes open-telemetry#34719. **Testing:** ✅ --------- Co-authored-by: Curtis Robert <[email protected]> Co-authored-by: Alex Boten <[email protected]>
jriguera
pushed a commit
to springernature/opentelemetry-collector-contrib
that referenced
this issue
Oct 4, 2024
**Description:** Restore a skipped test, after understanding the nature of the problem. The problem was mostly addressed in open-telemetry#34794, which left the test disabled. The test had been flaky because while testing for an out-of-memory condition, the test could fail for timeout or other reason. To make the test more reliable, this now waits until at least one ArrowTraces span has been received by both components. After one span is available, it checks that the expected log messages are present on both sides. **Link to tracking Issue:** Fixes open-telemetry#34719. **Testing:** ✅ --------- Co-authored-by: Curtis Robert <[email protected]> Co-authored-by: Alex Boten <[email protected]>
|
This is still happening in Windows CIs though with different messages https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/11370646308/job/31630914777 |
mx-psi
pushed a commit
that referenced
this issue
Oct 29, 2024
#### Description Remove a flaky portion of the internal/otelarrow/test e2e test. #### Link to tracking issue Fixes #34719. #### Testing There was a time-based test that has proven unreliable. #### Documentation n/a
jpbarto
pushed a commit
to jpbarto/opentelemetry-collector-contrib
that referenced
this issue
Oct 29, 2024
…try#36034) #### Description Remove a flaky portion of the internal/otelarrow/test e2e test. #### Link to tracking issue Fixes open-telemetry#34719. #### Testing There was a time-based test that has proven unreliable. #### Documentation n/a
zzhlogin
pushed a commit
to zzhlogin/opentelemetry-collector-contrib-aws
that referenced
this issue
Nov 12, 2024
…try#36034) #### Description Remove a flaky portion of the internal/otelarrow/test e2e test. #### Link to tracking issue Fixes open-telemetry#34719. #### Testing There was a time-based test that has proven unreliable. #### Documentation n/a
sbylica-splunk
pushed a commit
to sbylica-splunk/opentelemetry-collector-contrib
that referenced
this issue
Dec 17, 2024
…try#36034) #### Description Remove a flaky portion of the internal/otelarrow/test e2e test. #### Link to tracking issue Fixes open-telemetry#34719. #### Testing There was a time-based test that has proven unreliable. #### Documentation n/a
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
internal/otelarrow
Describe the issue you're reporting
Hit on #34358 see https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/10203882356/job/28231140032?pr=34358#step:6:518
The text was updated successfully, but these errors were encountered: