search

tricorder-observability / Starship

Starship: next-generation Observability platform built with eBPF+WASM
GNU Affero General Public License v3.0
162 stars 25 forks source link

Convoluted bazel test failure on github CI #221

Open nascentcore-eng opened 1 year ago

nascentcore-eng commented 1 year ago

Describe the bug //src/api-server/wasm:wasm_test fails consistently on GitHub workflow [0]. One way to fix is to update build_env to forcefully use a new cache. Since github action workflow runs bazel cache on buildbuddy, the most-likely suspect is that the cache on buildbuddy was not refreshed after adding -p to the genrule's cmd [1].

[0] https://github.com/tricorder-observability/Starship/blob/main/.github/workflows/build-and-test.yml [1] https://github.com/tricorder-observability/Starship/blob/2d2794da4eccc382eb7ed74520467ef8c309191b/src/api-server/cmd/BUILD.bazel#L45

To Reproduce Revert following entries in .bazelrc to its original state before https://github.com/tricorder-observability/Starship/pull/209

build --action_env=CACHE_VERSION=0.0.1
build --host_action_env=CACHE_VERSION=0.0.1

back to

build --action_env=CLANG_COMPILER_VERSION=14.0_0
build --host_action_env=CACHE_VERSION=0.0.1

And make sure trigger //src/api-server/wasm:wasm_test

Expected behavior The test should run OK regardless of the setup

Screenshots N/A

Additional context N/A