drizzle-merge team mailing list archive
-
drizzle-merge team
-
Mailing list archive
-
Message #00055
Re: Merge status
Test fixes + Rollup of Monty's patches from build are in staging now. Will
move to trunk once staging is done.
On Fri, Aug 20, 2010 at 9:58 AM, Patrick Crews <gleebix@xxxxxxxxx> wrote:
> For embedded-innodb valgrind, it is because the test cases need to be
> re-recorded. Any test using SHOW CREATE TABLE has had its expected results
> change as we now include collation information in the output. Simple fix.
> I'll see about a patch
>
>
> On Fri, Aug 20, 2010 at 9:52 AM, Lee Bieber <lee.bieber@xxxxxxxxxxxxx>wrote:
>
>> Thanks Monty. What about the icc build, it seems to have gone red for
>> the past 3 builds. Also the embedded-innodb valgrind job in staging is red
>> again.
>>
>>
>> On 8/19/10 10:17 PM, Monty Taylor wrote:
>>
>>> Ok. My thing's in and it's all green. Yay!
>>>
>>> As a note, I uninstalled intltool and gettext from hades so we should be
>>> able to catch this in the future.
>>>
>>> I'm going to merge in my libdrizzle patch now - as Brian said, it should
>>> go in by itself.
>>>
>>> On 08/19/2010 07:13 PM, Patrick Crews wrote:
>>>
>>>> My apologies, man. My push of your latest didn't go through. I
>>>> rebuilt, thinking it was there.
>>>> Sorry about that and good luck getting hades green.
>>>>
>>>> On Thu, Aug 19, 2010 at 10:10 PM, Monty Taylor<mordred@xxxxxxxxxxxx
>>>> <mailto:mordred@xxxxxxxxxxxx>> wrote:
>>>>
>>>> Ass. When Patrick said "Monty's latest patch still fails" - it
>>>> build
>>>> doesn't actually have my latest - gonna try again real quick.
>>>>
>>>> On 08/19/2010 06:46 PM, Patrick Crews wrote:
>>>> > Hi. Just to send a status on the trees.
>>>> >
>>>> > Tried Monty's latest patch in build - still failing on hades
>>>> (grrr....evil)
>>>> >
>>>> > Embedded Innodb suite needs updating of .result files due to
>>>> COLLATE=
>>>> > info in SHOW CREATE TABLE. Failing in staging.
>>>> >
>>>> > Expect to push staging -> trunk after sysbench runs.
>>>> >
>>>> > Monty's latest patch in build can be backed out, but I'll leave
>>>> it
>>>> for now.
>>>> >
>>>> > Thanks,
>>>> > Patrick
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > Mailing list: https://launchpad.net/~drizzle-merge
>>>> > Post to : drizzle-merge@xxxxxxxxxxxxxxxxxxx
>>>> <mailto:drizzle-merge@xxxxxxxxxxxxxxxxxxx>
>>>> > Unsubscribe : https://launchpad.net/~drizzle-merge
>>>> > More help : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~drizzle-merge
>>> Post to : drizzle-merge@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~drizzle-merge
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> Confidentiality Notice: This e-mail message (including any attached or
>> embedded documents) is intended for the exclusive and confidential use of
>> the
>> individual or entity to which this message is addressed, and unless
>> otherwise
>> expressly indicated, is confidential and privileged information of
>> Rackspace.
>> Any dissemination, distribution or copying of the enclosed material is
>> prohibited.
>> If you receive this transmission in error, please notify us immediately by
>> e-mail
>> at abuse@xxxxxxxxxxxxx, and delete the original message.
>> Your cooperation is appreciated.
>>
>>
>
References