tests/lib/lib.status - Issue 10381133: Add 'fixnum' library to utils/

Side by Side Diff

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

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: tests/lib/lib.status

Issue 10381133: Add 'fixnum' library to utils/ (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Patch Set: Respond to review comments Created 8 years, 6 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 | Annotate | Revision Log

OLD	NEW
1 # Copyright (c) 2012, the Dart project authors. Please see the AUTHORS file	1 # Copyright (c) 2012, the Dart project authors. Please see the AUTHORS file

2 # for details. All rights reserved. Use of this source code is governed by a	2 # for details. All rights reserved. Use of this source code is governed by a

3 # BSD-style license that can be found in the LICENSE file.	3 # BSD-style license that can be found in the LICENSE file.

4	4

	5 # Run this test manually to verify that the fixnum library produces

	6 # the same results as native ints on a set of directed and random inputs.

	7 # Skip it when runnimng automated tests because it times out. This

	8 # test only makes sense on runtimes that support 64-bit integer

	9 # arithmetic natively, i.e., the VM.

	10 fixnum/int_64_vm_test: Skip
	Mads Ager (google) 2012/06/14 14:57:22 Thanks for adding the comment. Does it make sense Thanks for adding the comment. Does it make sense (in a follow-up change) to scale down the test with fewer cases and always run it on the VM? Then the manual step could be to change something in the test file itself to go through the full set of tests?
	11

5 [ $compiler == frog ]	12 [ $compiler == frog ]

6 crypto/*: Skip	13 crypto/*: Skip

7	14

8 [ $compiler == dart2js \|\| $compiler == dartc \|\| $compiler == frog ]	15 [ $compiler == dart2js \|\| $compiler == dartc \|\| $compiler == frog ]

9 math/*: Skip	16 math/*: Skip

10	17

11 [ $compiler == dart2js && $checked ]	18 [ $compiler == dart2js && $checked ]

12 # numbers typed 'int' are too big to fit in a JS int.	19 # numbers typed 'int' are too big to fit in a JS int.

13 crypto/hmac_md5_test: Fail	20 crypto/hmac_md5_test: Fail

14 crypto/hmac_sha1_test: Fail	21 crypto/hmac_sha1_test: Fail

15 crypto/hmac_sha256_test: Fail	22 crypto/hmac_sha256_test: Fail

16 crypto/sha1_test: Fail	23 crypto/sha1_test: Fail

17 crypto/sha256_test: Fail	24 crypto/sha256_test: Fail

18	25

19 [ $compiler == dartc ]	26 [ $compiler == dartc ]

20 i18n/*: Fail # Issue 3387	27 i18n/*: Fail # Issue 3387

21	28

22 [ $runtime == opera ]	29 [ $runtime == opera ]

23 *: Skip	30 *: Skip

OLD	NEW

« no previous file with comments | « tests/lib/fixnum/int_64_vm_test.dart ('k') | no next file » | no next file with comments »