[release] Restrict requirements_py310 targets to amd64 Linux

[andrew-anyscale]

Add @platforms//cpu:x86_64 and @platforms//os:linux to exec_compatible_with
so the pip-compile binary and validation test only run on amd64 Linux.

Topic: fix-requirements-update-2
Relative: fix-requirements-update
Signed-off-by: andrew andrew@anyscale.com

[andrew-anyscale]

Reviews in this chain:
└#61713 [release] Restrict requirements_py310 targets to amd64 Linux

[andrew-anyscale]

#	head	base	diff	date	summary
0	8f672a92	eb2e201a	diff	Mar 12 20:21 PM	1 file changed, 10 insertions(+), 2 deletions(-)
1	9d2432c6	8b3f20fd	diff	Mar 13 9:17 AM	0 files changed
2	459a34e6	2662fb1b	rebase	Mar 16 8:43 AM	0 files changed
3	9760dfbe	68a622a6	diff	Mar 16 10:55 AM	0 files changed

[gemini-code-assist]

Code Review

This pull request restricts the requirements_py310.update and requirements_py310_test targets to run only on amd64 Linux by adding constraints to exec_compatible_with. The change is correct and aligns with the goal. I've added one suggestion to improve maintainability by reducing code duplication.

[gemini-code-assist]

To improve maintainability and reduce duplication, consider extracting this exec_compatible_with list into a variable, as it's also used in the requirements_py310.update target above.

For example, you could define a variable before these targets:

_requirements_py310_exec_compatible_with = [
    "//bazel:py310",
    "@platforms//cpu:x86_64",
    "@platforms//os:linux",
]

And then use exec_compatible_with = _requirements_py310_exec_compatible_with in both py_binary and py_test targets.

[aslonnie]

seems to have conflicts now?

why it needs to be limited to amd64 linux?

[andrew-anyscale]

I was running into issues earlier where greenlit was being removed from the generated file on aarch64, but kept on amd64. I went to repro, and I think it was actually an issue with Python version, as opposed to platform.

This is not the correct fix, so closing.