fix tests

[loosebazooka]

looks like the string format changed

[gemini-code-assist]

Summary of Changes

Hello @loosebazooka, I'm Gemini Code Assist¹! 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 resolves a test failure by updating the expected error message pattern in a shell script. The change ensures that the test for platform mismatch scenarios continues to function correctly, adapting to a recent modification in the output string format of the container-structure-test utility.

Highlights

• Test Fix: Updated the regular expression in tests/structure_test_tests.sh to correctly match a changed error message format from the container-structure-test tool. This specifically addresses the platform mismatch test case.

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. ↩

[gemini-code-assist]

Code Review

This pull request fixes a failing test by updating the regular expression used to match an error message. The change correctly reflects the new error message format. I've added one suggestion to improve the readability and maintainability of the test script by extracting the long and complex regular expression into a variable.

[gemini-code-assist]

This line is very long and contains a complex regular expression, which makes it hard to read and maintain. Consider extracting the regex pattern into a variable on a separate line for better readability.

For example:

local expected_pattern="image\ with\ reference.+was\ found\ but\ its\ platform\ \(linux\/${go_architecture}\)\ does\ not\ match\ the\ specified\ platform\ \(linux\/riscv64\)"
if ! [[ "$res" =~ $expected_pattern && "$code" == "1" ]]; then

This makes the if condition much clearer.

[loosebazooka]

the repo isn't set up for modern bazel, but the actual tests are passing, so I'll merge this when ready.

[loosebazooka]

looks like macos12 is out of comission and macos15 still has no docker support until github upgrades to m3. I'll remove the requirement for now.