Vladislav Vaintroub wrote:
> John, thanks for the update.
> don't you think it makes sense to finish the MWH project and remove the
> "falcon_team" tree hack from mysql-test-run.pl. The amount of red seen
> recently is the team tree is alarming (for me).
Short version: Yes, I agree.
I believe the initial idea was to run the falcon_team suite only in the
mysql-6.0-falcon-team branch (now it is also running in mysql-6.0-falcon).
Then most of us would/should practically ignore test failures in
falcon_team (but keep it running to be able monitor changes on all
Pushbuild platforms), so that we can upmerge anyway. However, I don't
think that will work very well. Red is red, and these failing tests
could be "masking" other issues.
I agree that the best solution would be to get rid of the falcon_team
suite. We are well on our way to do that, as there are only 3 tests
left, however it is still work in progress:
- Failing (lock wait timeout instead of deadlock).
- Hakan is looking into this one.
- Times out with default MTR settings.
- Not run in Pushbuild since it is --big-test.
- Failing (lock wait timeout)
- Svoj and Hakan were working in this area (e.g. Bug#34182) before the
holidays, but I'm not sure about the current status.
I will implement the following change as soon as possible unless someone
Remove falcon_team "hack" in mysql-test-run.pl, meaning that the
falcon_team suite will no longer run by default in falcon branches in
Those working on the remaining falcon_team tests may temporarily move
such a test into the falcon suite to see how it runs in Pushbuild. Then
monitor results closely and revert or fix if the test fails. This should
generally not be done right before an upmerge to main (we want to avoid
propagating unstable tests). Alternatively, use one of the "private"
Pushbuild branches for such testing.
Note that the falcon_team suite is also run as part of the Weekly Falcon
Test Overview ( http://lists.mysql.com/falcon/348 ), regardless of these