You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What release version was the issue found in?
1.5.0
Hardware configuration
Any hardware platform
List Hardware components used.
Ex.
Issue found with the following:
Intel® xeon Platinum 8351N with Intel® Data Center GPU Flex 140
12th Gen Intel® Core™ i7 with Intel® Arc™ A770M Graphics
Describe the bug
if run ./docker-run.sh without providing --workload option at all, it shows message like
bash: ./docker-run.sh: No such file or directory
but instead it should shows error message like Error: please provide option --workload dlstreamer | opencv-ovms in the command line as required --OR-- workload should be default to dlstreamer if not provided in the command line option.
To Reproduce
Steps to reproduce the behavior:
Go to base root directory
Run the command ./docker-run.sh --platform core --inputsrc rstp://127.0.0.1:8554/camera_0
It will shows the error message
bash: ./docker-run.sh: No such file or directory
The text was updated successfully, but these errors were encountered:
jim-wang-intel
changed the title
Docker-run.sh with wrong message when no --workload option is provided
docker-run.sh with wrong message when no --workload option is provided
Jun 8, 2023
Version
What release version was the issue found in?
1.5.0
Hardware configuration
Any hardware platform
List Hardware components used.
Ex.
Issue found with the following:
Describe the bug
if run ./docker-run.sh without providing --workload option at all, it shows message like
but instead it should shows error message like
Error: please provide option --workload dlstreamer | opencv-ovms
in the command line as required --OR-- workload should be default to dlstreamer if not provided in the command line option.To Reproduce
Steps to reproduce the behavior:
./docker-run.sh --platform core --inputsrc rstp://127.0.0.1:8554/camera_0
The text was updated successfully, but these errors were encountered: