Pass resource config URI to graph store networking integration test workers#666
Conversation
…orkers get_graph_store_info() reads get_resource_config() to build the readiness URI (added in #533), but the launched Vertex AI workers had no GIGL_RESOURCE_CONFIG_URI in their env, so they failed with "No resource config provided". Inject it via the compute pool's environment_variables, which launch_graph_store_job propagates to both compute and storage pools. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
/all_test |
GiGL Automation@ 23:38:48UTC : 🔄 @ 24:39:40UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:38:49UTC : 🔄 @ 23:49:04UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:38:51UTC : 🔄 @ 23:46:33UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:38:51UTC : 🔄 @ 01:39:03UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:38:51UTC : 🔄 @ 23:40:42UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:38:52UTC : 🔄 @ 24:54:24UTC : ✅ Workflow completed successfully. |
…test workers The test runner's resource config URI may be a local path that does not exist on the worker Docker image, so passing it directly to the workers via GIGL_RESOURCE_CONFIG_URI would not be readable. Instead, upload the in-memory resource config to the regional bucket (accessible to workers over GCS), pass that URI to the workers, and delete it in tearDown. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
/all_test |
GiGL Automation@ 23:41:35UTC : 🔄 @ 24:43:57UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:41:36UTC : 🔄 @ 23:49:21UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:41:36UTC : 🔄 @ 24:58:02UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:41:37UTC : 🔄 @ 01:38:09UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:41:39UTC : 🔄 @ 23:43:31UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 23:41:40UTC : 🔄 @ 23:51:00UTC : ✅ Workflow completed successfully. |
kmontemayor2-sc
requested review from
nshah-sc,
svij-sc,
xgao4-sc and
zfan3-sc
as code owners
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
4 participants
get_graph_store_info() reads get_resource_config() to build the readiness URI (added in #533), but the launched Vertex AI workers had no GIGL_RESOURCE_CONFIG_URI in their env, so they failed with "No resource config provided". Inject it via the compute pool's environment_variables, which launch_graph_store_job propagates to both compute and storage pools.
Scope of work done
Where is the documentation for this feature?: N/A
Did you add automated tests or write a test plan?
Updated Changelog.md? NO
Ready for code review?: NO