Bugs item #1637853, was opened at 2007-01-17 17:26 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1637853&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: PF/tests Group: Pathfinder CVS Head Status: Closed Resolution: Fixed Priority: 8 Private: No Submitted By: Stefan Manegold (stmane) Assigned to: Jan Rittinger (tsheyar) Summary: XQ: syntax/parse error go to server instead of client Initial Comment: While working fine until Tuesday Nov 7 2006, the below tests fail (at least) since Saturday Nov 11 2006(!) (there were no pathfinder testing results in between these dates), because syntax/parse error messages now go to the server console as opposed to be set to the client to be handled/displayed there. See http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/Q14.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/A3.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/A4.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/A6.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/benchmarks_XPathMark/A7.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugDay_2005-11-09_0.9.3/strange_ampersand.SF-1208620.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_BugsViaSourgeforce/ID.1208620-2.err.00.html http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d-Fedora4/tests_i18n/bad-001.err.00.html ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2007-01-19 01:13 Message: Logged In: YES user_id=572415 Originator: YES Jan, thank you very much for fixing also this one! ---------------------------------------------------------------------- Comment By: Jan Rittinger (tsheyar) Date: 2007-01-18 21:40 Message: Logged In: YES user_id=993208 Originator: NO The errors are back in the error buffer (and thus not printed to stderr anymore). The tests are adjusted and the bug thus is solved. (Thanks Stefan for hunting this one down!) ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-01-17 18:57 Message: Logged In: YES user_id=572415 Originator: YES The new behaviour was most probabaly triggered by =================================================================== 2006/11/08 - tsheyar: ./compiler/oops.c,1.22 -- Split up the handling of PFoops, PFinfo and PFlog. Before the change everything went into a fixed character array (err_buf) and was printed to stderr after the query was finished (for the call of 'pf' and was returned as error message for the server side compilation). This was not feasible anymore as the generated timing information was already to big. Now only PFoops and PFinfo print to this array. (I'm however not sure whether a call to PFinfo should trigger an error in the server side compilation.) PFlog on the other side now prints directly to stderr. (Here again I'm not sure whether this does harm server side compilation.) =================================================================== In case the new behaviour is intended, *please* approve the respective new output as well; in case the new behaviour is not intended, *please* fix the respective code. Thanks! ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2007-01-17 17:51 Message: Logged In: YES user_id=572415 Originator: YES Since these tests do work in the XQuery_0-14 release branch, i.e., they have (recently) been broken only in the development trunk, I consider this bug report high priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1637853&group_id=56967 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
