Description:
Problem occurred in 5.0.25 builds.
Problem looks very similar to bug#18018 which is labeled "duplicate" of bug#18023 which is claimed to be fixed in 5.0.25,
so either one of these claims is wrong or it just appears to be similar ...
Might also be related to bug#21884, but for that no symptom is given.
im_life_cycle [ fail ]
Errors are (from /PATH/mysqltest-time) :
cat: /home/mysqldev/rpm/BUILD/mysql-5.0.25/mysql-test/var/run/mysqld_1.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec]
mysqltest: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/im_life_cycle.result
--- r/im_life_cycle.reject
***************
*** 40,46
--------------------------------------------------------------------
Killing the process...
Sleeping...
! Success: the process was restarted.
SHOW INSTANCES;
instance_name status
mysqld1 online
--- 40,46
--------------------------------------------------------------------
Killing the process...
Sleeping...
! Error: the process was killed.
SHOW INSTANCES;
instance_name status
mysqld1 online
-------------------------------------------------------
How to repeat:
Occurred during release build + test, but only rare.
