[BUG] transient error FAIL: TestAPITeam 404 Not Found #111
Labels
No Label
backport/v1.19
backport/v1.20
backport/v1.21
bug
dependency
Chi
dependency
Chroma
dependency
citation.js
dependency
devcontainers
dependency
dropzone
dependency
F3
dependency
ForgeFed
dependency
garage
dependency
Gitea
dependency
Go-org
dependency
Golang
dependency
goldmark
dependency
Goth
dependency
Helm
dependency
MariaDB
dependency
Mermaid
dependency
minio-go
dependency
Monaco
dependency
PDFobject
dependency
Runner
dependency
ssh
dependency
urfave
dependency
Woodpecker CI
dependency
XORM
Discussion
duplicate
enhancement/feature
forgejo/accessibility
forgejo/actions
forgejo/branding
forgejo/ci
forgejo/documentation
forgejo/federation
forgejo/furnace cleanup
forgejo/internationalization
forgejo/moderation
forgejo/privacy
forgejo/release
forgejo/scaling
forgejo/security
forgejo/ui
issue
closed
issue
do-not-exist-yet
issue
open
OS
FreeBSD
OS
Linux
OS
MacOS
OS
Windows
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: forgejo/forgejo#111
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Upstream reference
Description
Another instance today at https://forgejo-ci.codeberg.org/forgejo/forgejo/pipeline/35/21
Might be fixed by this patch:
I suspect because if it doesn't specify any paramaters it could happen that another TeamUser is given back, which might not be the TeamUser the code is expecting. I will open a PR at Gitea to change this.
https://github.com/go-gitea/gitea/pull/22192
[CI] transient error FAIL: TestAPITeam 404 Not Foundto [BUG] transient error FAIL: TestAPITeam 404 Not FoundAnd... the fix was merged into go-gitea:main on upstream
90572c5a22
.Thanks to @Gusted and the Gitea team for acting quickly on this.
BTW shortly after another fix was merged, which relates to testing as well Attempt to fix TestExportUserGPGKeys (#22159)
Interestingly this other transient failure never showed on Forgejo. 🤷
It was just a sidenote as I've seen it in the commit history when picking up the link to the fix we need, and thought "it hasn't bitten us yet, but there is a reason they fix it, so we could potentially also downstream that one while we are at it and avoid the next transient failure before it hits us.."
Both commits should be downstreamed on the next rebase of Gitea.
It is set to happen this saturday.