Public bug reported:

==============================================================================
TEST                                             RESULT
------------------------------------------------------------
box/xlog.test                                   Traceback (most recent call 
last):
  File "/data/work/tarantool/master/test/lib/test_suite.py", line 127, in run
    execfile(self.name, dict(locals(), **server.__dict__))
  File "box/xlog.test", line 122, in <module>
    exec admin "lua box.space[0]:select(0, 1)"
  File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 68, 
in execute
    self.opt_reconnect()
  File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 65, 
in opt_reconnect
    self.reconnect()
  File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 51, 
in reconnect
    self.connect()
  File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 39, 
in connect
    self.socket.connect((self.host, self.port))
  File "/usr/lib/python2.7/socket.py", line 224, in meth
    return getattr(self._sock,name)(*args)
error: [Errno 111] Connection refused
[ fail ]
Test failed! Last 10 lines of the result file:

00000000000000000006.xlog.inprogress has been successfully deleted

# Inprogress xlog with bad record must be deleted during recovery.

00000000000000000006.xlog.inprogress has been successfully deleted

A test case for https://bugs.launchpad.net/tarantool/+bug/1052018
panic_on_wal_error doens't work for duplicate key errors


Fatal error: Failed to run test box/xlog.test: test execution aborted, reason 
'[Errno 111] Connection refused'. Execution aborted.


2013-03-19 12:00:03.012 [1846] 1/sched I> recover from 
`./00000000000000000001.snap'
2013-03-19 12:00:03.012 [1846] 1/sched I> snapshot recovered, confirmed lsn: 1
2013-03-19 12:00:03.012 [1846] 1/sched I> done `./00000000000000000002.xlog' 
confirmed_lsn: 3
2013-03-19 12:00:03.012 [1846] 1/sched I> recover from 
`./00000000000000000004.xlog'
2013-03-19 12:00:03.012 [1846] 1/sched exception.m:127 E> ClientError at 
/data/work/tarantool/master/src/box/hash_index.m:374, Duplicate key exists in 
unique index 0
2013-03-19 12:00:03.012 [1846] 1/sched F> Fatal error, exiting loop

** Affects: tarantool
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Tarantool
Development Team, which is subscribed to tarantool.
https://bugs.launchpad.net/bugs/1157040

Title:
  xlog.test fails on 57bbb82ba205327706b7c88542dee40e3b8a4709

Status in Tarantool - an efficient in-memory data store:
  New

Bug description:
  ==============================================================================
  TEST                                             RESULT
  ------------------------------------------------------------
  box/xlog.test                                   Traceback (most recent call 
last):
    File "/data/work/tarantool/master/test/lib/test_suite.py", line 127, in run
      execfile(self.name, dict(locals(), **server.__dict__))
    File "box/xlog.test", line 122, in <module>
      exec admin "lua box.space[0]:select(0, 1)"
    File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 
68, in execute
      self.opt_reconnect()
    File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 
65, in opt_reconnect
      self.reconnect()
    File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 
51, in reconnect
      self.connect()
    File "/data/work/tarantool/master/test/lib/tarantool_connection.py", line 
39, in connect
      self.socket.connect((self.host, self.port))
    File "/usr/lib/python2.7/socket.py", line 224, in meth
      return getattr(self._sock,name)(*args)
  error: [Errno 111] Connection refused
  [ fail ]
  Test failed! Last 10 lines of the result file:

  00000000000000000006.xlog.inprogress has been successfully deleted

  # Inprogress xlog with bad record must be deleted during recovery.

  00000000000000000006.xlog.inprogress has been successfully deleted

  A test case for https://bugs.launchpad.net/tarantool/+bug/1052018
  panic_on_wal_error doens't work for duplicate key errors

  
  Fatal error: Failed to run test box/xlog.test: test execution aborted, reason 
'[Errno 111] Connection refused'. Execution aborted.

  
  2013-03-19 12:00:03.012 [1846] 1/sched I> recover from 
`./00000000000000000001.snap'
  2013-03-19 12:00:03.012 [1846] 1/sched I> snapshot recovered, confirmed lsn: 1
  2013-03-19 12:00:03.012 [1846] 1/sched I> done `./00000000000000000002.xlog' 
confirmed_lsn: 3
  2013-03-19 12:00:03.012 [1846] 1/sched I> recover from 
`./00000000000000000004.xlog'
  2013-03-19 12:00:03.012 [1846] 1/sched exception.m:127 E> ClientError at 
/data/work/tarantool/master/src/box/hash_index.m:374, Duplicate key exists in 
unique index 0
  2013-03-19 12:00:03.012 [1846] 1/sched F> Fatal error, exiting loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/tarantool/+bug/1157040/+subscriptions

_______________________________________________
Mailing list: https://launchpad.net/~tarantool-developers
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~tarantool-developers
More help   : https://help.launchpad.net/ListHelp

Reply via email to