Test Case 1: All Green

[oxve]

Verifying all green path for CI Shepherd.

Bug: 551996294

[github-actions]

🤖 Gemini Suggested Commit Message

---

ci: Mock build and test steps for CI Shepherd

Replace standard build and test execution steps in GitHub Actions with
mocked versions to facilitate CI Shepherd integration testing. This
allows for a fast and predictable "all green" path through the CI
pipeline without the overhead of full compilation or actual test
execution.

The update introduces a dedicated Python script to simulate job success
or failure and generates dummy artifacts to satisfy workflow
dependencies.

Bug: None

---

💡 Pro Tips for a Better Commit Message:

1. Influence the Result: Want to change the output? You can write custom prompts or instructions directly in the Pull Request description. The model uses that text to generate the message.
2. Re-run the Generator: Post a comment with: /generate-commit-message

[github-actions]

Context	State	Description
CI / android	✅ PASS	Passed
CI / linux	✅ PASS	Passed

[gemini-code-assist]

Code Review

This pull request mocks several GitHub Actions workflow steps—including GN generation, Ninja builds, browser tests, on-host tests, and artifact archiving—by replacing actual execution commands with a mock script (mock_step.py) and dummy artifact generation. The review feedback focuses on improving the robustness and portability of these mock implementations. Specifically, it suggests locating the configuration file relative to the script's path, handling relative paths safely in os.makedirs, using os.path.splitext to correctly parse filenames with multiple dots, and piping tar output to zstd to ensure cross-platform compatibility on macOS runners.

[gemini-code-assist]

Relying on GITHUB_WORKSPACE or the current working directory . makes the script less portable and harder to run or test locally. It is more robust to locate the configuration file relative to the script's own path using __file__.

    script_dir = os.path.dirname(os.path.abspath(__file__))
    config_path = os.path.abspath(os.path.join(script_dir, '..', 'config', 'mock_config.json'))

[gemini-code-assist]

If filepath is a relative path with no directory component (e.g., just a filename), os.path.dirname(filepath) will return an empty string. Calling os.makedirs('', exist_ok=True) will raise a FileNotFoundError. It is safer to check if the directory path is non-empty before calling os.makedirs.

Suggested change

	os.makedirs(os.path.dirname(filepath), exist_ok=True)
	dirname = os.path.dirname(filepath)
	if dirname:
	os.makedirs(dirname, exist_ok=True)

[gemini-code-assist]

Using filename.split('.')[0] to strip the file extension will incorrectly truncate filenames that contain multiple dots (e.g., foo.bar.test). Using os.path.splitext is the standard and robust way to separate a file's base name from its extension.

Suggested change

	test_name = filename.split('.')[0]
	test_name = os.path.splitext(filename)[0]

[gemini-code-assist]

Using tar --zstd is specific to GNU tar and may fail on macOS runners (which use BSD tar by default). To ensure cross-platform compatibility across different runner operating systems, you can pipe the tar output to zstd directly.

        tar -cf - dummy.txt | zstd -z > "${GITHUB_WORKSPACE}/artifacts/test_artifacts.tar.zstd"
        tar -cf - dummy.txt | zstd -z > "${GITHUB_WORKSPACE}/artifacts/cobalt_browsertests_deps.tar.zstd"