Artifact b2f442a5c94f3785f1180d238b731de8b9c8ae7841674081f21d44c5348fa79f:
- File
internal/fsltype/julian_test.go
-
2026-10-19 02:58:03
— part of check-in
[387204fa55]
on branch feat/submanifest-reader
— fix(fsltype): compute text Julian days in the platform's long double
fossil's printf carries a %.17g value in C long double: a 64-bit double on macOS arm64 and Windows, 80-bit x87 on x86-64 Linux. The 16th digit, and so the event time fossil stores, differs between the two for about one time in five, which is why TestTextJulianDayMatchesFossilBinary passed on macOS and failed against CI's linux-x64 fossil. SQLite is not involved: julianday() counts integer milliseconds and 3.52.0's text-to-double conversion is integer arithmetic, neither using LONGDOUBLE_TYPE.
fossilPrintf17g now runs fossil's algorithm in a big.Float with the significand width of the platform's long double (53, 64 or 113 bits). Against all 4,007 times fossil stored in the failing CI run, 849 of them different from macOS fossil's, the 64-bit form matches every one; the 53-bit form still matches macOS fossil. The binary128 width (arm64 Linux) follows the same arithmetic but has not been compared with such a fossil. Times written on one platform and rebuilt by fossil on another may differ in the last place, as two fossils do. (user: [email protected], size: 5368) [annotate] [blame] [check-ins using]
- 2026-10-19 12:46:36 — part of check-in [e9e08cbb58] on branch feat/submanifest-reader — Merge branch 'fix/tag-events' into feat/submanifest-reader (user: [email protected], size: 5368) [annotate] [blame] [check-ins using]
-
2026-10-19 02:58:03
— part of check-in
[387204fa55]
on branch feat/submanifest-reader
— fix(fsltype): compute text Julian days in the platform's long double