un-rolled-back savepoints cause crash upon scenario exit #2712
Last updated: 2011-10-27 20:55:23 +0200
Date: 2010-11-03 11:47:39 +0100
As revealed by insert_values.SF-1578838 and savepoint-SF.1898533, the server crashes upon destroying of the sql scenario when a savepoint was used which is not rolled back to. Commenting out savepoints which are not rolled back to, resolves the crash.
Program terminated with signal 6, Aborted.
The column that is about to be destroyed is schemas.id, which probably shouldn't be freed. Probably the left-over savepoint causes this to happen.
Date: 2010-11-03 12:25:16 +0100
*** Bug #2711 has been marked as a duplicate of this bug. ***
Date: 2010-11-03 12:26:12 +0100
For convenience, here's also the original posting of bug #2711:
SQL tests sql/src/test/BugTracker/Tests/insert_values.SF-1578838.sql &
cf., Current testing (always with assertion enabled)
or Candidate testing on odd days (with assertion disabled)
With assertions disabled (e.g., Candidate testing on even days), the first test
while the second test yields a recounting error:
Date: 2010-11-11 11:25:13 +0100
Unblock this bug.
Date: 2011-03-18 10:25:10 +0100
in Mar2011, this test causes decref errors on all non-Linux platforms
Date: 2011-03-28 17:36:32 +0200
The Mar2011 version has been released.
Date: 2011-07-13 16:00:36 +0200
The two tests run fine for me, but I see that they fail on various systems (not all) during nightly testing. Can anybody explain this?
Date: 2011-07-13 22:20:06 +0200
Works for me when I run the test in isolation.
Fails when I run all tests in sql/test/BugTracker/Tests/ .
Looks like some other test earlier in that directory leaves some remains that influence this test ...
Date: 2011-07-13 22:37:37 +0200
running test authorization.SF-1430616 before test savepoint-SF.1898533 seems to trigger the failure of the latter:
.../MonetDB/sql/test/BugTracker/Tests $ Mtest.py -q . savepoint-SF.1898533
Date: 2011-07-19 19:51:02 +0200
I still have this on Apr2011-SP2_pre:
Date: 2011-07-29 11:00:05 +0200
Apr2011-SP2 has been released.
Date: 2011-09-16 15:10:38 +0200
The Aug2011 version has been released.
Date: 2011-10-17 10:33:50 +0200
This seems to be fixed by changeset a9fb3d2364d7
Date: 2011-10-27 20:55:23 +0200
*** Bug #2913 has been marked as a duplicate of this bug. ***
The text was updated successfully, but these errors were encountered: