-
Notifications
You must be signed in to change notification settings - Fork 10
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
bug-1894282: Support gcp stage in systemtest #1002
Conversation
assert status_code == 504 | ||
assert status_code in ( | ||
# without LB, nginx drops the connection | ||
None, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What environment do we run the system tests in that doesn't have a load balancer, but does have nginx?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when i have a spare moment: local dev and CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand what that means. Does that mean you wrote up a bug to change the local dev environment such that it includes nginx running in local dev?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point, i have filed a bug about it https://bugzilla.mozilla.org/show_bug.cgi?id=1894955
We should support nginx without a cloud load balancer for a future where that bug is implemented.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
systemtest/test_env.sh
needs an env that points to the gcp stage urlsystemtest/test_content_length.py::TestContentLength::test_content_length_1000
needs to accept http 502 from google's load balancer, because it behaves differently from amazon load balancers.