build: reenable integration tests

[sitaktif]

The integration tests were deadlocking on trying to use the same output base as the root bazel invocation because of a value set in the home bazelrc by the Github Actions setup-bazel extension. Clearing the output base value in the integration test invocations works around the issue.

Related-to: bazel-contrib/setup-bazel#108.

[KushalP]

Looks like there build errors:

ERROR: Skipping '//...': error loading package under directory '': error loading package 'install/platforms/host': Unable to find package for @@[unknown repo 'host_platform' requested from @@]//:constraints.bzl: The repository '@@[unknown repo 'host_platform' requested from @@]' could not be resolved: No repository visible as '@host_platform' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.
ERROR: error loading package under directory '': error loading package 'install/platforms/host': Unable to find package for @@[unknown repo 'host_platform' requested from @@]//:constraints.bzl: The repository '@@[unknown repo 'host_platform' requested from @@]' could not be resolved: No repository visible as '@host_platform' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.

[sitaktif]

I must have missed something, because --output_base= definitely doesn't do what I thought: it uses the current working directory for the output base, which causes all sorts of mayhem.

[sitaktif]

No space left on device

sigh

[sitaktif]

According to https://docs.github.com/en/actions/reference/runners/github-hosted-runners#standard-github-hosted-runners-for-public-repositories, the runner should have 14GB of disk, which is probably a bit tight indeed.

I suggest we use the same output base of all the integration tests (which should be fine since they are exclusive).

[sitaktif]

The check-pkl-github-actions check is failing due to a 503 on github:

–– Pkl Error ––
Received unexpected status code `503` when making request `GET [https://github.com/apple/pkl-project-commons/releases/download/pkl.impl.ghactions@0.7.1/pkl.impl.ghactions@0.7.1`.](https://github.com/apple/pkl-project-commons/releases/download/pkl.impl.ghactions@0.7.1/pkl.impl.ghactions@0.7.1%60.)

EDIT: transient failure 👍

[KushalP]

Thank you.

Can you create issues for these hacks we've had to apply to the respective bazel-contrib/setup-bazel and rules_bazel_integration_test projects please?

[sitaktif]

Thanks @KushalP.

Regarding the issues, I created bazel-contrib/setup-bazel#108 on the setup-bazel side of things already.

I don't think rules_bazel_integration_test is doing anything wrong fundamentally; it does read the home bazelrc, but I think it's a desirable behavior to have since it allows picking up cache options of example.