[M3devel] hudson/m3cg ir changes

Jay K jay.krell at cornell.edu
Wed Nov 10 22:04:01 CET 2010


 > What you probably see is that a set of packages is first built locally
 > and then with buildship. You cannot just use ship on a locally compiled

Oops, you are right. I misread the log.

> > You can see LINUXLIBC6 also compiling during -ship.
>
> This is strange.

I probably misread the log there too.



> If upgrade.sh already works OK, how could the last-ok installations
> on the Hudson nodes become corrupted? Ideally, the cm3-current-build
> job should fail and retry everything with upgrade.sh. Probably the
> new incompatible cm3cg has already been installed then in current, and
> we would need to restart with last-ok. Could that be the problem?
> Then it should be easy to fix (in scripts/regression/defs.sh in
> test_build_system).


Thanks, I will look further.
Basically, endeavor to use upgrade more and buildship less.


 - Jay
 		 	   		  


More information about the M3devel mailing list