New issue
Advanced search Search tips

Issue 614985 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

ServiceWorkerMicrobenchmark has incorrect order of params to new Response()

Project Member Reported by falken@chromium.org, May 26 2016

Issue description

The first arg to Response ctor is the body. But our SW microbenchmark is trying to pass headers to it:

var response = new Response({
    statusCode: 200,
    statusText: 'OK',
    method: 'GET'
  });

It should really be something like:
var response = new Response('hello world');

https://github.com/horo-t/Service-Worker-Performance/blob/0cc35c2398526665399ca99fe53147ff81101408/request-latency-worker.js

Tentatively assigning to shimazu.
 
Status: Started (was: Assigned)
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 4 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/622df80e954a2ead9cdd6f242ae7bf301dd81bda

commit 622df80e954a2ead9cdd6f242ae7bf301dd81bda
Author: shimazu <shimazu@chromium.org>
Date: Sat Jun 04 02:18:18 2016

ServiceWorker: Fix the argument of ctor of Response

The first argument to Response constructor should be the body while
currently passing the header. This patch fixed it and updated the
pageset.

BUG= 614985 

Review-Url: https://codereview.chromium.org/2032893003
Cr-Commit-Position: refs/heads/master@{#397891}

[modify] https://crrev.com/622df80e954a2ead9cdd6f242ae7bf301dd81bda/tools/perf/page_sets/data/service_worker_micro_benchmark.json
[add] https://crrev.com/622df80e954a2ead9cdd6f242ae7bf301dd81bda/tools/perf/page_sets/data/service_worker_micro_benchmark_004.wpr.sha1
[modify] https://crrev.com/622df80e954a2ead9cdd6f242ae7bf301dd81bda/tools/perf/page_sets/service_worker_micro_benchmark.py

Status: Fixed (was: Started)

Sign in to add a comment