-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Travis tests are flaky #4884
Comments
Yes I notice that since we migrate from firefox to chrome. I try to analyse the reason but it's really hard because it's totally random. So sorry @deepu105 but be sure as soon as it's possible, I ll try to reduce these random failures. |
One of the reasons I switched to Firefox last year was because I saw issues with Chrome and logging out. Sometimes it worked, sometimes it didn't. It always worked with Firefox. However, it looks like there's still issues with Protractor and the latest Firefox. angular/protractor#3750 |
Most failures I had recently were legitimate, I didn't notice that. |
@pascalgrimaud since its mostly protractor can we try to catch if there is a failure and retry once again just the protractor step? |
@deepu105 : it's sound ok for me. I will give a try |
Our travis builds are acting very flaky recently. We had to restart several jobs to get it pass.
Here is an example https://travis-ci.org/jhipster/generator-jhipster/jobs/192443191
Most of the times the failure is from Protractor and sometimes JWT or cassandra builds
Its really annoying and time wasting
cc @pascalgrimaud @jdubois
The text was updated successfully, but these errors were encountered: