Skip to content

fix: use europe-west4 region for agentic_rag E2E tests#799

Merged
eliasecchig merged 1 commit intomainfrom
fix/agentic-rag-e2e-region
Feb 17, 2026
Merged

fix: use europe-west4 region for agentic_rag E2E tests#799
eliasecchig merged 1 commit intomainfrom
fix/agentic-rag-e2e-region

Conversation

@eliasecchig
Copy link
Collaborator

Summary

  • Route agentic_rag E2E tests to europe-west4 instead of europe-west1

Problem

E2E builds for agentic_rag with vertex_ai_vector_search fail because the Vector Search Collections beta API (vectorsearch_v1beta) returns a 501/404 error in europe-west1, indicating the endpoint is not available in that region.

Changes

  • tests/cicd/test_e2e_deployment.py: Add agentic_rag to region routing logic so it uses europe-west4 where the API is supported

The Vector Search Collections beta API is not available in
europe-west1, causing E2E tests to fail with a 501/404 error.
Route agentic_rag tests to europe-west4 where the API is supported.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @eliasecchig, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses persistent failures in agentic_rag E2E tests that utilize vertex_ai_vector_search. The issue stemmed from the Vector Search Collections beta API not being available in the europe-west1 region, leading to 501/404 errors. The solution involves updating the test deployment logic to direct agentic_rag tests to the europe-west4 region, where the necessary API is fully supported, thereby ensuring test stability and reliability.

Highlights

  • E2E Test Region Fix: Agentic RAG E2E tests are now routed to "europe-west4" to resolve "Vector Search Collections beta API" ("vectorsearch_v1beta") 501/404 errors encountered in "europe-west1".
Changelog
  • tests/cicd/test_e2e_deployment.py
    • Added logic to route agentic_rag E2E tests to europe-west4.
Activity
  • No specific activity (comments, reviews, progress) has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request correctly changes the region for agentic_rag E2E tests to europe-west4 to resolve an API availability issue. The implementation is correct. I've added one suggestion to refactor the region selection logic using a dictionary, which will improve maintainability and make it easier to add other agent-specific regions in the future.

@eliasecchig eliasecchig merged commit f8273eb into main Feb 17, 2026
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant