This week we added six new tests to the Falcon test suite. We had six tests, which where labeled as big tests. Big test means here, that the runtime or the resource requirements of that test are higher than usual. As our internal test systems are running steady integration tests on a 24/7 basis, we have to make a trade off and limit the test resource requirements to get an acceptable test throughput. However, from time to time these big tests should be run. In the Falcon team we agreed on running these tests in our Weekly Falcon Test Overview (WFTO) cycles.
We also see that there are two tests, which are not failing anymore. We disabled two tests, which will not be fixed in any near future:
- falcon_bug_22166.test Test for case-sensitive identifiers.
- falcon_bug_22187.test Test for Foreign Key. Useless as long we don’t have a general FK support from MySQL server side. Please note that Falcon does support FK. It’s just that we at MySQL are working on a general FK support for all storage engines.
News for this week:
- Jim Starkey made a change in commitNoUpdate related to Bug#34602 and Bug#36296. He worked on BLOB performance enhancement, online add column, and online native backup.
- Kevin Lewis pushed his changes for syncPrior code.
- Chris Powers worked on Bug#36269: Thread stalls during DBT2 run.
- Vladislav Vaintroub worked on fixing various Falcon and MySQL related bugs.
- Hakan Kuecuekyilmaz did test case reorganizations.
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!
- The test language we use is described here: MySQL Test Framework
- List of Falcon related bugs you will find here: http://bugs.mysql.com/saved/FalconBugs
- A preview version of Falcon you will find here: http://forge.mysql.com/wiki/Falcon_Feature_Preview
- Our MySQL Forum dedicated to Falcon related questions is here: http://forums.mysql.com/list.php?133
- To get latest Falcon source code, please see: http://dev.mysql.com/doc/refman/6.0/en/installing-source-tree.html
- Worklog entry about Foreign Key implementation: http://forge.mysql.com/worklog/task.php?id=148
By Jay Pipes 2008-04-28 - 17:19
Interesting stuff, Hakan. How do the number of Falcon tests relate to the number of, say, InnoDB tests? Also, what do you think about Stewart’s recent thread on internals@ about getting a more storage-engine-friendly test suite layout?
By admin 2008-04-29 - 09:16
you mentioned two good points. Currently we don’t compare directly to InnoDB tests. We could run all InnoDB related tests on Falcon by setting the storage engine parameter. However, Falcon’s isolation level behavior is not 100% identical to InnoDB’s.
Another way to compare InnoDB and Falcon would be the code coverage of the test runs. I am currently looking how to get the gcov test coverage numbers out of Pushbuild.
About Stewart’s recent thread on internals@; Matthias Leich and Patrick Crews are working on storage engine friendly tests: http://forge.mysql.com/worklog/task.php?id=4059
By Santo Leto 2008-04-30 - 13:42
I commented your post on my blog: http://yabomsat.honeysoftware.com/