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
Describe the bug
I tried to follow the steps in of the earlier reported issues in about rerunning failed tests. The rerunning is working fine, but it seems not to merge the results and produces additional logging
To Reproduce
Currently I managed to get below code running, including running failed tests. I assume the issue is somewhere in grabbing the output files from the correct path and merging them. Both the output files are created in the reports directory.
To me it seems that there are no entrypoints in this dockerfile to run the rebot command at all. So although you can give REBOT_OPTIONS, the rebot command is never actually run.
See Issue 300 if you're willing to create your own fork (there seems to be some samples).
My solution was to run the rebot outside the docker image, although it requires me to install the robot in the server where I run the docker.
Describe the bug
I tried to follow the steps in of the earlier reported issues in about rerunning failed tests. The rerunning is working fine, but it seems not to merge the results and produces additional logging
To Reproduce
Currently I managed to get below code running, including running failed tests. I assume the issue is somewhere in grabbing the output files from the correct path and merging them. Both the output files are created in the reports directory.
The part which uploads the reports to Git Hub Actions:
The text was updated successfully, but these errors were encountered: