-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
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
Add one liner documentation how to actually use CI mode #240
Comments
Hi! Thanks for opening your first issue here! 😄 |
You are right, I forgot to update the doc... |
This is how I personally use it:
|
But will it terminate like that? Seems like this is what I'm already doing locally 😁 So for CI I would need a mode that terminates after all tests ran |
Yes it terminates automatically after all tests run. |
Could not find file |
|
Thanks, got it to run. Unfortunately, it seems quite unreliable, e.g. worker disconnects, etc, at least I never got my tests to pass, which usually easily pass. Maybe it would be good to add another barebone CI mode that will just detect wether Logs:
and the runner:
|
Strongly suspect it is because: #188. See that issue for a lot of details. It is discussed in: flutter/flutter#37818 And it is fixed: flutter/engine#34496, but not landed in stable yet. |
I see, thanks 👍 I will try again with master branch and let you know. Let's hope for a either hotfix or fast next update 😅 |
If the only problem is "lost connection to device" maybe it is #188 problem; if many other problems feel free to create separate issues |
Yes personally I also suffer from this problem :( So eagerly looking forward to next stable! |
Thanks, yeah for now I can't really tell if anything else is broken 😄 will let you know if I find any other issues! |
Some features will be lost (e.g. "isolation mode", "all screenshots and videos", etc). But I guess it is implement-able. Feel free to PR! |
Sure, take your time! I personally feel it stable except for that problem; for my own case it is sometimes also not stable because I did e2e tests with a backend and docker etc which is source of unstableness - but that is surely not your case and not related to this package |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue. |
I can't figure out how to use it, because there used to be a flag for it, which is now gone, and the entire project contains no mention of the word CI anymore :D
The text was updated successfully, but these errors were encountered: