Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: target_compatible_with excluding arm64 #84

Merged

Conversation

jjmaestro
Copy link
Contributor

ci: update ci and exclude windows (#82) added target_compatible_with arguments to some of the tests restricting them to linux but it also forced amd64 instead of allowing the tests to run in both linux/amd64 and linux/arm64.

Before this fix, I would get SKIPPED tests when testing on linux/arm64 and now all the tests run.

I've also noticed that the locks were not updated and would produce side-effects so I've added a separate chore commit to make sure there's "no noise" in the commit and/or when running the tests or other code in the repo.

The 'ci: update ci and exclude windows' commit added
'target_compatible_with' arguments to some of the tests restricting them
to linux but it also forced amd64 instead of allowing the tests to run
in both linux/amd64 and linux/arm64.

Before this fix, I would get SKIPPED tests when testing on linux/arm64
and now all the tests run.
Just doing 'bazel run' on the locks (except apt_security which is
lock-less) and runnign the tests for linux/amd64 and linux/arm64:

```
bazel run @bullseye//:lock
bazel run @shared_dependencies//:lock
bazel run @noble//:lock

bazel test //...
```

produces these changes, which seem to be, mostly,

* tabs vs 2 spaces in lock.json
* keys with '_' instead of '~'
* some tooling in MODULES.lock
@thesayyn thesayyn merged commit 8a2174a into GoogleContainerTools:main Sep 12, 2024
10 checks passed
@jjmaestro jjmaestro deleted the fix-target_compatible_with branch September 12, 2024 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants