Bug 204386 - run-javascriptcore-tests: Hide the output of binaries behind --verbose
Summary: run-javascriptcore-tests: Hide the output of binaries behind --verbose
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Jonathan Bedard
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-11-19 16:42 PST by Jonathan Bedard
Modified: 2019-11-22 10:27 PST (History)
4 users (show)

See Also:


Attachments
Patch (1.59 KB, patch)
2019-11-19 16:47 PST, Jonathan Bedard
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Bedard 2019-11-19 16:42:47 PST
Aakash pointed out that we might have way too many logs coming out of run-javascriptcore-tests by default. We should gate some of these logs on the --verbose flag.
Comment 1 Jonathan Bedard 2019-11-19 16:47:26 PST
Created attachment 383921 [details]
Patch
Comment 2 Aakash Jain 2019-11-21 09:22:36 PST
Comment on attachment 383921 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=383921&action=review

> Tools/Scripts/run-javascriptcore-tests:585
> +            print "$subTestName failed\n" if ($failureFlag && !$verbose);

Shouldn't we print the failures irrespective of verbose flag. Hiding failure might make it difficult to debug those failures. Especially important for EWS, where engineers can't change the flag.
Comment 3 Jonathan Bedard 2019-11-21 09:35:04 PST
(In reply to Aakash Jain from comment #2)
> Comment on attachment 383921 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=383921&action=review
> 
> > Tools/Scripts/run-javascriptcore-tests:585
> > +            print "$subTestName failed\n" if ($failureFlag && !$verbose);
> 
> Shouldn't we print the failures irrespective of verbose flag. Hiding failure
> might make it difficult to debug those failures. Especially important for
> EWS, where engineers can't change the flag.

If we're verbose, we would have printed the error line already on line 522, I was thinking that we wouldn't want to duplicate the printing.

I don't feel super strongly about it either way, though.
Comment 4 Aakash Jain 2019-11-21 09:40:58 PST
Comment on attachment 383921 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=383921&action=review

>>> Tools/Scripts/run-javascriptcore-tests:585
>>> +            print "$subTestName failed\n" if ($failureFlag && !$verbose);
>> 
>> Shouldn't we print the failures irrespective of verbose flag. Hiding failure might make it difficult to debug those failures. Especially important for EWS, where engineers can't change the flag.
> 
> If we're verbose, we would have printed the error line already on line 522, I was thinking that we wouldn't want to duplicate the printing.
> 
> I don't feel super strongly about it either way, though.

That's ok either way.

But why is this print inside if reportData?
Comment 5 Jonathan Bedard 2019-11-21 09:49:58 PST
Comment on attachment 383921 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=383921&action=review

>>>> Tools/Scripts/run-javascriptcore-tests:585
>>>> +            print "$subTestName failed\n" if ($failureFlag && !$verbose);
>>> 
>>> Shouldn't we print the failures irrespective of verbose flag. Hiding failure might make it difficult to debug those failures. Especially important for EWS, where engineers can't change the flag.
>> 
>> If we're verbose, we would have printed the error line already on line 522, I was thinking that we wouldn't want to duplicate the printing.
>> 
>> I don't feel super strongly about it either way, though.
> 
> That's ok either way.
> 
> But why is this print inside if reportData?

This is handling the case where we somehow duplicate a test name when parsing binary output. This is possible because we don't have great standards for how JSC binary tests are organized.

That line of code is basically saying 'If we don't already have a result for this test, then'
Comment 6 WebKit Commit Bot 2019-11-22 10:26:02 PST
Comment on attachment 383921 [details]
Patch

Clearing flags on attachment: 383921

Committed r252781: <https://trac.webkit.org/changeset/252781>
Comment 7 WebKit Commit Bot 2019-11-22 10:26:03 PST
All reviewed patches have been landed.  Closing bug.
Comment 8 Radar WebKit Bug Importer 2019-11-22 10:27:19 PST
<rdar://problem/57432918>