OSX master branch unit test errors

[andig]

These are as of b03ab1c, split by Chrome and FireFox. Please let me know how I can contribute.

Chrome: https://pastebin.com/eJNMZNUa
Firefox: https://pastebin.com/9CsAiWgD

[benmccann]

@andig is this one you'd be willing to send a pull request for?

also, quick note, but make sure to test against the latest commit in master. there were a few recent test fixes like c6bda02

[andig]

I have unfortunately no clue how to fix these errors. I can submit test resulta for latest master if that helps.

[benmccann]

Sure, it'd be helpful to confirm if this is still an issue after recent changes

Unfortunately I'd have a hard time fixing this one too since I develop on Linux

[andig]

I'm still seeing 40 unit test errors on ff and chrome each on my local machine. To make this a little more accessible- would you mind if I tried to beef the travis integration to automatically run the tests on OSX, too? Not sure this is entirely feasible but I could at least try?

[simonbrunel]

That would be great if only unit tests (gulp test) could be ran on each platform but I'm not sure that's possible without tricky Travis configuration. We don't want Travis to execute everything multiple time, it will take too much time but more importantly, it will break the release process since it will try to deploy multiple time to GH and npm (not good).

[etimberg]

Interesting that it's still broken on OSX. I tested the latest stuff locally and the errors I was seeing are gone.

@andig what version of OSX, Chrome, and FF do you have on your system?

[andig]

OSX: Sierra 10.12.6
Chrome: 59.0.3071.115
Firefox: 47.0.1 (rarely used, I'll check later version, too)

I'll check if I can wip up a simple, unit-test only OSX build to run by default. I have some experience with tricky travis-ci setups.

[andig]

Here is a hacked-up version of the travis build for linux plus osx: https://travis-ci.org/andig/Chart.js/builds/260713745

The osx build only runs the unit test. It is unfortunately much slower than linux as resources are scarce. It should be good enough to get a first impression though. The deployment part is currently missing but can easily be added back in.

[simonbrunel]

Though the goal is not to maintain a tricky Travis config ;) We spent lot of time to get this build/deploy/release process stable, I really don't want to deal with a broken config for future release.

[andig]

Thats up to you. Unfortunately travis has no straightforward way to configure this buidl :/ I could offer to run osx from my repo and post results from time to time but that would make catching errors harder.