[BUG] Failed to execute script stmanalyze with many errors

Required Info:

  • Software Version
    DRIVE OS 6.0.8.1
  • Target OS
    Linux
  • SDK Manager Version
    1.9.2.10884
  • Host Machine Version
    native Ubuntu Linux 20.04 Host installed with DRIVE OS DOCKER Containers

Describe the bug

running stmanalysis to generate wcet report, failed with many errors.

To Reproduce

zs@in-sdk-docker:/gw_demo$ /usr/local/driveworks-5.14/tools/stmanalyze -s ./wcet/DWCGFApaNormal__standardSchedule.stm -l ./wcet/stm_20231222_155250.log -f csv -o ./wcet/report
/tmp/_MEIDfANo6/av/stm/analytics/src/parser/consolidate.py:837: UserWarning:

Error : No element present in state markers array.

/tmp/_MEIDfANo6/av/stm/analytics/src/parser/consolidate.py:1079: UserWarning:

Error : state marker array empty.

Traceback (most recent call last):
  File "stmanalyze.py", line 225, in <module>
  File "av/stm/analytics/src/parser/consolidate.py", line 872, in consolidate_schedule_with_log
  File "av/stm/analytics/src/parser/consolidate.py", line 1123, in consolidate_schedule_with_log_single
  File "av/stm/analytics/src/parser/consolidate.py", line 1600, in _populate_runnable_metrics_and_identify_missing_runnables
  File "av/stm/analytics/src/parser/consolidate.py", line 1508, in _get_start_times_with_overhead
ValueError: operands could not be broadcast together with shapes (2062,) (2040,) 
[4999] Failed to execute script stmanalyze

Expected behavior

full html/csv report generated in the report folder

Actual behavior

the command is returnning errors.

Additional context

stm_master args are

"stm_master": {
            "runOn": "machine0",
            "executable": "stm_master",
            "logSpec": "file:{{logpath}}/{{appname}}.log",
            "argv": {
                "--allow-unregistered-runnables": true,
                "--timeout-us": "60000000",
                "--soc": "TegraA",
                "--core": "0",
                "--enable-memlock": true,
                "-m": true,
                "--log": "./LogFolder/common_cgf_app/ApaNormal/stm.log",
                "--master-forked-log-path": "./LogFolder/common_cgf_app/ApaNormal"
            }
        },

Dear @lizhensheng,
Just confirming If the app run successfully?

I ran the app successfully, and use Ctrl-C to stop the runShell.sh

Is there any problem here?

Dear @lizhensheng,

Does it occur all the time? Or noticed when application does not have graceful exit as you discovered in [BUG] DO6081/CGF 5.14 app cannot exit gracefully: rerun failed, reporting internel errors and require reboot - #5 by lizhensheng?

@SivaRamaKrishnaNV Sorry for the late.

yes, it happens all the time in DO6.0.8.1. As you use Ctrl-C to stop the cgf-app program.

Any WAR to avoid this stm-log damage issue?

setting running epochs to stm_master makes the app exit gracefully, which generates a compelete stm.log

"stm_master": {
            "runOn": "machine0",
            "executable": "stm_master",
            "logSpec": "file:{{logpath}}/{{appname}}.log",
            "argv": {
                "--allow-unregistered-runnables": true,
                "--timeout-us": "60000000",
                "--soc": "TegraA",
                "--core": "0",
                "--enable-memlock": true,
                "-m": true,
                "--log": "./LogFolder/team_node/Helloworld/stm.log",
                "--master-forked-log-path": "./LogFolder/team_node/Helloworld",
                "--epochs": "10"
            }
        },