rethinkdb:i386 (32-bit) on Linux 64-bit OS fails some YAML tests #6272
Description
This applies to a bug in RethinkDB 2.3.5 and 2.3.6 RC. Somewhat a low-priority issue since it's non-standard to run RethinkDB 32-bit binary on a Linux 64-bit OS.
I tested rethinkdb 32-bit binary on:
- rethinkdb:[email protected] & 2.3.6 RC on Ubuntu 14.04 64-bit OS.
- rethinkdb:[email protected] & 2.3.6 RC on Ubuntu 16.04 64-bit OS.
Note: Running RethinkDB 64-bit on a Ubuntu 64-bit OS, there are no failing tests and all YAML tests succeed.
Note: To install 32-bit RethinkDB binary on Ubuntu 64-bit OS I ran: apt-get install rethinkdb:i386.
Failing Tests
I pointed the C# driver test suite to a 32-bit rethinkdb binary running on Ubuntu 14.04-64bit and 16.04-64bit and I have the same unit tests that fail the same way on 14.04-64bit and 16.04-64bit:
Test:
geo/intersection_inclusion.yaml, LineNum: 50
Expected ReQL:
true
Expected C#/Java:
true
Run ReQL:
r.line([1,1], [2,1]).intersects(r.point(1,1))
Run C#/Java:
r.line(r.array(1L, 1L), r.array(2L, 1L)).intersects(r.point(1L, 1L))
RunOpts: []
Protocol In Context:
TRACE JSON Send: Token: 24, JSON: [1,[163,[[160,[[2,[1,1]],[2,[2,1]]]],[159,[1,1]]]],{}]
TRACE JSON Recv: Token: 24, JSON: {"t":1,"r":[false]}
PROBLEM:
Expected string to be "true" with a length of 4, but "false" has a length of 5.
Test:
geo/operations.yaml, LineNum: 5
Expected ReQL:
("89011.26253835332")
Expected C#/Java:
"89011.26253835332"
Run ReQL:
r.distance(r.point(-122, 37), r.point(-123, 37)).coerce_to('STRING')
Run C#/Java:
r.distance(r.point(-122L, 37L), r.point(-123L, 37L)).coerceTo("STRING")
RunOpts: []
Protocol In Context:
TRACE JSON Send: Token: 3, JSON: [1,[51,[[162,[[159,[-122,37]],[159,[-123,37]]]],"STRING"]],{}]
TRACE JSON Recv: Token: 3, JSON: {"t":1,"r":["89011.2625383533"]}
PROBLEM:
Expected string to be
"\"89011.26253835332\"" with a length of 19, but
"\"89011.2625383533\"" has a length of 18.
Test:
times/constructors.yaml, LineNum: 42
Expected ReQL:
"1970-01-01T00:00:01.444+00:00"
Expected C#/Java:
"1970-01-01T00:00:01.444+00:00"
Run ReQL:
r.epoch_time(1.4444445).to_iso8601()
Run C#/Java:
r.epochTime(1.4444445).toIso8601()
RunOpts: []
Protocol In Context:
TRACE JSON Send: Token: 11, JSON: [1,[100,[[101,[1.4444445]]]],{}]
TRACE JSON Recv: Token: 11, JSON: {"t":1,"r":["1970-01-01T00:00:01.443+00:00"]}
PROBLEM:
Expected date and time to be <1970-01-01 00:00:01.444>, but found <1970-01-01 00:00:01.443>.
⌚ 🌆 "I just can't wait... I just can't wait... for saturday night..."