Unable to execute the smoke test

[devdi4522]

%Error: Command Failed /usr/local/bin/verilator_bin -f lowrisc_dv_chip_verilator_sim_0.1.vc -DDISABLE_PRIM_CDC_RAND_DELAY --trace --trace-fst --trace-structs --trace-params --trace-max-array 1024 --unroll-count 512 -CFLAGS \ -std=c++11\ -Wall\ -DVM_TRACE_FMT_FST\ -DVL_USER_STOP\ -DTOPLEVEL_NAME=chip_sim_tb -LDFLAGS \ -pthread\ -lutil\ -lelf -Wall --threads 4 -Wno-fatal --threads 4
make: *** [Makefile:16: Vchip_sim_tb.mk] Error 137

ERROR: Failed to build lowrisc:dv:chip_verilator_sim:0.1 : '['make']' exited with an error:

EDIT: this happens when i run both the tests
bazel test --test_tag_filters=verilator --test_output=streamed //sw/device/tests:uart_smoketest
bazel test --test_output=streamed //sw/device/tests:uart_smoketest_sim_verilator

[rswarbrick]

Hmm, that's unfortunate! I'm pretty certain that this isn't completely broken (we actually run it in CI, I think). Some things to check:

• What version of Verilator are you using?
• Also, I think error 137 is usually "out of memory". What machine are you using for this chip-level test, and how much RAM do you have available?

[devdi4522]

Hmm, that's unfortunate! I'm pretty certain that this isn't completely broken (we actually run it in CI, I think). Some things to check:

• What version of Verilator are you using?
• Also, I think error 137 is usually "out of memory". What machine are you using for this chip-level test, and how much RAM do you have available?

I'm using verilator version Verilator 4.210
I'm using VMWare Workstation
I realised that I had allocated less RAM and now increased the amount of RAM, now the build is stuck at
//hw:verilator_real; 202s linux-sandbox

[devdi4522]

Also when I'm trying to build the software, this happens
root@Devdi:~/opentitan# bazel query 'tests(//sw/device/tests/...)'
bash: /home/dev/opentitan/opentitan/bazelisk.sh: No such file or directory

For some reason it navigates to opentitan in the opentitan directory

[rswarbrick]

About the last message, thanks for the question. I suspect that everyone locally is using the bazelisk script (which downloads Bazel and sticks it in the repository root). You might be able to get something sensible with

$ ./bazelisk.sh query 'tests(//sw/device/tests/...)'

It's a bit silly that we're searching a stupid path though. If you fancy doing some digging to figure out what's going on, that would be brilliant.

[rswarbrick]

For the previous message, can you give me the exact command you're running? (Assuming that the build didn't complete: a top-level test might take a good chunk of an hour)

[devdi4522]

About the last message, thanks for the question. I suspect that everyone locally is using the bazelisk script (which downloads Bazel and sticks it in the repository root). You might be able to get something sensible with

$ ./bazelisk.sh query 'tests(//sw/device/tests/...)'

It's a bit silly that we're searching a stupid path though. If you fancy doing some digging to figure out what's going on, that would be brilliant.

I'm not quite sure what I did but I figured out that in the manual, the steps tell you to go to $REPO_TOP before calling this query, and this query also takes you to $REPO_TOP so in one of the places I just made it so that it doesn't navigate there.

[devdi4522]

For the previous message, can you give me the exact command you're running? (Assuming that the build didn't complete: a top-level test might take a good chunk of an hour)

It's this command
bazel test --test_tag_filters=verilator --test_output=streamed //sw/device/tests:uart_smoketest

As of now the hardware part has executed and now stuck at software test for the past 4366 seconds