`set -u` (does not allow unbound variables) has been removed from all scripts.
This is due to Docker on Windows treating variables in an env file,
set to an empty value (`MY_VAR=`), as unbound variables. Consequently,
these variables, even though they are "set", do not make it into the Docker
container at all, and various checks for those variables fail outright.
PiperOrigin-RevId: 713717958
Example of usage:
```
load(
"@tsl//:third_party/py/py_manylinux_compliance_test.bzl",
"verify_manylinux_compliance_test",
)
verify_manylinux_compliance_test(
name = "manylinux_compliance_test",
aarch64_compliance_tag = "manylinux_2_17_aarch64",
test_tags = [
"mac_excluded",
"windows_excluded",
],
wheel = ":wheel",
x86_64_compliance_tag = "manylinux_2_17_x86_64",
)
```
The test target is executed only when specified in Bazel command line. The test passes if `auditwheel show` results have the compliance tag value (depends on the machine type). The test fails otherwise and prints the `auditwheel show` results.
PiperOrigin-RevId: 708024471
The compliance check is disabled by default, but can be turned on by `--@local_tsl//third_party/py:wheel_compliance=true` option.
PiperOrigin-RevId: 695870736
This is an experimental job that only builds the tests and does not run them. The ML DevInfra team is using this to collect data on how these builds perform in production when compared to the regular continuous job (build + test) and to see if their runtime is fast enough to be enabled as presubmit (~20-25 mins)
"pycpp.sh" is modified such that it can be used either in build or test mode. Set `TFCI_PYCPP_SWAP_TO_BUILD_ENABLE` to 1 to enable build mode (default is test mode). Since test configs inherit from build, `linux_arm64_pycpp_test` and `linux_arm64_pycpp_test_filters` are changed to be prefixed with "build:" so that we can run both `bazel build` and `bazel test` commands with the same config.
PiperOrigin-RevId: 603543484
I forgot that Bazel does not expand shell variables inside of bazelrc files.
I also removed the extraneous printing of the index.html file into the log,
since it's not really helpful there.
PiperOrigin-RevId: 556978923
I originally used "build/" as the canonical output directory for all build
scripts, but that collided with a "BUILD" file in the TF root directory on
Windows. That was too confusing to handle, so I added a TFCI_OUTPUT_DIR
variable and set it to default to build_output instead, both of which are
additionally easier to search for. Just "build" is overloaded.
PiperOrigin-RevId: 556858432
Dmitri Latushko