pixie-io
Fix qemu test runner issues with `symbolizer_test`
We recently discovered that some tests that were skipped during CI builds because of how certain test labels conflicted with each other. Once the tags used for bazel test filtering were fixed, it was identified that the symbolizer_test.cc is flaky under the qemu test runner and so it was disabled (#1342). This is likely due to timing issues since the test relies on sleeping before certain assertions are made.
I think there might be inconsistencies with our bazelrc file used in development (meaning the fixes applied to #1342 may be relevant elsewhere). When attempting to run the symbolizer_test with qemu locally, bazel believes the test should be filtered. I had to apply the following diff to reproduce the qemu failures (P385). Without those changes, bazel is unable to find a test target as seen below:
$ bazel test -c opt --config=qemu-bpf --test_output=all --cache_test_results=no --remote_download_outputs=all //src/stirling/source_connectors/perf_profiler/symbolizers:symbolizer_test --test_output=streamed --//bazel/test_runners/qemu_with_kernel:kernel_version=latest
INFO: Invocation ID: eade06e7-b056-48ec-909d-fb419f20f8b4
INFO: Streaming build results to: https://bb.corp.pixielabs.ai/invocation/eade06e7-b056-48ec-909d-fb419f20f8b4
WARNING: Streamed test output requested. All tests will be run locally, without sharding, one at a time
WARNING: All specified test targets were excluded by filters
INFO: Analyzed target //src/stirling/source_connectors/perf_profiler/symbolizers:symbolizer_test (1 packages loaded, 13 targets configured).
INFO: Found 1 target and 0 test targets...
Target //src/stirling/source_connectors/perf_profiler/symbolizers:symbolizer_test up-to-date:
bazel-bin/src/stirling/source_connectors/perf_profiler/symbolizers/symbolizer_test
INFO: Elapsed time: 0.550s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
ERROR: No test targets were found, yet testing was requested
INFO: Streaming build results to: https://bb.corp.pixielabs.ai/invocation/eade06e7-b056-48ec-909d-fb419f20f8b4
INFO: Build completed successfully, 1 total action
I am mistaken that there are additional fixes necessary for the bazel config. #1342 will allow bazel to identify that the test target applies for the qemu-bpf config.