workload: check that TPCH workload returns expected results

[yuzefovich]

Now, by default, whenever TPCH workload is being run on scale factor of 1,
the returned output is checked against the expected results (which have been
roughly confirmed with PostgreSQL). This behavior can be disabled
with a flag --disable-checks=true to the workload command.

Release note: None

[cockroach-teamcity]

This change is 

[yuzefovich]

Some concerns are:

1. I modified date output from 1994-04-07 00:00:00+00:00 (returned by our cli) to 1994-04-07 00:00:00 +0000 +0000 (returned by the workload)
2. an error on query 11
3. 6202 represented by ASCII codes by the workload ([54 50 48 50])

[jordanlewis]

let's get this merged, although we won't currently pass.

Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @jordanlewis and @yuzefovich)

---

pkg/workload/tpch/tpch.go, line 56 at r1 (raw file):

}

// TODO(yuzefovich): this seems to not be used anywhere, should we delete it?

init functions get automatically run by Go.

[yuzefovich]

Query 11 has since been fixed, but it returns 1048 rows, so I added a check only for the number of rows returned for it (same as query 16).

Query 12 is still skipped (I'm not sure what the problem is, running query through cli gives the expected result, but via a workload it for some reason returns ASCII encoding of the output Error: wrong result on query 12 in row 0 in column 1: got "[54 50 48 50]", expected "6202").

Reviewable status: complete! 0 of 0 LGTMs obtained (and 1 stale) (waiting on @jordanlewis)

---

pkg/workload/tpch/tpch.go, line 56 at r1 (raw file):

Previously, jordanlewis (Jordan Lewis) wrote…

init functions get automatically run by Go.

Yeah, I didn't know about this at the time, thanks!

[yuzefovich]

TFTR!

bors r+

[craig]

Build succeeded

• GitHub CI (Cockroach)