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

[CI][Windows] increase timeout to check run_worker process exit #3185

Conversation

kavilla
Copy link
Member

@kavilla kavilla commented Jan 5, 2023

Description

Increasing the timeout if platform is on Windows to 10 seconds from 5 seconds.

Origin:
https://github.com/opensearch-project/OpenSearch-Dashboards/actions/runs/3850790218/jobs/6561333017

In this run, the error:

ERROR UNHANDLED ERROR
ERROR Error: process did not automatically exit within 5 seconds, forcing exit
          at Timeout._onTimeout (D:\a\OpenSearch-Dashboards\OpenSearch-Dashboards\packages\osd-optimizer\src\worker\run_worker.ts:81:9)

Occurred for Windows when running:

node scripts/build_opensearch_dashboards_platform_plugins --no-examples --workers 10

The process appears not to end in the expected time given for the Windows CI and based on known performance issues, this increases the timeout for windows to allow for the Windows processes to attempt to naturally end within 10 seconds rather than 5 seconds.

Signed-off-by: Kawika Avilla kavilla414@gmail.com

Issues Resolved

n/a

Check List

  • All tests pass
    • yarn test:jest
    • yarn test:jest_integration
    • yarn test:ftr
  • New functionality includes testing.
  • New functionality has been documented.
  • Update CHANGELOG.md
  • Commits are signed per the DCO using --signoff

Increasing the timeout if platform is on Windows to 10 seconds from
5 seconds.

Origin:
https://github.com/opensearch-project/OpenSearch-Dashboards/actions/runs/3850790218/jobs/6561333017

In this run, the error:
```
ERROR UNHANDLED ERROR
ERROR Error: process did not automatically exit within 5 seconds, forcing exit
          at Timeout._onTimeout (D:\a\OpenSearch-Dashboards\OpenSearch-Dashboards\packages\osd-optimizer\src\worker\run_worker.ts:81:9)
```

Occurred for Windows when running:
```
node scripts/build_opensearch_dashboards_platform_plugins --no-examples --workers 10
```

The process appears not to end in the expected time given for the Windows CI and based on known
performance issues, this increases the timeout for windows to allow for the Windows processes
to attempt to naturally end within 10 seconds rather than 5 seconds.

Issue:
n/a

Signed-off-by: Kawika Avilla <kavilla414@gmail.com>
@kavilla kavilla force-pushed the avillk/inc-timeout-for-run-worker branch from 3ff058c to 0929df1 Compare January 5, 2023 23:24
@joshuarrrr
Copy link
Member

Do we have evidence of this happening in both main and 2.x branches?

@codecov-commenter
Copy link

Codecov Report

Merging #3185 (0929df1) into main (038968d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3185   +/-   ##
=======================================
  Coverage   66.53%   66.53%           
=======================================
  Files        3200     3200           
  Lines       61249    61249           
  Branches     9426     9426           
=======================================
  Hits        40753    40753           
  Misses      18247    18247           
  Partials     2249     2249           
Flag Coverage Δ
Linux 66.48% <ø> (ø)
Windows 66.48% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@kavilla
Copy link
Member Author

kavilla commented Jan 6, 2023

Do we have evidence of this happening in both main and 2.x branches?

it might be because the retry is on main only so we dont see this happening often in the CI for main

@kavilla
Copy link
Member Author

kavilla commented Jan 6, 2023

Closed in favor of: #3193

@kavilla kavilla closed this Jan 6, 2023
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

Successfully merging this pull request may close these issues.

3 participants