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
TestServerPathEncodingIssues/{Unicode_paths,Windows_multilingual_404} often fail (seen on Debian buildd) #10332
Comments
Yea, that test has been flaky on GitHub CI as well so I don't mind it if we somehow only run it locally and on GitHub ... or something, |
The test has been flaky on my (somewhat old) local laptop too. After some debugging, it seems that no 567 milliseconds or (for CI) 2 seconds wait is added because |
Set getNumHomes: 1 to enable 567 ms or 2 s of wait for the server to be ready in TestServerPathEncodingIssues/Unicode_paths and TestServerPathEncodingIssues/Windows_multilingual_404. Fixes gohugoio#10332
Set getNumHomes: 1 to enable 567 ms or 2 s of wait for the server to be ready in TestServerPathEncodingIssues/Unicode_paths and TestServerPathEncodingIssues/Windows_multilingual_404. Fixes gohugoio#10332
Set getNumHomes: 1 to enable 567 ms or 2 s of wait for the server to be ready in TestServerPathEncodingIssues/Unicode_paths and TestServerPathEncodingIssues/Windows_multilingual_404. Fixes #10332
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
It looks like TestServerPathEncodingIssues/Windows_multilingual_404 in v0.104.0 is another "flaky" test (see 08f0984) , failing on the first try on armel and s390x architectures on Debian buildd machines:
I tried rebuilding (or "giveback" in Debian-speak), but surprisingly to me, the test failed consistently on armel and s390x (and ppc64)
Don't know why yet; I'll try again on Debian porterbox machines for armel and s390x and see if I could reproduce the error.
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
YesNot sure, only tested with v0.104.0; will test with v0.104.1 soon.The text was updated successfully, but these errors were encountered: