-
Notifications
You must be signed in to change notification settings - Fork 565
Integration tests failing locally on macOS #753
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
Comments
I just installed my new laptop with a new go installation (everything by default) and the test works without problems. Can you check if you have some specific configuration that we should be aware to replicate this behaviour? |
Hello, @taik0 Is your new laptop running macOS? I tried running the tests again on another laptop (my wife's), which is not used for development. Here’s what I did:
After this setup, I ran the tests, and they passed successfully. The only major difference between my laptop and hers is that mine has an Apple A1 chip, while hers has an Intel Core i9. In the meantime, I'm trying to figure out if there's another configuration causing this issue, maybe something related to IPv6. As soon as I have any updates, I'll share them here. Thanks for the help! |
My old laptop is a first-generation M1 (it works there), and the new one is a M4. |
Describe the bug
When running the integration tests for the Lura project, the tests fail due to an unexpected value in the X-Forwarded-For header. The tests expect this header to be an empty string (
[""]
), but it is set to["127.0.0.1"]
, causing the tests to fail.To Reproduce
Steps to reproduce the behavior:
/etc/hosts
:127.0.0.1 localhost
git clone https://github.com/luraproject/lura.git
cd lura
go build -v ./...
: Success!go test -cover -race ./...
: Success!go test -tags integration ./test
: Here is where it fails!Note that in all the tests that failed, the expected behavior was for the
X-Forwarded-For
header to be empty ([""]
), but it was populated with["127.0.0.1"]
.Expected behavior
The integration tests should pass successfully
Logs
The text was updated successfully, but these errors were encountered: