help with building: undefined module "cts-tradefed"

[Lanchon]

for oneplus/instantnoodlep i'm getting this error:

[100% 1/1] analyzing Android.bp files and generating ninja file at out/soong/build.ninja
FAILED: out/soong/build.ninja
cd "$(dirname "out/host/linux-x86/bin/soong_build")" && BUILDER="$PWD/$(basename "out/host/linux-x86/bin/soong_build")" && cd / && env -i  "$BUILDER"     --top "$TOP"     --soong_out "out/soong"     --out "out"     -o out/soong/build.ninja --globListDir build --globFile out/soong/globs-build.ninja -t -l out/.module_paths/Android.bp.list --available_env out/soong/soong.environment.available --used_env out/soong/soong.environment.used.build Android.bp
error: cts/hostsidetests/jvmti/attaching/Android.bp:78:1: "CtsJvmtiAttachingHostTestCases" depends on undefined module "cts-tradefed"
error: cts/hostsidetests/numberblocking/Android.bp:19:1: "CtsHostsideNumberBlockingTestCases" depends on undefined module "cts-tradefed"
error: cts/hostsidetests/graphics/gpumetrics/Android.bp:19:1: "CtsGpuMetricsHostTestCases" depends on undefined module "cts-tradefed"
error: cts/hostsidetests/jvmti/base/host/Android.bp:19:1: "CtsJvmtiHostTestBase" depends on undefined module "cts-tradefed"
error: cts/tests/tests/carrierapi/targetprep/host/Android.bp:19:1: "CtsCarrierApiTargetPrep" depends on undefined module "cts-tradefed"
ninja: build stopped: subcommand failed.
13:51:37 soong bootstrap failed with: exit status 1

i think this wasn't happening 1 or 2 days ago.

[petefoth]

@Lanchon are you still having this problem building? I was able to build for instantnoodle(not instantnoodlep) a couple of days ago with no problems.

[Lanchon]

@petefoth i have not tried anymore since i reported. i tried many times before reporting though. i spent some time contributing to the gnome project instead but i need to get back to this. what i read at the time -as weird as it sounds- was that supposedly there was a kernel regression behind this failure affecting LOS. i was using 6.x at the time and you needed to be on 5.something for it to work, but at the time i couldnt reboot for several days due to background tasks, so i didnt test this hypothesis. i can reboot now and intent to test some time in the future.

[petefoth]

OK, I'll leave this open and assigned to you. Are you building using Docker?

[Lanchon]

yes. when it tested, cloning this repo locally and then using it with no changes to build triggered this issue.

surprisingly, i think that using docker run lineageos4microg/docker-lineage-cicd did NOT display de issue; idk why.

[Lanchon]

i had built many many times then and my builds all failed. i got back to this project now, and after pulling all new changes from repos, builds succeed. this seems to have been an issue in LOS, and is now fixed.