non-deterministic Ruby-induced failures on Travis

[stevengj]

As seen in e.g #51 and #45, we are getting frequent Travis failures due to the Ruby data-generation script producing different results on Travis than on the machines where @jiahao and I generated the data.

It's not clear what is causing this. If anyone can reproduce this failure locally, with any Ruby version, that would be helpful. Try:

rm -f data/utf8proc_data.c.new
make data/utf8proc_data.c.new
diff utf8proc_data.c data/utf8proc_data.c.new

to see if the diff output is non-empty.

cc: @StefanKarpinski

[nalimilan]

diff is non-empty here on Fedora 22. Do you want me to try something?

EDIT: but make check passes. Not sure that's useful.

[stevengj]

@nalimilan, I guess the next step would be getting a machine (or a different Ruby version on the same machine) where diff is empty, and then the tedious grind of outputting intermediate results from earlier steps in the ruby script and seeing at what point a difference is introduced...

(I don't expect make check to fail with either version of the data file. You can try make update && make check to verify this.)

[stevengj]

This seems to no longer occur.