Skip to content

fix: Add https readiness check for rest-registry tests#5978

Open
ntkathole wants to merge 1 commit intofeast-dev:masterfrom
ntkathole:wait_rest
Open

fix: Add https readiness check for rest-registry tests#5978
ntkathole wants to merge 1 commit intofeast-dev:masterfrom
ntkathole:wait_rest

Conversation

@ntkathole
Copy link
Member

@ntkathole ntkathole commented Feb 17, 2026

What this PR does / why we need it:

This PR adds an HTTP readiness poll to the test fixture in sdk/python/tests/integration/registration/rest_api/test_registry_rest_api.py. It poll the HTTP endpoint until it returns a non-502 response.

Which issue(s) this PR fixes:

Fixes #5977


Open with Devin

Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
@ntkathole ntkathole self-assigned this Feb 17, 2026
@ntkathole ntkathole requested a review from a team as a code owner February 17, 2026 11:06
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

Open in Devin Review

@ntkathole
Copy link
Member Author

Logs from run:

Waiting for HTTP endpoint to become ready (timeout=120s): http://feast.kind.test/api/v1/projects
 HTTP endpoint is ready (status=200)

 Connected to Feast REST at: http://feast.kind.test/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

registry-rest-api-tests CI workflow sometimes fails due to missing HTTP readiness check

1 participant