Bugs item #2893875, was opened at 2009-11-07 17:19
Message generated for change (Comment added) made by boncz
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2893875&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 "stable"
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Stefan Manegold (stmane)
>Assigned to: Stefan Manegold (stmane)
Summary: PF: 82 tests fail on Auf2009_NFI/Nov2009 but work on Aug2009
Initial Comment:
The following 82 tests work(ed) fine with the Aug2009 branch,
but appear to fail with the Aug2009 branch,
and hence most probaly also with the Nov2009 branch
(which is currently even more instable wrt. testing for yet undiscovered
reasons):
benchmarks/MBench/qa05
benchmarks/MBench/
benchmarks/XBench/DC/MD/q19
benchmarks/XBench/DC/MD/
modules/pftijah/procs
modules/pftijah/colltest1
modules/pftijah/colltest2
modules/pftijah/
runtime/xrpc/admin/add_del_doc_noxrpc
runtime/xrpc/admin/backup_restore_noxrpc
runtime/xrpc/admin/
tests/BugTracker/treat_as.SF-1586454
tests/BugTracker/insert_multiple.SF-1590580
tests/BugTracker/inserting_multiple_elements.SF-1590583
tests/BugTracker/insert_into_transient.SF-1626208
tests/BugTracker/clear_attrs_on_delete.SF-1612739
tests/BugTracker/clear_attrs_on_delete.SF-1612739-b
tests/BugTracker/clear_attrs_on_delete.SF-1612739-c
tests/BugTracker/corrupt_after_update.SF-1706640
tests/BugTracker/accessing_renamed_inserted_deleted_node.SF-1718622-1718635-1718709
tests/BugTracker/insert_large_doc.SF-1726954
tests/BugTracker/replace-corrupts.SF-1758902
tests/BugTracker/swizzle-bug.SF-1760811
tests/BugTracker/swizzle-bug2.SF-1763495
tests/BugTracker/insert_attribute_gives_ERROR_in_merged_union.SF-1763575
tests/BugTracker/immune_for_updates.SF-1766259
tests/BugTracker/repeated-insert.SF-1814911
tests/BugTracker/insert-new-page.SF-1854215
tests/BugTracker/immune_for_updates.SF-1981852
tests/BugTracker/hang_non_existing_doc.SF-1911209
tests/BugTracker/function_parameter_without_type.SF-1898518
tests/BugTracker/copybug.SF-2642003
tests/BugTracker/update-with-timing.SF-2852928
tests/BugTracker/compilation_error.SF-2860574_1
tests/BugTracker/compilation_error.SF-2860574_2
tests/BugsViaSourgeforce/invisible_error_messages.SF-1409122
tests/BugsViaSourgeforce/
tests/StandOff/update/basic_insert
tests/StandOff/update/basic_test
tests/StandOff/update/
tests/Update/setattr-1
tests/Update/insert-1
tests/Update/insert-2
tests/Update/symm
tests/Update/replacevaluetest
tests/Update/replacevaluetest2
tests/Update/update
tests/Update/illegal-insert
tests/Update/illegal-delete
tests/Update/insert_test_order
tests/Update/insert_test_order_seq
tests/Update/replacenode-corruption.SF-2153245
tests/W3C_use_cases/XQUF/AddressBook/Q1x
tests/W3C_use_cases/XQUF/AddressBook/check_docs
tests/W3C_use_cases/XQUF/AddressBook/
tests/W3C_use_cases/XQUF/Parts/Q1
tests/W3C_use_cases/XQUF/Parts/Q2
tests/W3C_use_cases/XQUF/Parts/Q3a1
tests/W3C_use_cases/XQUF/Parts/Q3a2
tests/W3C_use_cases/XQUF/Parts/Q4a
tests/W3C_use_cases/XQUF/Parts/Q4ax
tests/W3C_use_cases/XQUF/Parts/Q4b
tests/W3C_use_cases/XQUF/Parts/Q4bx
tests/W3C_use_cases/XQUF/Parts/Q4c
tests/W3C_use_cases/XQUF/Parts/Q4cx
tests/W3C_use_cases/XQUF/Parts/Q6
tests/W3C_use_cases/XQUF/Parts/Q6x
tests/W3C_use_cases/XQUF/Parts/
tests/W3C_use_cases/XQUF/R/Q1
tests/W3C_use_cases/XQUF/R/Q2
tests/W3C_use_cases/XQUF/R/Q3
tests/W3C_use_cases/XQUF/R/Q4
tests/W3C_use_cases/XQUF/R/Q4x
tests/W3C_use_cases/XQUF/R/Q5b
tests/W3C_use_cases/XQUF/R/Q6a
tests/W3C_use_cases/XQUF/R/Q6b
tests/W3C_use_cases/XQUF/R/Q7
tests/W3C_use_cases/XQUF/R/Q7x
tests/W3C_use_cases/XQUF/R/Q8
tests/W3C_use_cases/XQUF/R/Q9
tests/XQuery/is-before4
tests/XQuery/union
----------------------------------------------------------------------
>Comment By: Peter Boncz (boncz)
Date: 2009-11-11 11:45
Message:
Thanks. I looked into this and fixed a problem with XQuery updates that
indeed was present. This will reduce the amount of problems, removing
(almost) all of those tests that are XQuery updates from the list.
The update bug was caused by a later modification that succeeded my own
check of the testweb that I performed before checking in the code. At that
time, already, I found it very hard to work with the test web. Note, this
is not a complaint to anyone in particular. However a matter of fact.
Simply too many tests fail, such that one is forced to spend an hour just
to compare the state of the testweb before and after a check-in, to detect
which of the tests that fail were actually already failing before the
check-in. Let alone analyze what is happening.
my suggestons are as follows:
(1) approve output:
- tests/BugTracker/empty_file.SF-2017862: SunOS specific version only!!
- tests/BugTracker/XML_document_cache_broken.SF-1414720
- tests/W3C_use_cases/XQ/NS/* (or remove tests!)
- tests/XQuery/{div.is-before4,union}
-
tests/BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516
- tests/BugDay_2005-12-19_0.9.3/shred_doc_with_space.SF-1211372: windows
only
- tests/clients/php_monetdb
- runtime/procs/approve
- modules/pftijah/{load,sigs,procs}
-
tests/BugsViaSourgeforce/{invisible_error_messages.SF-1409122,ID.1766173}
(2) remove or disable the following tests, which seem incorrect or
outdated:
- tests/BugTracker/xs_untypedAtomic.SF-1509806.mps
- tests/BugTracker/Zombie_document.SF-2009556
- tests/BugTracker/function_parameter_without_type.SF-1898518
- tests/BugTracker/fn-root_fn-id_on_attribute_nodes.SF-1
- tests/BugTracker/975028,non-existing_collection.SF-1991726
- tests/BugTracker/port_busy.SF-1809586
- tests/BugTracker/collection_management
- tests/BugDay_2005-12-19_0.9.3/multiple_servers_2.SF-1385152
- runtime/smack
- benchmarks/mbench/{qa02,qa06} are now only run for Darwin9.8.0
G.32.32.d.1 -- should also set NOT_ALGEBRA for this platform
(3) ask Jennie to look at the following tests in runtime/xrpc/admin/:
- add_del_doc_norpc: approve?
- backup_restore_xrpc: empty, check this pls??
(4) ask Jan Flokstra to look at the following tests in modules/pftijah/:
- coltest1 hang
- test_lms-or: order
- test_lms_rmoverlap, test_select_start*: empty
(5) adapt or disable these test scripts to work on windows:
- tests/BugDay_2005-12-19_0.9.3/file_locked_after_shredding.SF-1238352
(windows6 only) -
- tests/BugDay_2005-12-19_0.9.3/shredding_on_the_fly.SF-1377006: idem
- tests/BugTracker/predicate_selects_too_few_nodes.SF-1636588 - windows
fails to parse, because of Mtest substitution failure (for $v becomes for
4)
(6) ignore output of tests (possibly for certain platforms only), as these
are system limits related (too deep recursion):
- tests/BugTracker/crash_on_concatenated_query.SF-1730547 - for all
systems
- tests/BugTracker/server-side_compilation_crash.SF-1607210 - for all
systems
- tests/BugsViaSourgeforce/ID.1015172{a,b,c}: timeout on windows5
(windows6 works)
- tests/XQuery/step_attr_nametest: Darwin9.8.0 G.32.32.d too deep
recursion,
- tests/XQuery/typeswitch3 - too deep recursion on various systems..
- tests/BugDay_2005-11-09_0.9.3/xquery_crashtest.SF-1207048: pf recursion
check not triggered on Fedora10 G.32.32.d.1
what will be left, then
=======================
The only problems that will be left after following the above are in fact
problems that occur only on a single system.
Rather than indicating a platform deficiency, however, it is still very
likely that these differences indicate the
precense of a bug, that is only triggered under certain circumstances that
happen to hold on that platform.
so these are interesting to look at; all of them were already present in
the last Stable
Fedora10.G.64.64.d.0 - merge_union2: non dense head
- tests/XQuery/merge_union2
Fedora10 G.64.64.d.0 - crash
- tests/XQuery/step_attribute8,
Fedora10 I.64.64.d.1: crash
- tests/XQuery/orderby6
Fedora10 G.64.64.s.1 - crash
- tests/XQuery/step_descendant-or-self3
Fedora10.G.32.32.d.1 -- segmentation fault
- xbench/tc/md/q10
- tests/W3C_use_cases/XQ/XMP/Q07
windows - !ERROR: couldn't read name (1000000152_qn_uri) 1
- tests/BugTracker/32_docs.SF-1730617:
sunos5 g32.32.d.1 - segmentation fault
- mbench/{qs28,31}
- tests/XQuery/{step_duplicates,transient_upward_steps}
- benchmarks/XPathMark/{Q27,28}
- benchmarks/XPath/q13
- benchmarks/XMark/q04
- tests/XQuery/step_attr_nametest (also on Darwin9.8.0 G.32.32.d.1)
sunos5 g32.32.d.1 - 4 times inserted nil due to errors at tuples 0, 1, 2,
3
- tests/BugTracker/child-steps-and-replace.SF-2716723:
Debian4.0 G.32.32.d.1 - !fatal error: columns referenced in trace message
operator not found
- tests/BugTracker/fn-trace.SF-2805513 (also Gentoo2.0.1 G.64.64.d.1)
----------------------------------------------------------------------
Comment By: Stefan Manegold (stmane)
Date: 2009-11-08 18:13
Message:
The same test that fail with Aug2009_NFI, while working with Aug2009,
indeed also fail with Nov2009.
----------------------------------------------------------------------
Comment By: Stefan Manegold (stmane)
Date: 2009-11-08 16:50
Message:
For completeness:
I checked this on my 64-bit Fedora 10 Linux desktop, using a "testing"
build of MonetDB, i.e., configured with --disbale-debug --enable-optimize
--enable-assert .
I ran Mtest.py (more precisely make check, respectively RunMtest in the
build directory) seperately for the Aug2009 and the Aug2009_NFI brach
(builds) of pathfinder, collected the console output in files, and run diff
over those (as well as over the times.sql files that Mtest.py creates in
its <TSTTRGBASE> directory.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2893875&group_id=56967
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
