Bug #19807 linux build from source 5.0.21 tests failed; SUSE ES9
Submitted: 14 May 2006 20:47 Modified: 18 Jun 2006 21:45
Reporter: [ name withheld ] Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.21 OS:Linux (Linux Suse ES9; 2.6.5; gcc 3.3.3)
Assigned to: CPU Architecture:Any

[14 May 2006 20:47] [ name withheld ]
Description:
Building from source with: ./BUILD/compile-pentium  on system with:
- OS: Linux Suse  ES9 
- H/w: IBM; Dual Xeon 3.6
- gcc: gcc-3.3.3-43.34 
- kernel:  2.6.5-7.191-bigsmp
and running "make test-force" failes a number of the tests. The failed tests are listed below with the associated error mesage below each one:

fulltext :
mysqltest: At line 195: query 'select * from t1 where match title against ('test
' in boolean mode)' failed: 126: Incorrect key file for table './test/t1.MYI'; try to repair it

fulltext2:
mysqltest: At line 26: query 'insert t1 (a) values ('aaaxxx')' failed: 126: Incorrect key file for table './test/t1.MYI'; try to repair it

fulltext_cache:
mysqltest: Result content mismatch
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/fulltext_cache.result 2006-04-26 21:41:57.000000000 +0300
--- r/fulltext_cache.reject 2006-05-14 15:34:02.693222921 +0300
***************
*** 24,30 ****
  SELECT t1.q, t2.item, t2.id, round(MATCH t2.item AGAINST ('sushi'),6)
  as x FROM t1, t2 WHERE (t2.id2 = t1.id) ORDER BY x DESC,t2.id;
  q item    id  x
! aaaaaaaaa dsaass de   sushi   1   1.923787
  aaaaaaaaa dsaass de   Bolo de Chocolate   2   0.000000
  aaaaaaaaa dsaass de   Feijoada    3   0.000000
  aaaaaaaaa dsaass de   Mousse de Chocolate 4   0.000000
--- 24,30 ----
  SELECT t1.q, t2.item, t2.id, round(MATCH t2.item AGAINST ('sushi'),6)
  as x FROM t1, t2 WHERE (t2.id2 = t1.id) ORDER BY x DESC,t2.id;
  q item    id  x
! aaaaaaaaa dsaass de   sushi   1   0.000000
  aaaaaaaaa dsaass de   Bolo de Chocolate   2   0.000000
  aaaaaaaaa dsaass de   Feijoada    3   0.000000
  aaaaaaaaa dsaass de   Mousse de Chocolate 4   0.000000
***************
*** 46,52 ****
  SELECT t1.q, t2.item, t2.id, round(MATCH t2.item AGAINST ('sushi'),6)
  as x FROM t2, t1 WHERE (t2.id2 = t1.id) ORDER BY x DESC,t2.id;
  q item    id  x
! aaaaaaaaa dsaass de   sushi   1   1.923787
  aaaaaaaaa dsaass de   Bolo de Chocolate   2   0.000000
  aaaaaaaaa dsaass de   Feijoada    3   0.000000
  aaaaaaaaa dsaass de   Mousse de Chocolate 4   0.000000
--- 46,52 ----
  SELECT t1.q, t2.item, t2.id, round(MATCH t2.item AGAINST ('sushi'),6)
  as x FROM t2, t1 WHERE (t2.id2 = t1.id) ORDER BY x DESC,t2.id;
  q item    id  x
! aaaaaaaaa dsaass de   sushi   1   0.000000
  aaaaaaaaa dsaass de   Bolo de Chocolate   2   0.000000
  aaaaaaaaa dsaass de   Feijoada    3   0.000000
  aaaaaaaaa dsaass de   Mousse de Chocolate 4   0.000000
-------------------------------------------------------

fulltext_distinct:
mysqltest: At line 37: query 'SELECT DISTINCT t2.id_t2 FROM t2, t1
WHERE MATCH (t1.value) AGAINST ('baz333') AND t1.id = t2.id_t1' failed: 126: Incorrect key file for table './test/t1.MYI'; try to repair it

fulltext_left_join:
mysqltest: At line 43: query 'select * from t1 left join t2 on venue_id = entity_id
where match(name) against('aberdeen') and dt = '2003-05-23 19:30:00'' failed: 126: Incorrect key file for table './test/t2.MYI'; try to repair it

fulltext_multi:
mysqltest: Result content mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/fulltext_multi.result 2006-04-26 21:41:57.000000000 +0300
--- r/fulltext_multi.reject 2006-05-14 15:34:21.263333264 +0300
***************
*** 13,19 ****
  INSERT INTO t1 VALUES (3,'qpwoei','zmxnvb');
  SELECT a, round(MATCH  b  AGAINST ('lala lkjh'),5) FROM t1;
  a round(MATCH  b  AGAINST ('lala lkjh'),5)
! 1 0.67003
  2 0.00000
  3 0.00000
  SELECT a, round(MATCH  c  AGAINST ('lala lkjh'),5) FROM t1;
--- 13,19 ----
  INSERT INTO t1 VALUES (3,'qpwoei','zmxnvb');
  SELECT a, round(MATCH  b  AGAINST ('lala lkjh'),5) FROM t1;
  a round(MATCH  b  AGAINST ('lala lkjh'),5)
! 1 0.00000
  2 0.00000
  3 0.00000
  SELECT a, round(MATCH  c  AGAINST ('lala lkjh'),5) FROM t1;

fulltext_order_by:
mysqltest: At line 52: query 'INSERT INTO t1 (message) VALUES ("testbug"),("testbug foobar")' failed: 126: Incorrect key file for table './test/t1.MYI'; try to repair it

fulltext_update:
mysqltest: At line 21: query 'insert into test (url,shortdesc,longdesc,description,n
ame) VALUES ("http:/test.at", "kurz", "","desc", "name")' failed: 126: Incorrect key file for table './test/test.MYI'; try to repair it

myisam:
mysqltest: At line 329: query 'INSERT INTO t1 (post_text) VALUES ('ceci est un t
est'),('ceci est un test'),('ceci est un test'),('ceci est un test'),('ceci estun test')' failed: 126: Incorrect key file for table './test/t1.MYI'; try to repair it

Different arch flags tried  pentiumpro, pentium4, nocona; similar failures still existed in all cases.  Even no arch flags failed these tests.

How to repeat:
On a Suse ES9 system, build with: ./BUILD/compile-pentium from 5.0.21 sources.
Then run: make test-foce
[15 May 2006 19:22] Valeriy Kravchuk
Thank you for a problem report. Do you have enough free space in /tmp filesystem? Will these tests fail on your system when run one by one, not as a part of full test suite?
[16 May 2006 23:38] [ name withheld ]
Plenty of disk space exists under  /tmp. That is not a problem.
I am not sure how to run scripts independently so did not try that.
FYI, I tried -O2 as optimisation flag (instead of std -O3) with gcc and this seems to overcome the issues. However, I still want to use max optimisation build on this platform.
[18 May 2006 21:45] Valeriy Kravchuk
Please, try to upgrade gcc then and compile with -O3. There is 3.4.5 already. Inform about the results. 3.3.5 let my build pass that tests.
[18 Jun 2006 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".