Hello, I've never run the Win32 scripts, so they may or may not work. I suspect that if you get the right environment setup they will run, but what the right environment is is the big question. See below ...
On Wednesday 29 August 2007 00:25, Michael Short wrote: > I just got around to testing out the regression scripts when I realized > that I have no idea how to use them. I set the configuration file > "prototype.conf" and ran "config prototype.conf" in the regression > directory. Everything seemed to work okay until I ran make, in which it > fails with: > The problem here is quite likely due to the fact that the Makefile must have tabs in it, so either there are a series of spaces in your prototype.conf that should be converted to a tab (unlikely IMO) or more likely the Makefile.in file somehow lost the tabs. > > > ) was unexpected at this time. > > > > When running the regression scripts, do I need to start with "make", or run > the all-tests first? > The README file gives a brief rundown on what you need to do. I think there may be more in the online Developer's guide, but those docs pertain to the Unix/Linux scripts. The person who converted the scripts to Win32, to the best of my knowledge, never bothered to document the Win32 process so I am not sure how it works there. That said, from what I see, it looks for the most part like it is a straight port of the Unix/Linux scripts, so most everything will probably work according to the README. > > > Anyways, I ran all-tests and was overwhelmed with incorrect file path > errors and "Zombie Jobs in (All Daemons)". Well, I've seen this before in the Unix/Linux scripts, and *normally* that means something really fundamental is broken. The most likely causes of something really fundamental are: 1. Bacula did not build correctly, so immediately fails -- this is unlikely to be the problem since it probably uses the Linux built binaries, but maybe it is making some assumption about the install environment. 2. The database is not correctly installed/running, so *everything* breaks. 3. Bacula is installed, but the daemons are not properly configured so that they can talk to each other (i.e. password or naming problems). This doesn't happen often on Unix/Linux because the setup takes care of it, but on Win32 it could be a big problem. > Seems there is much work to be > done here, any tips before I dive into this collection of scripts? Run one of the tests by hand, such as backup-bacula-test.cmd, and set the line: CALL scripts\functions set_debug 0 to be CALL scripts\functions set_debug 1 That should allow you to see everything. Also, I notice that sed must be on your path. There are probably some other "Unix" tools that must be installed too. > I wasn't > really sure which environment to run the scripts in either. I built a > version of Bacula from the latest SVN, r5410. Then I installed everything > with the installers (and setup sqlite along with director/storage/client) > all with their default settings. Then after everything was running, I ran > what I posted above. Yes, I am not sure what the environment was either. I would probably try running it under cygwin to avoid having to build a sed that runs on Win32. You can probably get a much better idea of what is needed by looking at the file win32\scripts\functions. That script has a lot of functions that are basic to running the scripts. Thanks for working on this. Best regards, Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
