WFTO – Weekly Falcon Test Overview 2009-01-23

WFTO – a few more bug fixes

Our MySQL/Falcon team is back from vacation and we were very productive in fixing bugs. Last week Kevin pushed his new scavenger code and after a few bug fixes in the new scavenger code long outstanding memory leak issues were fixed.

Since my last report from 2009-01-16 we fixed around 7 Falcon related bugs. Compared to our last WFTO from 2009-01-16 we have 3 new test.

The development of our failed/passed tests ratio over time looks like:

  • 1.69% – 4/236(this report)
  • 1.28% – 3/234(last report)
  • 1.29% – 3/233 (report before last one)

WFTO 2009-01-23

News for this week:

  • Christopher Powers fixed
    • Bug#39678 Assertion (bdb) fails in IndexRootPage::indexMerge during recovery
    • Bug#41663 Falcon assertion (deferredIndex->virtualOffset) failed at Index.cpp:264
    • Bug#42131 falcon_backlog test crashes in Record::getEncodedValue
    • Bug#42274 Running iuds6.tst leads to assertion in Falcon
  • Lars-Erik Bjørk fixed
    • Bug#42196 Issue with key look up for bit field in Falcon table after insert + stored func
  • Sergey Vojtovich fixed
    • Bug#42079 Falcon does not reset auto_increment on transactional truncate
  • Vladislav Vaintroub fixed
    • Bug#42136 Falcon: odd behavior for range query on index prefix when MRR is disabled

The four failing test cases are:

  • falcon_bug_30124-big
  • falcon_bug_36294-big
  • falcon_deadlock (a fix for this test failure is in review)
  • falcon_bug_22173 (a fix for this regression will be merged into our Falcon source tree soon)

What about you?

We are interested in you! Where do you use Falcon? What do you do with Falcon? Are there any features you want to see in Falcon? You can test Falcon and get famous by providing valuable bug reports or even test cases for Falcon!


This entry was posted in MySQL and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.