Skip to content
Snippets Groups Projects
  1. May 19, 2011
  2. May 18, 2011
  3. May 14, 2011
  4. May 13, 2011
  5. May 12, 2011
  6. May 11, 2011
  7. Apr 26, 2011
  8. Apr 21, 2011
  9. Apr 19, 2011
  10. Apr 03, 2011
  11. Mar 31, 2011
  12. Mar 23, 2011
  13. Mar 21, 2011
  14. Mar 18, 2011
  15. Mar 16, 2011
    • Konstantin Osipov's avatar
      Test-runner: provide a correct fix for SIGCHLD issue · e50e8fc5
      Konstantin Osipov authored
      Revert the yesterday's patch that installs SIGCHLD
      handler to early collect <defunct> server processes
      that received SIGSEGV/otherwise somehow terminated
      abnormally.
      
      The invinite loop in Tarantool_connection::recvall()
      was caused by misuse of the Python socket API,
      not by the fact that the sending side was still
      "alive".
      
      The correct fix simply checks for EOF received from
      the other end and raises an exception if
      we expected some data and got a EOF.
      e50e8fc5
  16. Mar 15, 2011
    • Konstantin Osipov's avatar
      Test-runner: update the sigchld handler (debug). · 640a81a7
      Konstantin Osipov authored
      Iron out thet sigchld handler.
      640a81a7
    • Konstantin Osipov's avatar
      Test-runner: add signal handler for SIGCHLD · 83434893
      Konstantin Osipov authored
      If Tarantool server segfaults when a test is
      running, it used to hand in <defunct> state,
      since there was no wait() call in the parent
      to collect child process state. All file descriptors,
      as well as open sockets, of a <defunct> process were
      left open. This lead to the test runner cycling
      in an infinite loop in recv() from the server,
      and the whole test suite to, ultimately, hanging
      in a busy wait.
      
      This looks more like a bug in python pexpect,
      but install a SIGCHLD handler to work it around,
      and collect child data immediately as soon as
      child terminates.
      83434893
  17. Mar 14, 2011
    • Konstantin Osipov's avatar
      A fix and a test case for Bug#730593 · ac9d9b6b
      Konstantin Osipov authored
      A fix and a test case for
      https://bugs.launchpad.net/tarantool/+bug/730593
      "Bad data if incomplete tuple"
      
      A partial tuple could get accepted by INSERT
      command, and later on show up in all search results
      on the index for which this partial tuple was missing
      keys.
      
      When inserting into a TREE index Tarantool/Box did not
      validate that the tuple which is being inserted actually
      has fields used in the index, and would insert instead
      an "ASTERISK" (wildcard) value into the index.
      
      Additionally, when such validation was added, it turned
      out that box_raise leaves a corrupt tuple in place
      since txn_abort() doesn't remove the unless it's marked
      as "GHOST", and tuples were marked as "GHOST" after
      index insert, not before.
      ac9d9b6b
Loading