- Notifications
You must be signed in to change notification settings - Fork927
test: ignore slog errors inTestUserLatencyInsights
#15105
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
johnstcn approved these changesOct 16, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Should we useslogtest.IgnoredErrorIs: []error{pq.ErrCanceled}
or similar instead?
I might be wrong, but it seems there isn't anything equivalent to // Common error typesvar (ErrNotSupported=errors.New("pq: Unsupported command")ErrInFailedTransaction=errors.New("pq: Could not complete operation in a failed transaction")ErrSSLNotSupported=errors.New("pq: SSL is not enabled on the server")ErrSSLKeyUnknownOwnership=errors.New("pq: Could not get owner information for private key, may not be properly protected")ErrSSLKeyHasWorldPermissions=errors.New("pq: Private key has world access. Permissions should be u=rw,g=r (0640) if owned by root, or u=rw (0600), or less")ErrCouldNotDetectUsername=errors.New("pq: Could not detect default username. Please provide one explicitly")errUnexpectedReady=errors.New("unexpected ReadyForQuery")errNoRowsAffected=errors.New("no RowsAffected available after the empty statement")errNoLastInsertID=errors.New("no LastInsertId available after the empty statement")) |
21feb42
intomain 30 checks passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spotted in:https://github.com/coder/coder/actions/runs/11362544440/job/31604644424
It looks like
TestUserLatencyInsights
failed due to a random error while reporting agent stats: