Running example results in incostenties with timeouts and infinite loops

[JPtenBerge]

Running example results in incostenties with timeouts and infinite loops

[JaySunSyn]

Hmmm could you find this file in your node_modules and comment this out:

example/node_modules/@polymer/font-roboto/roboto.js

if (!window.polymerSkipLoadingFontRoboto) {
  // const link = document.createElement('link');
  // link.rel = 'stylesheet';
  // link.type = 'text/css';
  // link.crossOrigin = 'anonymous';
  // link.href =
  //     'https://fonts.googleapis.com/css?family=Roboto+Mono:400,700|Roboto:400,300,300italic,400italic,500,500italic,700,700italic';
  // document.head.appendChild(link);
}

Does it make a difference if you re-run the test?

[JaySunSyn]

I've pushed a fix to master to skip loading those fonts.

[JaySunSyn]

In your node_modules is cypress-daywalker version 0.1.1 installed, right?

[JPtenBerge]

In your node_modules is cypress-daywalker version 0.1.1 installed, right?

Yep.

"devDependencies": {
    "cypress": "^3.2.0",
    "cypress-daywalker": "^0.1.1",
    "npm-run-all": "^4.1.3"
}

I've tried commenting out those lines inside roboto.js, but that did nothing. Same inconsistencies. Buuuuut. Then I took your second suggestion:

window.polymerSkipLoadingFontRoboto = true;

And the first and second run were all green!

I wanted to rule out any luck, so I set out that it had to be all green for at least 10 runs. And sadly, on the third run things broke again.

4th run was all green, 5th run had 1 failing test, 6th and 7th run were all green, 8th run resulted in an infinite loop.

All in all, it seems that not loading fonts shaves a bit of time off, making test results more green, but timeout problems still occur. The total running time is now just under 80 seconds when they pass. When they fail, they're just under 90.

[JaySunSyn]

Please confirm if this is still the case with version 0.2.1

[JaySunSyn]

Closing this issue.

Tests are now succeeding consistently as per https://travis-ci.com/JaySunSyn/cypress-daywalker/builds/

Feel free to re-open.

[JPtenBerge]

@JaySunSyn It took me a while, but I've tested it with version 0.2.1. Sadly, exactly the same results as before: inconsistent timeouts. I'd reopen, but can't if I didn't close it myself.

[JaySunSyn]

I will now run the tests daily here https://travis-ci.com/JaySunSyn/cypress-daywalker/builds so we can check if tests fail once in a while but so far, they did not.

I've also run them around 10 times locally just now and they succeed...

I guess you did this:

git checkout master && git pull && cd example && npm install && npm run test

correct?

[JPtenBerge]

I will now run the tests daily here https://travis-ci.com/JaySunSyn/cypress-daywalker/builds so we can check if tests fail once in a while but so far, they did not.

I've also run them around 10 times locally just now and they succeed...

I'm truly curious what it could be, why it's so much slower on my machine and not on yours. Is it a software thing? A hardware thing? A Windows thing?

I guess you did this:

git checkout master && git pull && cd example && npm install && npm run test

correct?

That, and then I noticed it installed 0.2.0 of your plugin, so I explicitly installed 0.2.1 and then ran npm run test again.

[JaySunSyn]

Not sure, but here are my specs:

With now 0.2.1 installed, same issue?

[JPtenBerge]

Not sure, but here are my specs:

With now 0.2.1 installed, same issue?

Sorry for the late response, a bit busy here. But yep, I used 0.2.1 with my latest try. As for my specs:

And I have an SSD (Samsung PM981 512GB) and an NVIDIA GeForce MX130 video card as well as the Intel Integrated UHD Graphics.

[JaySunSyn]

Hmm, shouldn't matter much. You can check out here how long the tests took to run on a travis runner https://travis-ci.com/JaySunSyn/cypress-daywalker/builds/127339626#L348