Re: [RFA] Add JDWP VM_INIT JVMTI callback

[Marco Trudel <mtrudel at gmx dot ch>]

Tom Tromey wrote:
> > > > > > "Marco" == Marco Trudel <mtrudel@gmx.ch> writes:
>
> Marco> I just wonder how the GCC
> Marco> staff are able to keep the quality so constant and
> Marco> gcj... well... unfortunately not that constant.
>
> You're doing probably the hardest build there is: a Canadian cross
> targeting Windows.  The core gcj developers generally are doing native
> builds, and not many gcj developers use Windows; also the ones who do
> use Windows tend to be less active.  Finally, we're in a time where
> gcj is changing rapidly, which makes the ordinary background problem
> worse.

Yes. Andrew also said it quite adequate:
	We're in "rapid development" mode at the moment.
In my opinion, progress is more worthy than stability and I'm glad GCJ 
is being worked so hard on.


> That's the explanation for how it is... but:
>
> Marco> Can we do something to change that?
>
> Yes, I think so.  One thing we could do is set up an automated tester
> on the GCC compile farm (http://gcc.gnu.org/wiki/CompileFarm) that
> does a build like yours.  That way breakage would be noticed more quickly.
>
> Would you be able to set something up?  I may be able to help a bit;
> we could take some infrastructure stuff from the Classpath builder.

Very interesting. I was thinking about something like that for a long 
time but didn't knew that there is already infrastructure around. I 
would suggest to:
- regularly try to compile a host=Linux target=mingw and host=mingw 
target=mingw compiler. Now what is regularly? What makes sense? Every 
day? Every second day? Once a week?
- If it failes: email notification. To who? Me? GCJ list?

I'd be interested in setting up a mingw-testing account and maintaining 
it. This could really help keeping things working.


Thanks for the Idea
Marco