Skip to content

fix: longer timeout for notices in the testing environment #656

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

Merged
merged 1 commit into from
Jun 25, 2025

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Jun 24, 2025

We're observing a lot of these errors in our integration tests:

[09:29:38] Could not refresh notices: _ToolkitError: Network error: Request timed out

It could be that our timeout is too short on a heavily congested machine. Increase the timeout specifically for those cases to improve the reliability of our tests.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@rix0rrr rix0rrr requested a review from a team June 24, 2025 10:51
@rix0rrr rix0rrr temporarily deployed to integ-approval June 24, 2025 10:51 — with GitHub Actions Inactive
@aws-cdk-automation aws-cdk-automation requested a review from a team June 24, 2025 10:52
@github-actions github-actions bot added the p2 label Jun 24, 2025
@codecov-commenter
Copy link

codecov-commenter commented Jun 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.01%. Comparing base (9d2fff5) to head (72b2dc9).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #656   +/-   ##
=======================================
  Coverage   79.01%   79.01%           
=======================================
  Files          46       46           
  Lines        7085     7085           
  Branches      791      791           
=======================================
  Hits         5598     5598           
  Misses       1468     1468           
  Partials       19       19           
Flag Coverage Δ
suite.unit 79.01% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@mrgrain mrgrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a public facing fix or a chore?

// integration test environment, so wait for a longer timeout there.
//
// In production, have a short timeout to not hold up the user experience.
const timeout = process.env.TESTING ? 30_000 : 3_000;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have a more unique env name here? This name feels generic enough for customers to have it set in their enviornment.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was debating that. I was actually looking for something like CI, an officiously standardized environment variable, but couldn't find one.

Obviously I can turn it into CDK_TESTING if you'd prefer.

@rix0rrr
Copy link
Contributor Author

rix0rrr commented Jun 25, 2025

Is this a public facing fix or a chore?

I want to make sure it gets released, that's why it's a fix.

We're observing a lot of these errors in our integration tests:

```
[09:29:38] Could not refresh notices: _ToolkitError: Network error: Request timed out
```

It could be that our timeout is too short on a heavily congested
machine. Increase the timeout specifically for those cases to improve
the reliability of our tests.
@rix0rrr rix0rrr requested a review from mrgrain June 25, 2025 08:16
@aws-cdk-automation aws-cdk-automation added this pull request to the merge queue Jun 25, 2025
Merged via the queue into main with commit c29855e Jun 25, 2025
27 checks passed
@aws-cdk-automation aws-cdk-automation deleted the huijbers/inc-timeout branch June 25, 2025 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants