test/webkit/function-declarations-in-switch-statement-expected.txt - Issue 1628013003: Update webkit test expectations for sloppy functions in case

Side by Side Diff: test/webkit/function-declarations-in-switch-statement-expected.txt

Issue 1628013003: Update webkit test expectations for sloppy functions in case (Closed) Base URL: https://chromium.googlesource.com/v8/v8.git@master

Patch Set: Created 4 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « no previous file | test/webkit/webkit.status » ('j') | no next file with comments »

OLD	NEW
1 # Copyright 2013 the V8 project authors. All rights reserved.	1 # Copyright 2013 the V8 project authors. All rights reserved.

2 # Copyright (C) 2005, 2006, 2007, 2008, 2009 Apple Inc. All rights reserved.	2 # Copyright (C) 2005, 2006, 2007, 2008, 2009 Apple Inc. All rights reserved.

3 #	3 #

4 # Redistribution and use in source and binary forms, with or without	4 # Redistribution and use in source and binary forms, with or without

5 # modification, are permitted provided that the following conditions	5 # modification, are permitted provided that the following conditions

6 # are met:	6 # are met:

7 # 1. Redistributions of source code must retain the above copyright	7 # 1. Redistributions of source code must retain the above copyright

8 # notice, this list of conditions and the following disclaimer.	8 # notice, this list of conditions and the following disclaimer.

9 # 2. Redistributions in binary form must reproduce the above copyright	9 # 2. Redistributions in binary form must reproduce the above copyright

10 # notice, this list of conditions and the following disclaimer in the	10 # notice, this list of conditions and the following disclaimer in the

11 # documentation and/or other materials provided with the distribution.	11 # documentation and/or other materials provided with the distribution.

12 #	12 #

13 # THIS SOFTWARE IS PROVIDED BY APPLE INC. AND ITS CONTRIBUTORS ``AS IS'' AND ANY	13 # THIS SOFTWARE IS PROVIDED BY APPLE INC. AND ITS CONTRIBUTORS ``AS IS'' AND ANY

14 # EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED	14 # EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

15 # WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE	15 # WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE

16 # DISCLAIMED. IN NO EVENT SHALL APPLE INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY	16 # DISCLAIMED. IN NO EVENT SHALL APPLE INC. OR ITS CONTRIBUTORS BE LIABLE FOR ANY

17 # DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES	17 # DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES

18 # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;	18 # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

19 # LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON	19 # LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON

20 # ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT	20 # ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

21 # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS	21 # (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS

22 # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.	22 # SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

23	23

24 WARN: shouldBe() expects string arguments	24 WARN: shouldBe() expects string arguments

25 PASS 20 is 20	25 PASS 20 is 20

26 WARN: shouldBe() expects string arguments	26 WARN: shouldBe() expects string arguments

27 PASS 20 is 20	27 PASS 20 is 20

28 WARN: shouldBe() expects string arguments	28 WARN: shouldBe() expects string arguments

29 PASS 20 is 20	29 FAIL -1 should be 20. Was -1.
	Michael Achenbach 2016/01/25 08:47:52 Maybe changing the .js file would look cleaner if Maybe changing the .js file would look cleaner if the new semantics are correct. Dan Ehrenberg 2016/01/25 08:52:20 In some cases, it seems like we've been avoiding c Show quoted text On 2016/01/25 at 08:47:52, Michael Achenbach wrote: > Maybe changing the .js file would look cleaner if the new semantics are correct. In some cases, it seems like we've been avoiding changing these webkit tests, as they're largely historical. Also, it's possible that in the future we'll want to restore the syntax error behavior (pending TC39)--its still unclear what semantics we want. That's why I decided to make this a change in expectations, not the test itself.
30 PASS successfullyParsed is true	30 PASS successfullyParsed is true

31	31

32 TEST COMPLETE	32 TEST COMPLETE

33	33

OLD	NEW