test monetdb5/modules/kernel/Tests/vacuum.mal fails since changeset ada288cef37c #2994

monetdb-team · 2020-11-30T11:51:07Z

Date: 2012-02-03 11:04:22 +0100
From: @drstmane
To: MonetDB5 devs <>
Version: -- development
CC: @yzchang

Last updated: 2012-11-27 14:14:52 +0100

Comment 16857

Date: 2012-02-03 11:04:22 +0100
From: @drstmane

The following tests fail since changeset ada288cef37c
http://dev.monetdb.org/hg/MonetDB/rev/ada288cef37c

monetdb5/mal/Tests/tst654.mal
http://monetdb.cwi.nl/testweb/tests/43018:6e534d939e36/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/mal/tst654.out.diff.html

monetdb5/mal/Tests/tst655.mal
http://monetdb.cwi.nl/testweb/tests/43018:6e534d939e36/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/mal/tst655.out.diff.html

IMHO the key property must not be set in both cases, since there is a NULL value (rendered as "unknown")

monetdb5/modules/kernel/Tests/vacuum.mal
http://monetdb.cwi.nl/testweb/tests/43018:6e534d939e36/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/modules/kernel/vacuum.err.diff.html

times out after 100s

Comment 16859

Date: 2012-02-03 12:29:20 +0100
From: @drstmane

Correction for tests monetdb5/mal/Tests/tst654.mal & monetdb5/mal/Tests/tst655.mal

Since there is only one NULL values, the "key" property does hold after all (at least for the first/left of the two BATs is was already approved as correct.

Hence, I approved the new output for tests monetdb5/mal/Tests/tst654.mal & monetdb5/mal/Tests/tst655.mal and changed the subject of this bug report to refer only to test monetdb5/modules/kernel/Tests/vacuum.mal