Skip to content

Conversation

silverwind
Copy link
Member

@silverwind silverwind commented Oct 19, 2022

This test is causing a lot of failures on CI and I'm not really motived to look into, so just skip it to make CI results more accurate.

Related: #19961

@silverwind silverwind added type/testing skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. labels Oct 19, 2022
@wxiaoguang
Copy link
Contributor

Hmm, I would prefer to find the root problem and fix the test instead of skipping it -- unless there is a strong reason that the test couldn't be fixed and must be skipped .....

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 20, 2022
@silverwind
Copy link
Member Author

As I see it, a randomly failing test just wastes everyone's time. It's worse than not being there in first place.

@silverwind
Copy link
Member Author

silverwind commented Oct 20, 2022

We should find a way to mark individual tests as flaky so that they will execute but not trigger a step failure.

@silverwind
Copy link
Member Author

Closing in favor of #21520.

@silverwind silverwind closed this Oct 20, 2022
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants