[rayci] 0 retries for exit code 42 (test failures)

[elliot-barn]

Removing buildkite job retries for exit code 42 (test failures) for cost savings
Retries are already enabled at the bazel test level and are configurable per job in the bk config

[gemini-code-assist]

Code Review

This pull request updates the automatic retry configuration in raycicmd/bk_pipeline.go to omit retries for test failures (exit status 42), since Bazel already handles them. The reviewer pointed out a minor typo in an inline comment ("exist status" instead of "exit status") and provided a code suggestion to fix it.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

There is a small typo in the inline comment: "exist status" should be "exit status" to match the terminology used elsewhere in the function.

Suggested change

	map[string]int{"exit_status": 1, "limit": 1}, // unknown exist status
	map[string]int{"exit_status": 1, "limit": 1}, // unknown exit status

[sai-miduthuri]

+1