Skip to content

Update Combine method to treat warnings as failures and adjust tests (#37048)#37075

Merged
lunny merged 1 commit intogo-gitea:release/v1.25from
GiteaBot:backport-37048-v1.25
Apr 1, 2026
Merged

Update Combine method to treat warnings as failures and adjust tests (#37048)#37075
lunny merged 1 commit intogo-gitea:release/v1.25from
GiteaBot:backport-37048-v1.25

Conversation

@GiteaBot
Copy link
Copy Markdown
Collaborator

@GiteaBot GiteaBot commented Apr 1, 2026

Backport #37048 by @bircni

Treat Commit Status Warnings as errors

The root problem is that the definition of "warning" are different across systems.

  • Sometimes, "warning" is treated as "acceptable" (Gitea 1.25)
  • Sometimes, "warning" is mapped from "Result.UNSTABLE", which means "there are test failures" and it is "failure" in Gitea

To avoid breaking existing users, the best choice is to revert the behavior on Gitea side: treat "warning" as "error".

#37042 (comment)

fixes #37042

…o-gitea#37048)

Treat Commit Status Warnings as errors

> The root problem is that the definition of "warning" are different
across systems.
> 
> * Sometimes, "warning" is treated as "acceptable" (Gitea 1.25)
> * Sometimes, "warning" is mapped from "Result.UNSTABLE", which means
"there are test failures" and it is "failure" in Gitea
> 
> **To avoid breaking existing users, the best choice is to revert the
behavior on Gitea side: treat "warning" as "error".**


go-gitea#37042 (comment)

fixes go-gitea#37042

---------

Signed-off-by: Nicolas <bircni@icloud.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
@GiteaBot GiteaBot added the modifies/go Pull requests that update Go code label Apr 1, 2026
@GiteaBot GiteaBot added the modifies/go Pull requests that update Go code label Apr 1, 2026
@GiteaBot GiteaBot added this to the 1.25.6 milestone Apr 1, 2026
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Apr 1, 2026
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Apr 1, 2026
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 1, 2026
@bircni
Copy link
Copy Markdown
Member

bircni commented Apr 1, 2026

Why back port this?

@jpraet
Copy link
Copy Markdown
Member

jpraet commented Apr 1, 2026

Because it fixes a regression introduced in 1.25, which breaks jenkins integration.
I ran into this problem on my company instance after migrating from 1.24 to 1.25.
I think the 1.26 final will take some more weeks/months to be released?

@lunny lunny merged commit b0cc5cc into go-gitea:release/v1.25 Apr 1, 2026
26 checks passed
@wxiaoguang
Copy link
Copy Markdown
Contributor

I think the 1.26 final will take some more weeks/months to be released?

TBH it needs to "push" to make it release sooner, otherwise it will never be released.

@silverwind
Copy link
Copy Markdown
Member

I'm a strong proponent of fixed and predictable release cycles, but so far the owners have not followed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/go Pull requests that update Go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants