Bug: proxy_component_test and other tests are unstable

[lurtz]

Description

The proxy_component_test fails when run concurrently with other tests:

vscode ➜ /workspaces/communication (main) $ bazel test --nocache_test_results //...
WARNING: /workspaces/communication/score/mw/com/impl/rust/BUILD:51:11: target '//score/mw/com/impl/rust:proxy_bridge_macros' is deprecated: Please change your dependency to //score/mw/com/impl/rust:bridge_macros
INFO: Analyzed 398 targets (0 packages loaded, 139 targets configured).
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.log)
INFO: Found 263 targets and 135 test targets...
INFO: Elapsed time: 14.689s, Critical Path: 12.30s
INFO: 134 processes: 151 processwrapper-sandbox.
INFO: Build completed, 1 test FAILED, 134 total actions
//score/mw/com/message_passing:resmgr_factory_test                      SKIPPED
//score/mw/com/message_passing:resmgr_traits_test                       SKIPPED
//bazel/tools:invalid_schema_and_valid_json_test                         PASSED in 0.1s
...
//score/mw/com/message_passing:unit_test                                 PASSED in 0.4s
//score/mw/com/impl/bindings/lola/test:proxy_component_test              FAILED in 2.5s
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.log

Executed 133 out of 135 tests: 132 tests pass, 1 fails locally and 2 were skipped.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.

This failure does not always happen, but often enough to be annoying.

When the test itself is run in parallel with multiple instances, each one is failing:

vscode ➜ /workspaces/communication (main) $ bazel test //score/mw/com/impl/bindings/lola/test:proxy_component_test  --runs_per_test=12
INFO: Analyzed target //score/mw/com/impl/bindings/lola/test:proxy_component_test (0 packages loaded, 5 targets configured).
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 10 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_10_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 7 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_7_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 4 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_4_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 5 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_5_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 2 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_2_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 9 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_9_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 8 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_8_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 6 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_6_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 11 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_11_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 3 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_3_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 12 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_12_of_12/test.log)
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (run 1 of 12) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_1_of_12/test.log)

FAILED: //score/mw/com/impl/bindings/lola/test:proxy_component_test (Summary)
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_10_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_7_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_4_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_5_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_2_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_9_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_8_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_6_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_11_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_3_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_12_of_12/test.log
      /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_1_of_12/test.log
INFO: Found 1 test target...
Target //score/mw/com/impl/bindings/lola/test:proxy_component_test up-to-date:
  bazel-bin/score/mw/com/impl/bindings/lola/test/proxy_component_test
INFO: Elapsed time: 1.774s, Critical Path: 1.38s
INFO: 13 processes: 24 processwrapper-sandbox.
INFO: Build completed, 1 test FAILED, 13 total actions
//score/mw/com/impl/bindings/lola/test:proxy_component_test              FAILED in 12 out of 12 in 1.3s
  Stats over 12 runs: max = 1.3s, min = 0.7s, avg = 1.1s, dev = 0.2s
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_10_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_7_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_4_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_5_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_2_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_9_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_8_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_6_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_11_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_3_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_12_of_12/test.log
  /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/run_1_of_12/test.log

Executed 1 out of 1 test: 1 fails locally.

in #39 the solution was to not run any test, which uses lola (/dev/shm, /tmp/mw_com_lola) in parallel. I did that because no other test was using the service id 52719 as used by the proxy_component_test and had no other idea how to make it reliable.

Ideally the tests are isolated from each other, but that is not the case when they do not mock lola.

Error Occurrence Rate

Highly Intermittent

How to reproduce

bazel test --nocache_test_results //...

or

bazel test //...  --runs_per_test=10

The last command shows that more tests than proxy_component_test are affected.

//score/mw/com/impl/bindings/lola/service_discovery/client:service_discovery_client_test FAILED in 9 out of 10 in 3.7s
...
//score/mw/com/impl/bindings/lola/test:proxy_component_test              FAILED in 10 out of 10 in 1.7s
...
//score/mw/com/impl/bindings/lola/test:skeleton_component_test           FAILED in 9 out of 10 in 1.0s
...
//score/mw/com/impl/bindings/lola/test:skeleton_event_component_test     FAILED in 7 out of 10 in 1.1s
...
//score/mw/com/impl/plumbing:skeleton_service_element_binding_factory_test FAILED in 9 out of 10 in 1.3s

Supporting Information

No response

Classification

minor

Affected Version

0.5

Expected Closure Version

0.5

Category

• Safety Related
• Security Related

[lurtz]

FYI @limdor

[Lakmal-Padmakumara]

We will have a look. Created a ticket internally to plan this. Will provide an update once initial analysis is done.

[crimson11]

@lurtz : I checked the issue. This is my analysis so far:

These "component tests" can only be run concurrently/parallel, if they are sandboxed. This is because the tests access/create files in filesystem. Concurrent actions obviously fail!

In our (BMW side) repository, which is configured to run with bazel 7.5.0 the tests run fine (even with N parallel instances running like in your example), because bazel (default behaviour) sandboxes every instance of the test with its own filesystem (linux-sandbox).

When I do run the same tests on my machine based on the SCORE repo, I see exactly the same errors, you reported.
The reason in my case (please check, if it is the same case for you): For some reason in the SCORE setup, which is using bazel 8.3.0, I see, that sandboxing does NOT work! And this is the reason that parallel execution of these test fails.

Where do I see, that sandboxing doesn't work correctly in the SCORE setup?
Just add -s flag to the bazel test cmd-line.
In my case it shows in the "debug output" the following:

# Execution platform: @@platforms//host:host
# Runner: sandbox-fallback

sandbox-fallback is the issue here! You can google for it! I have NO CLUE, why this fallback to local happens! I tried a myriad of arguments to avoid this fallback -> no success!

Bottomline:

1. This is not a test case problem! The tests DO interact with file-system and therefore NEED to be èxecuted sandboxed, which is the default behaviour in bazel.
2. Someone, who has more insights into bazel/SCORE bazel setup has to fix this weird fallback from sandboxed to local.
3. I will check, who can investigate this general bazel setup topic.

[lurtz]

@crimson11 I was able to reproduce that it runs without sandbox with bazel 8.3.0 and that it at least seems to run sandboxed with bazel 7.5.0. But even with bazel 7.5.0 tests are not stable and this all started with bazel 7.5.0 because 8.3.0 was added later in time.

[lurtz]

@crimson11

It still fails on my side

vscode ➜ /workspaces/communication (main) $  bazel version
Starting local Bazel server (8.3.0) and connecting to it...
Build label: 8.3.0
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Mon Jun 23 18:31:41 2025 (1750703501)
Build timestamp: 1750703501
Build timestamp as int: 1750703501

I used the following command to run the tests:

vscode ➜ /workspaces/communication (main) $ bazel test //... --build_tests_only --nocache_test_results -s

And this is the log output of the test itself:

2025/09/08 13:10:41.7041937 201048135 000 ECU1 NONE lola log fatal verbose 6 Outside tampering! Bailing! Failed to remove flag file /tmp/mw_com_lola/service_discovery/52719/16/17223_asil-qm_20104563272019 : Error  Could not remove file or directory  occurred 

This is the verbose output of bazel:

SUBCOMMAND: # //score/mw/com/impl/bindings/lola/test:proxy_component_test [action 'Testing //score/mw/com/impl/bindings/lola/test:proxy_component_test', configuration: f9d1072eba4f79b7211e6e879bc2b5949c02376a3663ff4930821f56d7b1ff46, execution platform: @@platforms//host:host, mnemonic: TestRunner]
(cd /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main && \
  exec env - \
    EXPERIMENTAL_SPLIT_XML_GENERATION=1 \
    JAVA_RUNFILES=bazel-out/k8-fastbuild/bin/score/mw/com/impl/bindings/lola/test/proxy_component_test.runfiles \
    PATH=/bin:/usr/bin:/usr/local/bin \
    PYTHON_RUNFILES=bazel-out/k8-fastbuild/bin/score/mw/com/impl/bindings/lola/test/proxy_component_test.runfiles \
    RUNFILES_DIR=bazel-out/k8-fastbuild/bin/score/mw/com/impl/bindings/lola/test/proxy_component_test.runfiles \
    RUN_UNDER_RUNFILES=1 \
    TEST_BINARY=score/mw/com/impl/bindings/lola/test/proxy_component_test \
    TEST_INFRASTRUCTURE_FAILURE_FILE=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.infrastructure_failure \
    TEST_LOGSPLITTER_OUTPUT_FILE=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.raw_splitlogs/test.splitlogs \
    TEST_NAME=//score/mw/com/impl/bindings/lola/test:proxy_component_test \
    TEST_PREMATURE_EXIT_FILE=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.exited_prematurely \
    TEST_SHARD_INDEX=0 \
    TEST_SIZE=small \
    TEST_SRCDIR=bazel-out/k8-fastbuild/bin/score/mw/com/impl/bindings/lola/test/proxy_component_test.runfiles \
    TEST_TARGET=//score/mw/com/impl/bindings/lola/test:proxy_component_test \
    TEST_TIMEOUT=300 \
    TEST_TMPDIR=_tmp/953dc09c339308529a8cd0d9a088ff0e \
    TEST_TOTAL_SHARDS=0 \
    TEST_UNDECLARED_OUTPUTS_ANNOTATIONS=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.outputs_manifest/ANNOTATIONS \
    TEST_UNDECLARED_OUTPUTS_ANNOTATIONS_DIR=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.outputs_manifest \
    TEST_UNDECLARED_OUTPUTS_DIR=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.outputs \
    TEST_UNDECLARED_OUTPUTS_MANIFEST=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.outputs_manifest/MANIFEST \
    TEST_UNUSED_RUNFILES_LOG_FILE=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.unused_runfiles_log \
    TEST_WARNINGS_OUTPUT_FILE=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.warnings \
    TEST_WORKSPACE=_main \
    TZ=UTC \
    XML_OUTPUT_FILE=bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.xml \
  external/bazel_tools/tools/test/generate-xml.sh bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.log bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.xml 1 134)
