Naman,
Can you have a human-readable output from this test? The output is so
long, you can't spot anything there...
thanks,
-marina
Naman Mehta wrote:
> On Saturday 26 June 2010 02:11 AM, Chris Kasso wrote:
>>
>>
>> Naman Mehta wrote:
>>>
>>> hi tom,
>>>
>>> Right now, it won't fail QL otherwise hudson will remain RED and due
>>> to this RE can not promote a build and SQE can not certify a build.
>>>
>>> My plan is to monitor this and raised the bug for respective module
>>> with P2.
>>
>> A P2 seems a bit high for some of the issues this test may find. A
>> P2 suggests the fix should be in by the next milestone. For example
>> a misspelling of a log message while easy to fix is not a P2 issue.
>> I think most of the issues this test would find should be P3's some
>> maybe P4's.
>>
>> Can you also choose a consistent keyword to be put in the whiteboard
>> field to make it easy to track these logging issues in issuetracker?
>
> Make it as P2 to make sure developer can fix immediately and these are
> the issues to be fixed easily. We need to close all log message issues
> before MS3 if possible so we don't have much left after MS3. I will
> use proper keyword as subject line(starting with Log: ) to
> differentiate with other bugs.
>
> Regards,
> Naman
>
>>
>> thanks,
>> Chris
>>
>>>
>>> Regards,
>>> Naman
>>>
>>> On Friday 25 June 2010 07:33 PM, Tom Mueller wrote:
>>>> Naman,
>>>>
>>>> This sounds like a very nice tool. I would suggest that if any
>>>> problem found by this tool would be considered a P3 or higher
>>>> defect, then we should have failure of the tool cause failure of
>>>> the QL tests. Otherwise, the failure output will be ignored until
>>>> much later in the project when the fix will be more expensive to make.
>>>>
>>>> Tom
>>>>
>>>>
>>>> On 6/25/2010 12:33 AM, Naman Mehta wrote:
>>>>>
>>>>> hi all,
>>>>>
>>>>> I am planning to send same email. How to use this and How to check
>>>>> your error?
>>>>>
>>>>> Right now it's giving error for all messages(from server.log file)
>>>>> not specific to your module.
>>>>>
>>>>> Regards,
>>>>> Naman
>>>>>
>>>>> On Friday 25 June 2010 05:22 AM, Ming Zhang wrote:
>>>>>> Naman integrated the check-logged-message target to QL yesterday.
>>>>>>
>>>>>> Naman, can you add descriptions to section I of
>>>>>> quicklook/QuickLook_Test_Instructions.html for how user should
>>>>>> use/interpreate this target?
>>>>>>
>>>>>> Regards,
>>>>>> Ming
>>>>>>
>>>>>> On 6/24/2010 3:32 PM, Jane Young wrote:
>>>>>>> Okay, I see the check-logged-message target:
>>>>>>>
>>>>>>> check-logged-messages:
>>>>>>> [echo] Checking messages in:
>>>>>>> [echo]
>>>>>>> /BUILD_AREA/workspace/gf-trunk-build-continuous/gfv3-gp/glassfishv3/glassfish/domains/domain1/logs/server.log
>>>>>>>
>>>>>>> [echo] [copy] Copying 1 file to
>>>>>>> /export/home1/java_re/BUILD_AREA/workspace/gf-trunk-build-continuous/v3/tests/test-output
>>>>>>>
>>>>>>> [echo]
>>>>>>> [echo] * Message keys logged instead of message:
>>>>>>> [echo] (none)
>>>>>>> [echo]
>>>>>>>
>>>>>>> Ming, can you answer Marina's question.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Jane
>>>>>>>
>>>>>>>
>>>>>>> Marina Vatkina wrote:
>>>>>>>> I'm asking what the check-logged-messages test does and how to
>>>>>>>> decipher its output?
>>>>>>>>
>>>>>>>> thanks,
>>>>>>>> -marina
>>>>>>>>
>>>>>>>> Jane Young wrote:
>>>>>>>>> I'm not sure what you're asking. But you can check if QL
>>>>>>>>> tests are passing on Hudson:
>>>>>>>>> http://hudson.glassfish.org/job/gf-trunk-build-continuous/
>>>>>>>>> If Hudson tests are passing and your local QL tests are
>>>>>>>>> failing then it may be related to your changes.
>>>>>>>>>
>>>>>>>>> Marina Vatkina wrote:
>>>>>>>>>> What does its long output mean and how can I check if I broke
>>>>>>>>>> anything?
>>>>>>>>>>
>>>>>>>>>> thanks,
>>>>>>>>>> -marina
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>
>>>>>>> To unsubscribe, e-mail: quality-unsubscribe_at_glassfish.dev.java.net
>>>>>>> For additional commands, e-mail:
>>>>>>> quality-help_at_glassfish.dev.java.net
>>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>