It is caused by the unittest secretly setup our module (rules_cuda, current root module as of invocation of bazel command) as an external module under testing, then the local_cuda is ignore in this case. We shall allow call to module_extenion in both root module and our module.
Superserde #239
In https://github.com/bazel-contrib/rules_cuda/pull/263#issuecomment-2273722073 a new error popup as expected.
It is caused by the unittest secretly setup our module (rules_cuda, current root module as of invocation of
bazelcommand) as an external module under testing, then thelocal_cudais ignore in this case. We shall allow call to module_extenion in both root module and our module.This in principle also fixes #238.