-
Notifications
You must be signed in to change notification settings - Fork 340
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
Failing test #1523
Comments
I have tested under alpine-3.17.2 (aarch64) and go1.19.6 (alpinelinux package) and I have no errors. I think the errors are not related to alpinelinux, but due to yaegi repo probably not installed at |
Thanks for the explanation. I moved the cloned repo to the suggested path and the tests ran successfully. Would you consider adding this note into contributing / building from source guideline? That would be helpful. Then, this issue can be closed. Also can you look into the |
I will update the readme to document the constraint on repo path. I'm running on alpinelinux and can totally run You mention |
Yes, nothing goes wrong when we run the command manually with default Go package in AlpineLinux.
https://git.alpinelinux.org/abuild/tree/abuild.conf#n5 It is set in
|
This should allow to build the package on AlpineLinux. Also document the constraint of having to install the source under $GOPATH/src/github.com/traefik/yaegi until Go modules are supported. Fixes traefik#1523.
This should allow to build the package on AlpineLinux. Also document the constraint of having to install the source under $GOPATH/src/github.com/traefik/yaegi until Go modules are supported. Fixes #1523.
The following program
sample.go
triggers an unexpected resultExpected result
Running `go test ./...` passed.
Got
Yaegi Version
0.15.0
Additional Notes
I'm trying to package
yaegi
for AlpineLinux, but my local build are failing (see the log above).Also, it would be nice to have race optional when running test. AlpineLinux (and a few other distros) set
-buildmode=pie
that forbid-race
flag.yaegi/cmd/yaegi/yaegi_test.go
Line 54 in da03c92
The text was updated successfully, but these errors were encountered: