Thanks to visit codestin.com
Credit goes to github.com

Skip to content

chore: de-flake TestWorkspaceAgent_Metadata #7036

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
Apr 6, 2023
Merged

chore: de-flake TestWorkspaceAgent_Metadata #7036

merged 1 commit into from
Apr 6, 2023

Conversation

ammario
Copy link
Member

@ammario ammario commented Apr 6, 2023

No description provided.

@ammario ammario self-assigned this Apr 6, 2023
@ammario ammario requested a review from kylecarbs April 6, 2023 17:11
@ammario ammario enabled auto-merge (squash) April 6, 2023 17:11
Copy link
Member

@kylecarbs kylecarbs left a comment

Choose a reason for hiding this comment

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

Why is it important that we check the duration that occurred?

@ammario ammario merged commit 2637f55 into main Apr 6, 2023
@ammario ammario deleted the fix-flake branch April 6, 2023 17:20
@github-actions github-actions bot locked and limited conversation to collaborators Apr 6, 2023
@mafredri
Copy link
Member

mafredri commented Apr 6, 2023

This still seems to flake, the merge to main had such a flake.

@ammario
Copy link
Member Author

ammario commented Apr 6, 2023

@kylecarbs — it's not critical, and not worth a flake.

@mafredri — I see. We can remove these time checks altogether, disable them in CI, or maybe just disable t.Parallel here if in CI and Windows. What do you think?

@mafredri
Copy link
Member

mafredri commented Apr 6, 2023

@kylecarbs — it's not critical, and not worth a flake.

@mafredri — I see. We can remove these time checks altogether, disable them in CI, or maybe just disable t.Parallel here if in CI and Windows. What do you think?

Any of those sounds reasonable to me. I think as far as parallelism is concerned only linux runners are “safe”. Maybe another option is to skip if short test?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants