Conversation
Adapt the /codex-verify slash command from the BAGL repo to target GiGL directly: update the preamble to reference GiGL instead of BAGL, remove the submodule warning, and rewrite the full-scope directory list and find commands to match GiGL's actual project structure. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
/all_test |
GiGL Automation@ 19:54:04UTC : 🔄 @ 21:18:58UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 19:54:04UTC : 🔄 @ 20:03:10UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 19:54:06UTC : 🔄 @ 21:16:24UTC : ✅ Workflow completed successfully. |
GiGL Automation@ 19:54:06UTC : 🔄 @ 20:01:21UTC : ❌ Workflow failed. |
GiGL Automation@ 19:54:07UTC : 🔄 @ 21:00:05UTC : ✅ Workflow completed successfully. |
mkolodner-sc
left a comment
There was a problem hiding this comment.
Thanks for the work Kyle! This generally LGTM, one note is that it's not immediately clear where the metrics can be found (i.e. how do we locate https://console.cloud.google.com/vertex-ai/metadata/locations/us-central1/metadata-stores/default/artifacts/3974059031304843089?project=external-snap-ci-github-gigl, or should they be referencing gs://gigl-cicd-perm/hom_cora_sup_test_on_20260303_200910/trainer/models/trainer_eval_metrics.json in the pipeline you linked).
Can we add some notes to the two example files about where the metrics are exported to and how they can be accessed?
|
/e2e_test |
GiGL Automation@ 21:02:07UTC : 🔄 @ 22:21:52UTC : ❌ Workflow failed. |
Scope of work done
We should support this, for now we only have Loss as a metric. See https://console.cloud.google.com/vertex-ai/pipelines/locations/us-central1/runs/hom-cora-sup-test-on-20260303-200910?project=external-snap-ci-github-gigl which produces https://console.cloud.google.com/vertex-ai/metadata/locations/us-central1/metadata-stores/default/artifacts/3974059031304843089?project=external-snap-ci-github-gigl which records loss
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