[Fisterra-devel] problems with jhbuild-buildbot in fisterra

[Maria I. F. T. <mif...@ig...>]

Hello

I have installed jhbuild-buildbot for fisterra in my machine and I found
some problems in the process of building.

First:
In the step of build for fisterra-repair module it fails because tries
to write in a directory where it hasn't permissions (this is /etc/pam.d)
and for this reason the process isn't completed successfully. This fail
happens when command "make install" is executing. 
I don't know if I can do something to solve this.

Second:
The other modules are built successfully and I'm trying to execute unit
tests for fisterra-base module in the slave.

First time the system executed the step make-check and in this step the
command "jhbuild --moduleset=fisterra.modules pathrun fisterra-base
make-check.sh", one of the fails appeared was:

** (Libfisterra: GNOME business applications development
framework:7200): WARNING **: Error: libpq.so.2: cannot open shared
object file: No such file or directory
** ERROR **: f_da_provider_init: GDA provider does not exist
aborting...

I solve the first error adding to path the place where the library libpq.so.2 is but now the output is:

	Error: Could not find provider SQLite in the current setup
	[...]
	check_fisterra-base.c:146:F:Core:check_fisterra_base_sqlite:
	******************************************************
	The sqlite gda provider is not (properly) installed
	There are certain tests that rely on that provider; so,
	those tests will fail without actually being executed
	******************************************************

I don't write all the output because is too long. This behaviour is in the slave.

Then I execute "make -k check" in my directory, (not in the slave) where I have downloaded and
 installed fisterra-base by manual process, and all tests passed successfully. 

I think that to solve this in the slave I have to change or add a environment variable but really I don't know.

If someone has an idea, could you help me?


Third:
Executing this tests in the slave the result of one is segmentation fault but in my directory it passed successfully. This 
behaviour seems stranged and I think that it can be solved substituing this code (in fisterra-base/ut/common/check_util.c in the test 
check_util_name_month): 
  
 gchar* months[] = {"January",
                     "February",
                     "March",
                     "April",
                     "May",
                     "June",
                     "July",
                     "August",
                     "September",
                     "October",
                     "November",
                     "December"};
  int i;
  for (i=1;i<13;i++){
    fail_unless(strcmp(u_get_name_of_month(i),
                       months[i]));
    fail_unless(strcmp(u_month_number_to_month_string(i),
                       months[i]));
  }


for that one:

  int i;
  for (i=1;i<13;i++){
    fail_unless(!strcmp(u_get_name_of_month(i),
                       months[i-1]));
    fail_unless(!strcmp(u_month_number_to_month_string(i),
                       months[i-1]));
  }

Because strcmp returns 0 if the strings are equals and fail_unless(0) make the test fails. And I think that the counter of the array it was wrong.

I don't know what I can do with this because the next time the jhbuild-buildbot execute the step of update the sources will be overwritten and 
the test will fail again.