# Configuration: f9d1072eba4f79b7211e6e879bc2b5949c02376a3663ff4930821f56d7b1ff46
# Execution platform: @@platforms//host:host
# Runner: sandbox-fallback
SUBCOMMAND: # //score/mw/com/impl/bindings/lola:sample_ptr_test [action 'Linking score/mw/com/impl/bindings/lola/sample_ptr_test', configuration: f9d1072eba4f79b7211e6e879bc2b5949c02376a3663ff4930821f56d7b1ff46, execution platform: @@platforms//host:host, mnemonic: CppLink]
(cd /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main && \
  exec env - \
    PATH=/bin:/usr/bin:/usr/local/bin \
    PWD=/proc/self/cwd \
  external/score_toolchains_gcc++gcc+gcc_toolchain_gcc/bin/x86_64-unknown-linux-gnu-g++ @bazel-out/k8-fastbuild/bin/score/mw/com/impl/bindings/lola/sample_ptr_test-0.params)
# Configuration: f9d1072eba4f79b7211e6e879bc2b5949c02376a3663ff4930821f56d7b1ff46
# Execution platform: @@platforms//host:host
# Runner: sandbox-fallback
SUBCOMMAND: # //score/mw/com/impl/bindings/lola:subscription_state_machine_methods_test [action 'Linking score/mw/com/impl/bindings/lola/subscription_state_machine_methods_test', configuration: f9d1072eba4f79b7211e6e879bc2b5949c02376a3663ff4930821f56d7b1ff46, execution platform: @@platforms//host:host, mnemonic: CppLink]
(cd /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main && \
  exec env - \
    PATH=/bin:/usr/bin:/usr/local/bin \
    PWD=/proc/self/cwd \
  external/score_toolchains_gcc++gcc+gcc_toolchain_gcc/bin/x86_64-unknown-linux-gnu-g++ @bazel-out/k8-fastbuild/bin/score/mw/com/impl/bindings/lola/subscription_state_machine_methods_test-0.params)
# Configuration: f9d1072eba4f79b7211e6e879bc2b5949c02376a3663ff4930821f56d7b1ff46
# Execution platform: @@platforms//host:host
# Runner: sandbox-fallback
FAIL: //score/mw/com/impl/bindings/lola/test:proxy_component_test (Aborted) (see /var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.log)

There is still

# Execution platform: @@platforms//host:host
# Runner: sandbox-fallback

but as discussed this is misleading and should not be an issue. When I have more time, I might debug this further.

[crimson11]

@lurtz
Can you attach your test log here?

/var/cache/bazel/d130cfea8d610fd5cbbe7bb32e05decb/execroot/_main/bazel-out/k8-fastbuild/testlogs/score/mw/com/impl/bindings/lola/test/proxy_component_test/test.log

[lurtz]

@crimson11 Sorry for my slow response, I was on vacation had no access to my notebook. This is the log. I already quoted the most important message in my comment above: proxy_component_test_test.log

[crimson11]

@lurtz
Had a short look at the test-log.
There you have the following log:

score/mw/com/impl/bindings/lola/test/proxy_component_test.cpp:281: Failure
Actual function call count doesn't match EXPECT_CALL(find_service_handler_2, Call(_, _))...
Expected: to be called once
Actual: never called - unsatisfied and active

As far as I see this doesn't match with the current code-base (line 281 doesn't have this EXPECT). Can you re-run after you pulled the latest master and post your log?
Q: The error you get/saw - do you get it also with single runs or always with "parallel runs" or do you get it also with single run:
bazel test -s --nocache_test_results //score/mw/com/impl/bindings/lola/test:proxy_component_test