-
-
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
Failures in test suite when using go 1.18 with Gitea 1.16.4 #19134
Comments
A few more pieces of information that might help us debug: as you are on arch, I assume that you are running these with go1.18 is this indeed the case? and, are you on amd64, arm64, or some other arch? |
I am trying to get gitea 1.16.4 on my Arch server to run and no matter what it just panics. I built it on the same server with go 1.18, nodejs 17.7.2 and npm 8.5.5.
Just tell me if you need anything else. I can provide you with some debug logs or anything, if you tell me what I need to do.
|
This is already fixed on master, #19100. @techknowlogick we maybe should release 1.16.5 as go1.18 is rolling out slowly. |
Not that it matters much now (at least it confirm), but yes go1.18 and amd64 (arm is a separate distro, at least for now). @Gusted Thanks, I can confirm that cherry-picking #19100 solves these failures as well as the one on start I had reported in #19135. Keep up the good work! |
That being said, the third failure still happens. It did not on my first attempt after backporting the fix, but then I wanted to remove the “expected failure” of tests from my build script and now it failed three times in a row (still re-running it, but no success so far). So seems to be an intermittent one, but not related to #19100? |
Gitea Version
1.16.4
Git Version
2.35.1
Operating System
Arch Linux
How are you running Gitea?
Not running, but building with:
Log Gist
https://gist.github.com/ArchangeGabriel/42e7699cce6dfbd6054566b0ceabdc2d
Description
Failure in
modules/lfs
:Failure in
routers/web/repo
:Failure in
services/migrations
:Those might be configuration issues of our tests environment, so I’m happy to try any suggestion.
The text was updated successfully, but these errors were encountered: