rewrite usage setup part for escaping "Error: ENOTEMPTY: directory not empty, rmdir" and "Error: Could not find job" errors#20
Open
VitaliLebedzeu wants to merge 1 commit intoSimitTomar:masterfrom
Conversation
…t empty, rmdir" and "Error: Could not find job" errors
joweaver
reviewed
Feb 8, 2022
joweaver
left a comment
joweaver
left a comment
There was a problem hiding this comment.
This works @VitaliLebedzeu would you mind me merging?
@SimitTomar
rameshkumarj
left a comment
rameshkumarj
left a comment
There was a problem hiding this comment.
Hi .. this will not work if you run this with --suites.. with the current version, if we specify suites, then the split files will be available when the execution starts. But if we move the split function to onPrepare, then suites directory will be empty
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It should fix the Issue #17 and the "Error: Could not find a job" errors. They come across with putting the "wdioParallel.performSetup()" method as a global function into the "wdio.config.js" because this file is running with each new browser instance.
This MR suggests to use the "wdioParallel.performSetup()" method only once in the onPrepare() hook.