Re: [Cooker] GET READY FOR A DISCUSSION: Testing on all platforms
> > > yep, we are under the process of changing the way we upload new packages: > > > we would rather upload the SRPM, and a robot shall try to recompile it on > > > the various (validated) architectures before "enabling" it. > > Perfect!!! > > (you guys are making me drool ;-) ) > Okay, actually, we had an internal discussion here. Apparently this would > cause too much problems. > Actually, what I told was a suggestion of some persons here, but it will > be too much problematic to be adopted ; also, the guys involved in the > ports know the kinds of problems that the package usually face, so the > current process seems more efficient. So... as I understand it, "problems" will be "stuck" until the maintainer of the port goes ahead and figures them out?? I personally like the idea of the buildrobot handling all the builds. If something goes "wrong" (some put a "i386" in a perl package again) then they would be notified about it. The "problem packages" are more of an exception than the rule. I myself build on alpha and i686 here, things go reasonable automatic. The packages that really won't build on alpha are mostly arched out by now > Sorry to have transmitted too quick, something which was just under > discussion. :-/ Stefan
Re: [Cooker] GET READY FOR A DISCUSSION: Testing on all platforms
Stefan van der Eijk <[EMAIL PROTECTED]> writes: > Guillaume Cottenceau wrote: > > > > Stefan van der Eijk <[EMAIL PROTECTED]> writes: > > > > > What I've seen happening a few times is that a change in > > > a package causes it to refuse to build on an other platform. > > > > > > The Mozilla team has come up with tinderbox to make sure that > > > the stuff is tested & builds on all platforms, and to show > > > what went wrong... See: > > > > > > http://www.mozilla.org/tinderbox.html > > > > > > If you get more than 10 developers together without tools, there is > > > going to be an explosion. Tinderbox keeps this potentially explosive > > > situation under control. > > > > yep, we are under the process of changing the way we upload new packages: > > we would rather upload the SRPM, and a robot shall try to recompile it on > > the various (validated) architectures before "enabling" it. > > Perfect!!! > > (you guys are making me drool ;-) ) Okay, actually, we had an internal discussion here. Apparently this would cause too much problems. Actually, what I told was a suggestion of some persons here, but it will be too much problematic to be adopted ; also, the guys involved in the ports know the kinds of problems that the package usually face, so the current process seems more efficient. Sorry to have transmitted too quick, something which was just under discussion. -- Guillaume Cottenceau
Re: [Cooker] GET READY FOR A DISCUSSION: Testing on all platforms
Guillaume Cottenceau wrote: > > Stefan van der Eijk <[EMAIL PROTECTED]> writes: > > > What I've seen happening a few times is that a change in > > a package causes it to refuse to build on an other platform. > > > > The Mozilla team has come up with tinderbox to make sure that > > the stuff is tested & builds on all platforms, and to show > > what went wrong... See: > > > > http://www.mozilla.org/tinderbox.html > > > > If you get more than 10 developers together without tools, there is > > going to be an explosion. Tinderbox keeps this potentially explosive > > situation under control. > > yep, we are under the process of changing the way we upload new packages: > we would rather upload the SRPM, and a robot shall try to recompile it on > the various (validated) architectures before "enabling" it. Perfect!!! (you guys are making me drool ;-) )
Re: [Cooker] GET READY FOR A DISCUSSION: Testing on all platforms
Stefan van der Eijk <[EMAIL PROTECTED]> writes: > What I've seen happening a few times is that a change in > a package causes it to refuse to build on an other platform. > > The Mozilla team has come up with tinderbox to make sure that > the stuff is tested & builds on all platforms, and to show > what went wrong... See: > > http://www.mozilla.org/tinderbox.html > > If you get more than 10 developers together without tools, there is > going to be an explosion. Tinderbox keeps this potentially explosive > situation under control. yep, we are under the process of changing the way we upload new packages: we would rather upload the SRPM, and a robot shall try to recompile it on the various (validated) architectures before "enabling" it. -- Guillaume Cottenceau
[Cooker] GET READY FOR A DISCUSSION: Testing on all platforms
What I've seen happening a few times is that a change in a package causes it to refuse to build on an other platform. The Mozilla team has come up with tinderbox to make sure that the stuff is tested & builds on all platforms, and to show what went wrong... See: http://www.mozilla.org/tinderbox.html If you get more than 10 developers together without tools, there is going to be an explosion. Tinderbox keeps this potentially explosive situation under control. Essentially, Tinderbox is a detective tool. It allows you to see what is happening in the source tree. It shows you who checked in what (by asking Bonsai); what platforms have built successfully; what platforms are broken and exactly how they are broken (the build logs); and the state of the files that made up the build (cvsblame) so you can figure out who broke the build, so you can do the most important thing, hold them accountable for their actions.
