-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Migration test failure #21739
Labels
Comments
techknowlogick
pushed a commit
that referenced
this issue
Nov 15, 2022
GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves #21739 Signed-off-by: Gary Moon <gary@garymoon.net>
@garymoon FWIW, I’m still seeing random failures at times while testing a fresh build. Since they are not 100 % reproducible, I just rerun the tests suite until it passes. If I still see some in the next release(s), I’ll try to see whether it’s always the same one or not and report. |
fsologureng
pushed a commit
to fsologureng/gitea
that referenced
this issue
Nov 22, 2022
…1824) GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net>
Codeberg-org
pushed a commit
to Codeberg-org/gitea
that referenced
this issue
Jan 18, 2023
…1824) GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net>
Codeberg-org
pushed a commit
to Codeberg-org/gitea
that referenced
this issue
Feb 23, 2023
…1824) GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net> (cherry picked from commit af149bd91f5b042ba108aa972eba832c0ce085b1)
xtexChooser
pushed a commit
to xtexChooser/central
that referenced
this issue
Nov 3, 2024
…#21824) GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea/gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net> (cherry picked from commit 40229a7)
xtexChooser
pushed a commit
to xtexChooser/central
that referenced
this issue
Nov 3, 2024
…#21824) GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea/gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net> (cherry picked from commit 40229a7)
xtexChooser
pushed a commit
to xtexChooser/central
that referenced
this issue
Nov 3, 2024
GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea/gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net>
xtexChooser
pushed a commit
to xtexChooser/central
that referenced
this issue
Nov 3, 2024
GitHub migration tests will be skipped if the secret for the GitHub API token hasn't been set. This change should make all tests pass (or skip in the case of this one) for anyone running the pipeline on their own infrastructure without further action on their part. Resolves go-gitea/gitea#21739 Signed-off-by: Gary Moon <gary@garymoon.net>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When running the drone pipeline either with
drone exec
or with a full Drone setup from a repo I reliably experience the following timeout during the migration unit tests.The closest I've come to identifying something similar is the third issue reported in #19134, but that issue went unreproduced and unresolved (@ArchangeGabriel did you happen to find a fix for this by any chance please?).
Any guidance on how I might go about addressing this would be much appreciated 💙
P.S. Should there be an "n/a" option on being able to repro an issue on try?
Gitea Version
cb83288 (main HEAD as of yesterday)
Git Version
git version 2.34.1
Operating System
Ubuntu 22.04
How are you running Gitea?
Via Drone.
The text was updated successfully, but these errors were encountered: