Closed clphuong closed 1 year ago
I'm not surprised timestamps.csv is empty.
omniperf profile --name dml_profile --path dml_profile_data echo val | sudo -S ./tools/run_models.py --timeout 0
You appear to running omniperf on the echo command before piping in your password (val) to sudo via stdin. You'll get an empty file if you run rocprof echo
too.
I think you want:
echo val | sudo -S omniperf profile --name dml_profile --path dml_profile_data -- ./tools/run_models.py --timeout 0
Although running a Python script with sudo is an absolutely horrendous idea.
I think you want:
echo val | sudo -S omniperf profile --name dml_profile --path dml_profile_data -- ./tools/run_models.py --timeout 0
I did indeed use the echo val, but it does run into some syntax error saying "command val not found" (right before sudo -S so that is absolutely my mistake).
Nonetheless, I definitely copy pasta'd the older command to get this ticket in. Note that I've tried it with miperf as well with -c "./tools/run_models.py --timeout 0" as well
Other commands I've tried are here:
omniperf profile --name dml_profile --path dml_profile_data -- ./tools/run_models.py --timeout 0
Running shibuyastream is also yields similar results so perhaps we can look into that as well.
Archiving issue. Please reopen if issue persists.
Description: Some workloads fail on timestamp generation. ShibuyaStream, DLM Accuracy tests fail
OS/distro: Ubuntu 5.15.0-52-generic #58~20.04.1-Ubuntu ROCm Version: 5.2.0 Omniperf Version: 1.0.4dev Logs of crash output:
Steps to reproduce:
}
run:
omniperf profile --name dml_profile --path dml_profile_data echo val | sudo -S ./tools/run_models.py --timeout 0