Paul Podgorsek
Paul Podgorsek
It's exactly the same problem. You need to remember what Docker has access to. In that case, `../Resources/` means `/opt/robotframework/Resources/` in the container, which does not exist.
I'm sorry to say but, with the screenshot you sent, it is simply impossible that you had access to `Resources` when mounting `Tests_Recette`, no matter how hard you try, that's...
Have you tried enabling the Chrome logs? The README has a section indicating how this can be done: https://github.com/ppodgorsek/docker-robot-framework#accessing-the-logs
Do the logs show any specific message detailing the problem? You can view the logs by following the Troubleshooting section in the README.
What is the status of this issue? Has it been resolved and can it be closed?
Do the Chrome logs show any specific message detailing the problem? Could you post them here please? You can view the logs by following the Troubleshooting section in the README.
What is the status of this issue? Has it been resolved and can it be closed?
Closing due to inactivity.
It seems the Pabot project fixed similar bugs recently. The Pabot dependency has been upgraded today, could you retry using the latest image version please?
If using CodeShip: * Install the CodeShip service by going to the project's settings in GitHub > Integration & services > Add service * The following commands should be used...