-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Build stuck with error uploading image #107
Comments
oh it throws the error then stuck there. |
Yes |
https://github.com/kobenguyent/codeceptjs-testrail/blob/master/lib/testrail.js#L176 not sure why, we already catch the error. |
@kobenguyent I see that build is not stuck anymore. |
My run: npx codeceptjs run-workers 3 --grep '@C' --reporter mochawesome --reporter-options reportDir='./output',overwrite=false Could it be related to run-workers 3 ? |
Well, my assumption is that the screenshot is not yet available at the time. You could try to use the current version with run command. I don't believe that's the issue due to new versions. |
run-workers? |
please try https://github.com/kobenguyent/codeceptjs-testrail/releases/tag/v1.10.9. adding the wait for file to be existed before uploading the attachment. Hope this solves the issue! |
@kobenguyent I have now different issue type: |
please try https://github.com/kobenguyent/codeceptjs-testrail/releases/tag/v1.10.10 if you have time. Many thanks! |
Checking |
@kobenguyent still not working:
|
@kobenguyent are you running with run-workers N or with run ? |
|
I guess the parentheses is from your test title? |
Yes, I added it |
hmm, I think you're using the unique screenshot name? |
@kobenguyent yes |
Then I guess that is not yet supported. |
Ok, I will remove unique screenshot names. |
perfect! Glad to hear @exotlv! |
"codeceptjs-testrail": "^1.10.5"
"codeceptjs": "^3.5.10",
When Build finished running tests - its stuck for 30min.
Stucking with such error and screenshot is not uploaded.
I tried old version 1.10.3 - works fine
The text was updated successfully, but these errors were encountered: