Bug 173588 - test262: test262/test/built-ins/ArrayBuffer/prototype/slice/start-default-if-absent.js
Summary: test262: test262/test/built-ins/ArrayBuffer/prototype/slice/start-default-if-...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Joseph Pecoraro
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-20 00:44 PDT by Joseph Pecoraro
Modified: 2017-11-02 21:49 PDT (History)
7 users (show)

See Also:


Attachments
[PATCH] Proposed Fix (21.38 KB, patch)
2017-06-20 00:50 PDT, Joseph Pecoraro
buildbot: commit-queue-
Details | Formatted Diff | Diff
Archive of layout-test-results from ews104 for mac-elcapitan-wk2 (1.21 MB, application/zip)
2017-06-20 02:05 PDT, Build Bot
no flags Details
Archive of layout-test-results from ews116 for mac-elcapitan (1.88 MB, application/zip)
2017-06-20 02:21 PDT, Build Bot
no flags Details
Archive of layout-test-results from ews124 for ios-simulator-wk2 (20.88 MB, application/zip)
2017-06-20 02:30 PDT, Build Bot
no flags Details
Archive of layout-test-results from ews100 for mac-elcapitan (1.00 MB, application/zip)
2017-06-20 04:21 PDT, Build Bot
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Pecoraro 2017-06-20 00:44:10 PDT
test262/test/built-ins/ArrayBuffer/prototype/slice/start-default-if-absent.js

Test:

    let arrayBuffer = new ArrayBuffer(8);
    let result = arrayBuffer.slice();
    assert(result.byteLength === 8);

Actual:
Exception: TypeError: Slice requires at least one argument.

Notes:
- We shouldn't be throwing an exception about argument count here
- Same rules applies to SharedArrayBuffer

Spec:
https://tc39.github.io/ecma262/#sec-arraybuffer.prototype.slice
https://tc39.github.io/ecma262/#sec-sharedarraybuffer.prototype.slice
Comment 1 Joseph Pecoraro 2017-06-20 00:50:10 PDT
Created attachment 313379 [details]
[PATCH] Proposed Fix
Comment 2 Build Bot 2017-06-20 01:31:24 PDT
Comment on attachment 313379 [details]
[PATCH] Proposed Fix

Attachment 313379 [details] did not pass jsc-ews (mac):
Output: http://webkit-queues.webkit.org/results/3964892

New failing tests:
wasm.yaml/wasm/js-api/dont-mmap-zero-byte-memory.js.default-wasm
wasm.yaml/wasm/js-api/memory-grow.js.wasm-no-call-ic
wasm.yaml/wasm/spec-tests/jsapi.js.wasm-eager-jettison
wasm.yaml/wasm/spec-tests/jsapi.js.default-wasm
wasm.yaml/wasm/js-api/dont-mmap-zero-byte-memory.js.wasm-no-call-ic
wasm.yaml/wasm/js-api/memory-grow.js.wasm-no-cjit-yes-tls-context
wasm.yaml/wasm/js-api/dont-mmap-zero-byte-memory.js.wasm-no-tls-context
wasm.yaml/wasm/js-api/dont-mmap-zero-byte-memory.js.wasm-eager-jettison
wasm.yaml/wasm/js-api/memory-grow.js.wasm-eager-jettison
wasm.yaml/wasm/js-api/memory-grow.js.default-wasm
wasm.yaml/wasm/js-api/memory-grow.js.wasm-no-tls-context
wasm.yaml/wasm/spec-tests/jsapi.js.wasm-no-cjit-yes-tls-context
wasm.yaml/wasm/js-api/dont-mmap-zero-byte-memory.js.wasm-no-cjit-yes-tls-context
wasm.yaml/wasm/spec-tests/jsapi.js.wasm-no-tls-context
wasm.yaml/wasm/spec-tests/jsapi.js.wasm-no-call-ic
Comment 3 Build Bot 2017-06-20 02:05:28 PDT
Comment on attachment 313379 [details]
[PATCH] Proposed Fix

Attachment 313379 [details] did not pass mac-wk2-ews (mac-wk2):
Output: http://webkit-queues.webkit.org/results/3964956

New failing tests:
imported/w3c/web-platform-tests/IndexedDB/idb-binary-key-detached.htm
fast/canvas/webgl/arraybuffer-transfer-of-control.html
fast/dom/Window/window-postmessage-args.html
js/typed-array-mutated-during-set.html
Comment 4 Build Bot 2017-06-20 02:05:29 PDT
Created attachment 313383 [details]
Archive of layout-test-results from ews104 for mac-elcapitan-wk2

The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews.
Bot: ews104  Port: mac-elcapitan-wk2  Platform: Mac OS X 10.11.6
Comment 5 Build Bot 2017-06-20 02:21:39 PDT
Comment on attachment 313379 [details]
[PATCH] Proposed Fix

Attachment 313379 [details] did not pass mac-debug-ews (mac):
Output: http://webkit-queues.webkit.org/results/3964953

New failing tests:
imported/w3c/web-platform-tests/IndexedDB/idb-binary-key-detached.htm
fast/canvas/webgl/arraybuffer-transfer-of-control.html
fast/dom/Window/window-postmessage-args.html
js/typed-array-mutated-during-set.html
Comment 6 Build Bot 2017-06-20 02:21:40 PDT
Created attachment 313384 [details]
Archive of layout-test-results from ews116 for mac-elcapitan

The attached test failures were seen while running run-webkit-tests on the mac-debug-ews.
Bot: ews116  Port: mac-elcapitan  Platform: Mac OS X 10.11.6
Comment 7 Build Bot 2017-06-20 02:30:05 PDT
Comment on attachment 313379 [details]
[PATCH] Proposed Fix

Attachment 313379 [details] did not pass ios-sim-ews (ios-simulator-wk2):
Output: http://webkit-queues.webkit.org/results/3964977

New failing tests:
imported/w3c/web-platform-tests/IndexedDB/idb-binary-key-detached.htm
fast/dom/Window/window-postmessage-args.html
js/typed-array-mutated-during-set.html
Comment 8 Build Bot 2017-06-20 02:30:07 PDT
Created attachment 313385 [details]
Archive of layout-test-results from ews124 for ios-simulator-wk2

The attached test failures were seen while running run-webkit-tests on the ios-sim-ews.
Bot: ews124  Port: ios-simulator-wk2  Platform: Mac OS X 10.12.5
Comment 9 Build Bot 2017-06-20 04:21:23 PDT
Comment on attachment 313379 [details]
[PATCH] Proposed Fix

Attachment 313379 [details] did not pass mac-ews (mac):
Output: http://webkit-queues.webkit.org/results/3965441

New failing tests:
imported/w3c/web-platform-tests/IndexedDB/idb-binary-key-detached.htm
fast/canvas/webgl/arraybuffer-transfer-of-control.html
fast/dom/Window/window-postmessage-args.html
js/typed-array-mutated-during-set.html
Comment 10 Build Bot 2017-06-20 04:21:25 PDT
Created attachment 313392 [details]
Archive of layout-test-results from ews100 for mac-elcapitan

The attached test failures were seen while running run-webkit-tests on the mac-ews.
Bot: ews100  Port: mac-elcapitan  Platform: Mac OS X 10.11.6
Comment 11 Joseph Pecoraro 2017-11-02 21:49:25 PDT
I'm pretty sure the failing tests are just incorrect tests in WebCore. That said, I don't have the time to rebaseline this right now. So clearing flags.