[Chandler-dev] Re: Build failed on maunaloa-linux

[John Anderson]

It looks my checkin

Revision 11088

is responsible for the tinderbox failure on linux. It actually looks 
like my extra testing code might have uncovered a bug on linux. I'll 
look into it.

John


builder at osafoundation.org wrote:
> Tinderbox build has failed on maunaloa-linux.
> You are being notified because you are listed as a revision author.
>
> On Hook:      john, grant
>
> You can view the Tinderbox log here: http://builds.osafoundation.org/tinderbox/tbox/gunzip.cgi?tree=Chandler&full-log=1152204407.17464
>
> To add a Notice to the Tinderbox, visit this link: http://builds.osafoundation.org/tinderbox/tbox/addnote.cgi?tree=Chandler
>
> Revision 11088 by john. For details: http://viewcvs.osafoundation.org/chandler?view=rev&rev=11088
> Fix bug #6166 TestNewEvent throws unhandled exception in new test framework and its duplicates:
> bug #6110: functional tests (debug) crash Python on occasion and #5737: FunctionalTest crash - wxSetFocusToChild r=robin-------------------
>
> Revision 11085 by grant. For details: http://viewcvs.osafoundation.org/chandler?view=rev&rev=11085
> Fix Bug 6174 (modify occurrence to all-day causes sharing error) r=capps
>
> - Tweak some code that is trying to determine (unsuccessfully, in the
>   case of all-day events) whether or not the first occurrence in a ruleset has
>   been removed or not.
>   
> - It is somewhat unclear as to whether this is the 100% correct fix; will review
>   with jeffrey once he gets back.
> -------------------
>
> What should you do:
>
> 1. Get on IRC if you are not already and let people know you are looking
>    at the failure. Keep people up to date with your progress.
> 2. Post a note to Tinderbox (see link above). Post progress reports too.
> 3. Look at the log (see link above) to figure out what is wrong. You may
>    need to do tests locally if the log isn't helping (please file bugs
>    for any issues with the log).
> 4. If you determine that you are not the reason for the failure, let
>    people know on IRC and Tinderbox note. It would still be appreciated
>    if you could help fix the problem.
> 5. If you did cause the issue, you have to make a decision. If you think
>    you can fix the issue within an hour, do so. Otherwise, back out the
>    change so your breakage does not impact other developers.
>
> Full instructions are at http://wiki.osafoundation.org/twiki/bin/view/Projects/???
>
>