On Oct 27, 2006, at 10:31 AM, Josh Hursey wrote:
>> At the moment, I've been manually examining the mails every day and
>> firing off e-mails to those responsible. However, due to travel last
>> week and this week, I've gotten quite behind. :-(
> I wonder if there is a way to do something more automated. Probably
> too advanced for MTT 2.0 or 3.0, but something to think about. Maybe
> tie it in with the bug tracker, so send a "Bug Master Engineer" an
> aggregated list of failures that can be easily put into TRAC. Donno..
> just an idea to help take the burden off of you.
Ya, this is a hard one to do (Ethan suggested one method as well).
The problem is to try to figure out *who* created the problem. But
it's not always obvious, nor is it easy to figure out. Cisco nightly
regressions of internal software say, "A problem occurred -- here's
the people who committed since the test last ran successfully." So
it becomes a human problem to figure it out.
(that, and our SQA director puts a life-sized Dr. Evil cardboard
cutout in your cube if you break the build ;-) )
>> I would like to schedule some phone time with you guys and Ethan and
>> me to talk about what's working, what's not working, etc. One
>> obvious question I have is: is the INI config file format suitable?
>> Do we need to do something more complex that would allow
>> consolidation of your various configurations? ...etc.
> Tim M and I spent the better part of two days revamping our current
> setup to do some more 'advanced' things (Parallel builds, etc...). We
> are putting all of these scripts in ompi-tests/iu/mtt in case anyone
> wants to see how we are doing it and use that as an example for doing
> something similar.
Ethan -- can you coordinate with everyone to find a time that works?
I can setup a phone bridge if necessary. Monday all day and Tuesday
afternoon work for me.
Server Virtualization Business Unit