I don't know what the tests are doing, but could it be connected with the fact that a leap-second was added as we changed from 2016 to 2017 and one of expected/got is taking this into account and the other isn't? Graham -------- Original message --------From: Richard Hipp <d...@sqlite.org> Date: 05/01/2017 08:12 (GMT+00:00) To: SQLite mailing list <sqlite-users@mailinglists.sqlite.org> Subject: Re: [sqlite] date-2.2c tests fail for sqlite-3.16.1 on Fedora / i686 On 1/4/17, Jakub Dorňák <jakub.dor...@misli.cz> wrote: > Example output: > > ... > ! date-2.2c-1 expected: [06:28:00.001] > ! date-2.2c-1 got: [06:28:00.000] > ! date-2.2c-4 expected: [06:28:00.004] > ! date-2.2c-4 got: [06:28:00.003] > ! date-2.2c-7 expected: [06:28:00.007] > ! date-2.2c-7 got: [06:28:00.006] > ! date-2.2c-8 expected: [06:28:00.008] > ! date-2.2c-8 got: [06:28:00.007] > ...
This is probably a function of the underlying floating-point hardware. What CPU is this running on? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
