-
Notifications
You must be signed in to change notification settings - Fork 22
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
Set PREFECT_API_URL correctly during tests #5379
Conversation
e07159a
to
e4f97d6
Compare
CodSpeed Performance ReportMerging #5379 will not alter performanceComparing Summary
|
LGTM, but we're getting some scope mismatch on the fixtures so perhaps we need additional fixtures named after the scope. |
e4f97d6
to
cd4e0a7
Compare
cd4e0a7
to
0378e33
Compare
|
||
container.start() | ||
wait_for_logs(container, "Configure Prefect to communicate with the server") | ||
request.addfinalizer(cleanup) |
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.
Does the request.addfinalizer work in the same way when this function isn't a fixture? I'm not sure just wondering if the fixture decorator adds anything around this or if it's managed through the request object itself?
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 guess fixture decorator checks request object state when fixture function scope ends. So whereever we are mutating this object should not matter
Avoid running into
RuntimeError: Timed out while attempting to connect to ephemeral Prefect API server.
while testing locally.