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
It seems that doo constructs an absolute file URI for phantom to open in order to run the tests. The problem I've run into is that the following is a valid file path on linux: /home/user/code/feature%2Fbranch but when such things are passed to the browser as a file URI it interprets the encoding (presumably) as /home/user/code/feature/branch which doesn't exist.
This is common when running on jenkins which uses these kinds of paths to set up the workspace for git branches of the form feature/thing or hotfix/bug.
The text was updated successfully, but these errors were encountered:
It seems that doo constructs an absolute file URI for phantom to open in order to run the tests. The problem I've run into is that the following is a valid file path on linux:
/home/user/code/feature%2Fbranch
but when such things are passed to the browser as a file URI it interprets the encoding (presumably) as/home/user/code/feature/branch
which doesn't exist.This is common when running on jenkins which uses these kinds of paths to set up the workspace for git branches of the form
feature/thing
orhotfix/bug
.The text was updated successfully, but these errors were encountered: