-
Notifications
You must be signed in to change notification settings - Fork 44
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
fix: Resolve failing HTTP API tests via cleanup #557
Conversation
Benchmark ResultsSummary
✅ See Better Results...
❌ See Worse Results...
✨ See Unchanged Results...
🐋 See Full Results...
|
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.
LGTM.
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.
Nice - thanks Orpheus!
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.
👍
Relevant issue(s)
Resolves #555
Description
Various tests of the HTTP API were failing because they were assuming
env
was defined (to valuedev
), which is the case in the normal execution order as some previous tests set the global to that value, but not in a random execution order of tests.This PR simply, whenever it is required, sets the
env
value and cleans it up afterwards.I suggest that a future PR should improve on the global
env
pattern, e.g. after the config PR merges...Tasks
How has this been tested?
Int. tests.
Specify the platform(s) on which this was tested: