-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run_validate_11.sh script gets stuck on first test case #92
Comments
Same thing, but for run_validate_1N script. Any update here? |
@RomanShnurov No updates, i haven't been able to resolve or find what is the issue. |
@mlngan can you please help us out. |
Can you please try and run the provided null implementation and let us know if you encounter the same issue? |
Sounds like a genuine problem in your implementation. Check permissions of the folder. |
@xsacha, thanks for reply! |
From what I remember, the test makes the folder unreadable (permissions) and tests that you cope with this situation. The folder you use should be the one that is provided to the API. You shouldn't hardcode the name. You should also respond with an appropriate error if you cannot access it. That's what this test is. If your app crashed or otherwise failed due to not checking the folder, you might need to manually reset the permissions first. |
@xsacha thanks for responding, i don't think that the config folder is a issue since i am able to load models ( i can see it but putting print in my code). Also |
@mlngan These are the error i get when i run the |
@pawani2v It appears that you've modified the validation script/source code. It would be a good idea to run the null implementation with the original, unmodified scripts/code. The expected order of tests and output should like look the below: Running 1:1 validationChecking for hard-coded config directory [SUCCESS] |
I found the problem. I'm using ONNXInference and forgot to set IntraOpNumThreads to Ort::SessionOptions.
|
@RomanShnurov did you get it running after this change ? |
@pawani2v, yep, all tests were passed after this change. |
I am prepared my shared lib and now i am running
run_validate_11.sh
but thevalidate11
does not return even after it has run on all the images.How do i know
validate11
does not return control torun_testdriver.sh
script: I put astd::cout
invalidate11.cpp
just before return and changed theswitch
code to:I can see the
Exiting with status 0
printed but can't see the echo that i did inrun_testdriver.sh
script below theretEnroll=$?
echo i put in script:
echo "retEnroll: $retEnroll"
But if i open
htop
and kill the process i prints[SUCCESS]
and proceeds further, but the same issue occurs in next steps, what is this issue and how do i resolve it.I have run this on my development machine , and also on a virtual machine that i created using the image provided by NIST:
My Machine:
Virtual machine:
The issue occurs on both machines.
The text was updated successfully, but these errors were encountered: