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

chore(IDX): don't store bazel-targets #3851

Merged
merged 4 commits into from
Feb 7, 2025
Merged

chore(IDX): don't store bazel-targets #3851

merged 4 commits into from
Feb 7, 2025

Conversation

nmattia
Copy link
Contributor

@nmattia nmattia commented Feb 7, 2025

This drops the bazel-targets which we previously used to keep a list of built targets. The list was used in build-determinism to check which targets were built by the bazel-test-all job, but since both build-ic and bazel-test-all use the same diffing logic (diff.sh) it's not necessary to pass the list around.

Also includes a necessary fix that ensure that even if there are no targets, build-ic.tar is a valid tarball.

This drops the `bazel-targets` which we previously used to keep a list
of built targets. The list was used in `build-determinism` to check
which targets were built by the `bazel-test-all` job, but since
both `build-ic` and `bazel-test-all` use the same diffing logic
(`diff.sh`) it's not necessary to pass the list around.
@github-actions github-actions bot added the chore label Feb 7, 2025
@nmattia nmattia marked this pull request as ready for review February 7, 2025 12:26
@nmattia nmattia requested a review from a team as a code owner February 7, 2025 12:26
@github-actions github-actions bot added the @idx label Feb 7, 2025
@nmattia nmattia added this pull request to the merge queue Feb 7, 2025
Merged via the queue into master with commit b886b5f Feb 7, 2025
33 checks passed
@nmattia nmattia deleted the nm-no-bazel-targets branch February 7, 2025 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants