Bug #27346 autopush does not work on non-built tree
Submitted: 21 Mar 2007 17:10 Modified: 16 Mar 2009 12:25
Reporter: Ingo Strüwing Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Tests Severity:S3 (Non-critical)
Version:autopush OS:Linux (Linux)
Assigned to: Jani Tolonen CPU Architecture:Any
Triage: Triaged: D3 (Medium)

[21 Mar 2007 17:10] Ingo Strüwing
Description:
This happens if there has not been a build in the tree yet.

One of the goals of autopush was that I do not need to build and test locally but can leave this to autopush. This goal is missed if I need to build at least.

Not even --help and --version work!!!

~/internals/dev/autopush.pl --version

ERROR: Can't find my_print_defaults. Can't read my.cnf.

FIX: Please install my_print_defaults from MySQL distribution, OR
compile MySQL and autopush.pl will use extra/my_print_defaults, OR
use --force as the FIRST option to disable reading my.cnf(s)

Using --force might be a workaround for normal work, but prohibits the use of my.cnf. And requiring --force for --help and --version looks <CENSORED>.

How to repeat:
clone a tree
pull changes from another tree
~/internals/dev/autopush.pl --version

Suggested fix:
If you cannot make autopush independent of my_print_defaults, give it a --no-defaults option. In this case don't even try to run my_print_defaults. You can force --no-defaults to be the first argument like all other MySQL programs/scripts do, if it makes things easier. This is different from --force as it does not suppress non-fatal errors.

In case of --help and --version do not try to run my_print_defaults either.
[16 Mar 2009 12:25] Daniel Fischer
We don't use autopush anymore.