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
Tests failing -- phantomjs versionitis? #8
Comments
I'm at work at the moment. However I know these tests passed on my laptop which is using sierra. I'll check which version later when I'm at home and update this. There is also a npm task called tdd ie |
Just tried Riot 3.00 and 3.0.1 and both had same fails. Not sure what's going on... (as they've already passed on travis). |
Adding to the weirdness... In fiddling with the versions it seemed like it worked once for me, but then I couldn't repeat it. Dunno if it's that lack of sleep thing, or some randomness in the failure. Also I find that if I comment out these two passing tests, or move them to the end, then all the tests pass:
So there seems to be some sort of crosstalk between the tests. I haven't looked into what it can be. Both of those tests contain |
I'd added a setTimeout before update after the click. This was polluting the next test with an update. I've added the setTimeout to the test too, so now all seem to pass. Unfortunatly it looks like I forgot to run |
Seems to be still passing... all good. |
Hmm...
|
Further update. [...bit of fiddling...] Adding another it "should render only enough rows after scrolling", (done)->
document.querySelector('[ref=overlay]').scrollTop = 1000
setTimeout =>
expect(document.querySelectorAll('.cell').length).to.be.lt((gridheight/40)*4)
expect(document.querySelectorAll('.cell').length).to.be.gt((gridheight/40)*3)
done() |
For consistency & completeness, and to forestall future timing issues even though it currently seems OK on tested platforms. Addresses crisward#8
Hi, I wanted to submit a PR or two, and first tried to verify that the tests pass. But on my platform I'm getting some failures:
I notice that I'm using PhantomJS 2.1.1, whereas the travis build is using PhantomJS 1.9.8, so that could be the source of the problem?
Unfortunately I can't easily drop down to PhantomJS 1.9.8 as PhantomJS 1.9.x crashes on MacOS Sierra, without any workaround: "Please upgrade to PhantomJS 2. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2 version." -- response to ariya/phantomjs#14558)
Also unfortunately it seems travis-ci doesn't yet provide a clean way of using PhantomJS > 1.9.8. See this comment on travis-ci/travis-ci#3225 for links to the apparent latest way to do it. (I haven't tried it myself though)
The text was updated successfully, but these errors were encountered: