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

fix flaky insert notify limiter test #391

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

bgentry
Copy link
Contributor

@bgentry bgentry commented Jun 12, 2024

The insert notify limiter uses the FetchCooldown setting for its own debounce interval. This defaults to 100ms, which is short enough to occasionally fail in GitHub Actions when testing two trigger attempts back to back.

Failed on this run:

        client_test.go:1480: 
            	Error Trace:	/home/runner/work/river/river/client_test.go:1480
            	Error:      	Should be false
            	Test:       	Test_Client_InsertMany/DoesNotTriggerInsertNotificationForNonAvailableJob

The insert notify limiter uses the FetchCooldown setting for its own
debounce interval. This defaults to 100ms, which is short enough to
occasionally fail in GitHub Actions when testing two trigger attempts
back to back.
@bgentry bgentry requested a review from brandur June 12, 2024 04:10
@bgentry bgentry merged commit cb43f2c into master Jun 12, 2024
10 checks passed
@bgentry bgentry deleted the bg-fix-flaky-insert-notify-limiter-test branch June 12, 2024 04:47
bgentry added a commit that referenced this pull request Jun 12, 2024
Just as in #391, the insert notify limiter uses the FetchCooldown
setting for its own debounce interval. This defaults to 100ms, which is
short enough to occasionally fail in GitHub Actions when testing two
trigger attempts back to back.
bgentry added a commit that referenced this pull request Jun 12, 2024
* add JobDelete / JobDeleteTx APIs to Client

This adds new APIs to permanently delete a job from the job table, so
long as it is not currently running.

* fix another flaky insertNotifyLimiter test

Just as in #391, the insert notify limiter uses the FetchCooldown
setting for its own debounce interval. This defaults to 100ms, which is
short enough to occasionally fail in GitHub Actions when testing two
trigger attempts back to back.

* Update ErrJobRunning text

Co-authored-by: Brandur Leach <brandur@brandur.org>

---------

Co-authored-by: Brandur Leach <brandur@brandur.org>
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.

2 participants