Ignore dashboard UI tests as they crash randomly #8117
Merged
Conversation
This file contains 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
tsteur
added
not-in-changelog
|
👍 for lack of a better solution |
mnapoli
added a commit
that referenced
this pull request
Jun 18, 2015
Ignore dashboard UI tests as they crash randomly
|
Follow up issue to, at some point, re-enable them: Re-enable Dashboard UI tests #8142 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We still get PhantomJS error due to memory issues. At least I can reproduce them in my VM with only 1GB RAM and I think some travis servers have not a lot of RAM as well and then they fail. I tried to debug why they fail but couldn't figure out what is happening.
Proposal is to ignore them for now as it slows us down. We will also see if other tests are maybe causing PhantomJS to crash as well.