Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test monetdb5/optimizer/Tests/dataflow fails #2856

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

test monetdb5/optimizer/Tests/dataflow fails #2856

monetdb-team opened this issue Nov 30, 2020 · 0 comments

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-08-13 10:52:50 +0200
From: @drstmane
To: MonetDB5 devs <>
Version: 11.5.1 (Aug2011) [obsolete]
CC: @yzchang

Last updated: 2012-11-27 14:54:07 +0100

Comment 16097

Date: 2011-08-13 10:52:50 +0200
From: @drstmane

Test monetdb5/optimizer/Tests/dataflow fails;
the output appears to be polluted with profiling output; cf.,

http://monetdb.cwi.nl/testweb/tests/41338:3fefa57b67c0/GNU-Fedora-x86_64-propcheck-assert/monetdb5/mTests/optimizer/dataflow.out.diff.html

Please check, whether the profiling output can be avoided without compromizing the tests original intention.

Comment 16101

Date: 2011-08-13 14:08:56 +0200
From: @drstmane

Changeset 4af45f140b0f made by Stefan Manegold Stefan.Manegold@cwi.nl in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4af45f140b0f

Changeset description:

approved stable output according to changeset [e2984d191b6a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e2984d191b6a) 

this fixes bug #2856

Comment 16251

Date: 2011-09-16 15:04:39 +0200
From: @sjoerdmullender

The Aug2011 version has been released.

Comment 18098

Date: 2012-11-27 14:54:07 +0100
From: @yzchang

This is about existing tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant