Bug 175589 - LayoutTests: string formatting fails
Summary: LayoutTests: string formatting fails
Status: RESOLVED DUPLICATE of bug 175590
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 175579
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-15 11:25 PDT by JF Bastien
Modified: 2017-08-15 16:08 PDT (History)
9 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JF Bastien 2017-08-15 11:25:11 PDT
In #175579 having this line hangs LayoutTests/tests/xmlhttprequest/gzip-content-type.html:
        log(`Content-Length: ${xhr.getResponseHeader('Content-Length')}`);
But having this works as expected:
        log(`Content Length: ${xhr.getResponseHeader('Content-Length')}`);

Note, the only change is dash versus space in the string.

This isn't related to string templates because this also fails:
        log('Content-Length: ' + xhr.getResponseHeader('Content-Length'));
Comment 1 Alexey Proskuryakov 2017-08-15 13:27:33 PDT
Is this the same as bug 175590?
Comment 2 JF Bastien 2017-08-15 13:31:03 PDT
(In reply to Alexey Proskuryakov from comment #1)
> Is this the same as bug 175590?

No, it's one of a few failures encountered in the wake of #175579.
Comment 3 Alexey Proskuryakov 2017-08-15 14:30:50 PDT
Bug 175590 is about run-webkit-tests failing when test output contains a line starting with "Content-Length". This bug sounds like exactly the same thing - just a slightly different symptom when the value of the fake header us different.
Comment 4 JF Bastien 2017-08-15 15:27:35 PDT
(In reply to Alexey Proskuryakov from comment #3)
> Bug 175590 is about run-webkit-tests failing when test output contains a
> line starting with "Content-Length". This bug sounds like exactly the same
> thing - just a slightly different symptom when the value of the fake header
> us different.

Ah you may be right. When Dan and I debugged it we thought they were different issues.
Comment 5 Daniel Bates 2017-08-15 16:08:02 PDT
I know that this bug was filed one bug before bug #175590. I'm going to forward dup this to bug #175590 as bug #175590 provides detailed reproduction steps and has a reduced test case.

*** This bug has been marked as a duplicate of bug 175590 ***