We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We need something that will decide whether simulator is ready to work or not, rather than retry 70-80 times to get the command done
The text was updated successfully, but these errors were encountered:
This should also verify that, in case there are changes within this folder, you should add an entry to the changelog as well.
Sorry, something went wrong.
Can you explain what you expect from this? I've opened #146 adding CI, which would enable us to do this.
This is about checking if Simulator, app and web server are up and running. So the launcher will not try to work with it using hardcoded timeouts
Ah, so it's within the app; it has nothing to do with CI?
yeah
No branches or pull requests
We need something that will decide whether simulator is ready to work or not, rather than retry 70-80 times to get the command done
The text was updated successfully, but these errors were encountered: