[
https://issues.apache.org/jira/browse/BEAM-14367?focusedWorklogId=767265&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-767265
]
ASF GitHub Bot logged work on BEAM-14367:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/May/22 15:29
Start Date: 06/May/22 15:29
Worklog Time Spent: 10m
Work Description: AnandInguva commented on PR #17569:
URL: https://github.com/apache/beam/pull/17569#issuecomment-1119742609
> Does this indicate the tested object is not thread safe or any indication
of defect on the sdk side, or is the test being flaky caused by the issue of
the test itself?
We suspect the timeout happens because the tests are run in parallel and may
be resources are used more. So, running this test case using no_xdist might
solve the flakiness.
Issue Time Tracking
-------------------
Worklog Id: (was: 767265)
Time Spent: 1h (was: 50m)
> Flaky timeout in github Python unit test action
> StatefulDoFnOnDirectRunnerTest.test_dynamic_timer_clear_then_set_timer
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-14367
> URL: https://issues.apache.org/jira/browse/BEAM-14367
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-core, test-failures
> Affects Versions: 2.39.0
> Reporter: Yi Hu
> Priority: P1
> Labels: flake
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Causing unit test failures in nightly
> [https://github.com/apache/beam/runs/6150980228?check_suite_focus=true#step:6:112]
> [https://github.com/apache/beam/runs/6143954692?check_suite_focus=true#step:6:308]
> [https://github.com/apache/beam/runs/6137479897?check_suite_focus=true#step:6:112]
>
> @pytest.mark.timeout(3)
> [118|https://github.com/apache/beam/runs/6137479897?check_suite_focus=true#step:6:118]
> def test_dynamic_timer_clear_then_set_timer(self):
> E Failed: Timeout >3.0s
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
