Commit 86f4799
authored
Increase context deadline for TestTaskQueueAPIRateLimitOverridesWorkerLimit (temporalio#8696)
## What changed?
Increase flakiness buffer for
TestTaskQueueAPIRateLimitOverridesWorkerLimit
## Why?
It was still flaky at 3.5s
## How did you test it?
- [ ] built
- [ ] run locally and tested manually
- [ ] covered by existing tests
- [ ] added new unit test(s)
- [ ] added new functional test(s)
## Potential risks
Increasing the flakiness buffer too far could eventually mean this test
is worthless. I think 5s is ok though and still tests the rough shape of
the API.
<!-- CURSOR_SUMMARY -->
---
> [!NOTE]
> Increase buffer/timeout for the task-queue API rate-limit test and
adapt chasm parent-pointer test to Get() no-error API.
>
> - **Tests**:
> - **Task queue rate limiting**
(`tests/TaskQueueSuite.TestTaskQueueAPIRateLimitOverridesWorkerLimit`):
> - Increase flakiness buffer to `3.75s` and extend `drainTimeout` to
`30s`.
> - Add notes explaining increased buffer/timeout due to flakiness.
> - **Chasm tree tests** (`chasm/tree_test.go`):
> - Update `assertParentPointer` to use `Get(chasmContext)` without
error returns for `SubComponent1` and `SubComponent11`.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
f876389. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->1 parent a80b487 commit 86f4799
1 file changed
+7
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
261 | 261 | | |
262 | 262 | | |
263 | 263 | | |
| 264 | + | |
| 265 | + | |
| 266 | + | |
| 267 | + | |
264 | 268 | | |
265 | 269 | | |
266 | 270 | | |
267 | 271 | | |
268 | | - | |
| 272 | + | |
269 | 273 | | |
270 | 274 | | |
271 | 275 | | |
| |||
283 | 287 | | |
284 | 288 | | |
285 | 289 | | |
286 | | - | |
| 290 | + | |
| 291 | + | |
287 | 292 | | |
288 | 293 | | |
289 | 294 | | |
| |||
0 commit comments