feat: match multiline error

[BugenZhao]

Support matching multiline error message under ---- for both statement error and query error.

query error
SELECT 1/0;
----
db error: ERROR: Failed to execute query

Caused by these errors:
  1: Failed to evaluate expression: 1/0
  2: Division by zero

The output error message must be the exact match of the expected one to pass the test, except for the leading and trailing whitespaces. Users may use --override to let the runner update the test files with the actual output.

Empty lines are allowed in the expected error message. As a result, the message must end with two consecutive empty lines.

Breaking changes in the parser:

• Add new variants to ParseErrorKind. Mark it as #[non_exhaustive].
• Change the type of expected_error from Regex to ExpectedError, which is either a inline Regex or multiline String.

[BugenZhao]

An example generated by sqllogictest --override in RisingWave:

https://github.com/risingwavelabs/risingwave/blob/39493a08ea84d5ea5713ed745ddcf5d17c59c526/e2e_test/error_ui/main.slt#L1-L10

[xxchan]

(Haven't reviewed yet) @wangrunji0408 requested multi line mode for query last time (To test select jsonb_pretty). Could the work for these two features be shared?

---

forget it

[xxchan]

First I'm thinking whether it's necessary to introduce the error enum. Why not put it in expected_results. But it should be problematic.

I think we've messed the Record type. 🤣 To be more correct, it should be like enum of error or results. Some fields are common, and some belong only to query.

[xxchan]

nvm. I'm happy to live with it.

[BugenZhao]

Same opinion with you. 😕 It's a sum type instead of a product type. We may refactor them in future PRs.

[xxchan]

Suggested change

	pub fn is_match(&self, err: &str) -> bool {
	pub fn matches(&self, err: &str) -> bool {

?

[BugenZhao]

This is how regex names. 😕 Just to keep interface unchanged.

[xxchan]

LGTM. Just some minor points

[xxchan]

@skyzh @wangrunji0408 can we add @BugenZhao as a colaborator.

[skyzh]

@skyzh @wangrunji0408 can we add @BugenZhao as a colaborator.

Yep let's do that!

[BugenZhao]

Wow, semver-check gets really slow (up to 30min).

[BugenZhao]

@xxchan Would you please release a new version for this? 🥰

[xxchan]

@BugenZhao Done