Skip to content
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

test fail on Debian riscv64 arch #10347

Closed
yuzibo opened this issue Oct 3, 2022 · 5 comments
Closed

test fail on Debian riscv64 arch #10347

yuzibo opened this issue Oct 3, 2022 · 5 comments

Comments

@yuzibo
Copy link

yuzibo commented Oct 3, 2022

What version of Hugo are you using (hugo version)?

0.104.2

Does this issue reproduce with the latest release?

Hi, I noticed the hugo on Debian has a ftbfs issue on riscv64 arch:
https://buildd.debian.org/status/logs.php?pkg=hugo&arch=riscv64

I greped the failed test log on my locally real riscv64 hardware:

...
=== RUN   TestServerPathEncodingIssues/Windows_multilingual_404
    server_test.go:343:
        error:
          got non-nil error
        got:
          e`Get "http://localhost:36719/en/this/does/not/exist": dial tcp 127.0.0.1:36719: connect: connection refused`
        stack:
          /home/vimer/build/08/hugo-0.104.2/_build/src/github.com/gohugoio/hugo/commands/server_test.go:343
            c.Assert(err, qt.IsNil)
          /home/vimer/build/08/hugo-0.104.2/_build/src/github.com/gohugoio/hugo/commands/server_test.go:353
            func() {
                resp, err := http.Get(fmt.Sprintf("http://localhost:%d/%s", port, path))
                c.Assert(err, qt.IsNil)
                pr := pathResult{
                    statusCode: resp.StatusCode,
                }

                if err == nil {
                    defer resp.Body.Close()
                    pr.body = helpers.ReaderToString(resp.Body)
                }
                result.pathsResults[path] = pr
            }()
          /home/vimer/build/08/hugo-0.104.2/_build/src/github.com/gohugoio/hugo/commands/server_test.go:124
            r := runServerTest(c,
                serverTestOptions{
                    config:     config,
                    pathsToGet: []string{"en/this/does/not/exist", "es/this/does/not/exist"},
                },
            )

--- FAIL: TestServerPathEncodingIssues (1.35s)
    --- PASS: TestServerPathEncodingIssues/Unicode_paths (1.27s)
    --- FAIL: TestServerPathEncodingIssues/Windows_multilingual_404 (0.07s)
...
I want to dig into the reason why these cases will fail. any help will be appericated.

@yuzibo
Copy link
Author

yuzibo commented Oct 3, 2022

Maybe It has something with
#10314

@anthonyfok anthonyfok self-assigned this Oct 4, 2022
@anthonyfok anthonyfok added this to the v0.105.0 milestone Oct 4, 2022
@anthonyfok
Copy link
Member

Hi @yuzibo, thank you for reporting this issue. It is a duplicate of #10332.
Incidentally, the riscv64 build of hugo 0.104.2-1 finally built successfully on the eighth time.

Sorry for my tardiness in getting the fix ready; see #10356 pending the result of GitHub CI test and Debian buildd/CI results.

@yuzibo
Copy link
Author

yuzibo commented Oct 4, 2022

oh, thanks. I am going to close the issue before you did. But I am not sure how to build successfully on Debian riscv64 buildd machines.
Ok, great to hear your fix is ready, thanks again:)

@anthonyfok
Copy link
Member

@yuzibo Thanks for your reply!

But I am not sure how to build successfully on Debian riscv64 buildd machines.

As a DD with a Debian SSO certificate (or something like that), I am able to see a "giveback" link (e.g. https://buildd.debian.org/auth/giveback.cgi?pkg=hugo&arch=riscv64&suite=sid for riscv64) which resets it to BD-Uninstallable and then Needs-Build, so essentially a request for rebuild, so all I have been doing is to keep clicking that button when the build failed, and I did it 7 times for riscv64. I was curious to see if I could get all architectures to build successfully with enough number of rebuilds. (Silly me, eh? 😆)

Cheers!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants