not connected to DevTools about laravel-dusk-ci HOT 6 CLOSED

Can you check this thread for the beginnng?

from laravel-dusk-ci.

@chilio
I have checked and tried every possible no luck maybe resolution resize can cause this?

from laravel-dusk-ci.

@msonowal I doubt resize could cause this (you can always verify it yourself), rather I would suspect infrastructure or too complex tests.
I have a few additional questions for your case:

1. Can you find any significant common block in your modal tests, which might break tests, cause from your log it seems to happen on modals mostly? If tests are failing randomly, please omit this question.
2. Are you sure, that all tests are passing green on your local dev environment?
3. What are the parameters of your machine on AWS (CPU, MEM, Storage definitions)?

BTW. A small note from my experiences, if memory usage goes beyond default and system needs to use swap then these nasty problems are coming into force, certain lags, timeouts, etc. This sounds strange cause you should not experience them in services like AWS, or am I misssing something.

from laravel-dusk-ci.

@msonowal Additional note I have seen same tests randomly failing while using certain jquery plugins like for example iCheck. Removing these plugins made my stressed out, concurrent gitlab-runners going green.
So please keep in mind, that your project may be responsible for any strange behavior also...

from laravel-dusk-ci.

@chilio
There is no jQuery involved only pure Vue
right now it is working green after I have removed all the resize methods and put the window size in the start. It is working

from laravel-dusk-ci.

@msonowal great to hear that. I hope Laravel Dusk becomes more robust with time...

from laravel-dusk-ci.