diff --git a/bugs/issue-28dc02a2c229c9687f011b47b57e8916d92dc66b.yaml b/bugs/issue-28dc02a2c229c9687f011b47b57e8916d92dc66b.yaml new file mode 100644 index 00000000..05800d9a --- /dev/null +++ b/bugs/issue-28dc02a2c229c9687f011b47b57e8916d92dc66b.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: execution timeout into duk cmdline, add it to ecma262 test too +desc: "" +type: :task +component: duk +release: v0.9 +reporter: sva +status: :unstarted +disposition: +creation_time: 2014-01-17 20:22:54.809246 Z +references: [] + +id: 28dc02a2c229c9687f011b47b57e8916d92dc66b +log_events: +- - 2014-01-17 20:22:54.977146 Z + - sva + - created + - "" diff --git a/bugs/issue-43ac31846896102276580ae8e43d2b04af3057da.yaml b/bugs/issue-43ac31846896102276580ae8e43d2b04af3057da.yaml new file mode 100644 index 00000000..202aa6e7 --- /dev/null +++ b/bugs/issue-43ac31846896102276580ae8e43d2b04af3057da.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: ecma262 test result summary +desc: "" +type: :task +component: duk +release: v0.9 +reporter: sva +status: :unstarted +disposition: +creation_time: 2014-01-17 20:26:02.863927 Z +references: [] + +id: 43ac31846896102276580ae8e43d2b04af3057da +log_events: +- - 2014-01-17 20:26:03.016718 Z + - sva + - created + - "" diff --git a/bugs/issue-65b8a608c526e37b4fd27b3e0255b462c568c450.yaml b/bugs/issue-65b8a608c526e37b4fd27b3e0255b462c568c450.yaml new file mode 100644 index 00000000..a39535d1 --- /dev/null +++ b/bugs/issue-65b8a608c526e37b4fd27b3e0255b462c568c450.yaml @@ -0,0 +1,33 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: global code 'this' binding is undefined when global code is strict +desc: |- + Currently the caller is expected to provide the proper binding, and the + call handling then coerces the 'this' binding is it would for a function. + + In the non-strict case this yields the correct result even if the caller + misbehaves and provides a null/undefined as the this binding (perhaps the + calling code uses duk_call() instead of duk_call_method(), for instance, + like duk_cmdline.c used to do). + + In the strict case the 'undefined' value stands and causes various problems. + There is no problem if the caller uses duk_call_method() and pushes the + global object as the 'this' binding, and this is actually as designed. + + But perhaps this is unnecessarily brittle, and global/eval code should get + their 'this' binding disregarding the 'this' binding provided on the + value stack? +type: :task +component: duk +release: v0.9 +reporter: sva +status: :unstarted +disposition: +creation_time: 2014-01-18 00:44:39.705752 Z +references: [] + +id: 65b8a608c526e37b4fd27b3e0255b462c568c450 +log_events: +- - 2014-01-18 00:44:40.513830 Z + - sva + - created + - "" diff --git a/bugs/issue-6bb11f83617767ce219e5491239cf1502d61c0cc.yaml b/bugs/issue-6bb11f83617767ce219e5491239cf1502d61c0cc.yaml index fbd99e60..daa76ec7 100644 --- a/bugs/issue-6bb11f83617767ce219e5491239cf1502d61c0cc.yaml +++ b/bugs/issue-6bb11f83617767ce219e5491239cf1502d61c0cc.yaml @@ -57,3 +57,12 @@ log_events: - sva - assigned to release v0.10 from v0.9 - "" +- - 2014-01-17 20:22:12.908793 Z + - sva + - commented + - |- + Ecma-262 has a model where a testcase is "prepped". + + This might work quite well also for Duktape testcases. Test cases which + are "raw" and test for basic parsing of functions etc don't need the same + prepping, but this can prevented in test case metadata. diff --git a/bugs/issue-821b291e675b349d45816a1cb25cbba6eca13cd5.yaml b/bugs/issue-821b291e675b349d45816a1cb25cbba6eca13cd5.yaml index 38eca002..fb3b69f7 100644 --- a/bugs/issue-821b291e675b349d45816a1cb25cbba6eca13cd5.yaml +++ b/bugs/issue-821b291e675b349d45816a1cb25cbba6eca13cd5.yaml @@ -5,8 +5,8 @@ type: :task component: duk release: v0.9 reporter: sva -status: :unstarted -disposition: +status: :closed +disposition: :fixed creation_time: 2014-01-16 21:00:37.409343 Z references: [] @@ -16,3 +16,7 @@ log_events: - sva - created - "" +- - 2014-01-18 00:42:17.514719 Z + - sva + - closed with disposition fixed + - "" diff --git a/bugs/issue-a9ede55be64f0dac2e6a12c44de2c20dd2a04d7a.yaml b/bugs/issue-a9ede55be64f0dac2e6a12c44de2c20dd2a04d7a.yaml index 6986dc2d..04fc6190 100644 --- a/bugs/issue-a9ede55be64f0dac2e6a12c44de2c20dd2a04d7a.yaml +++ b/bugs/issue-a9ede55be64f0dac2e6a12c44de2c20dd2a04d7a.yaml @@ -14,8 +14,8 @@ type: :bugfix component: duk release: v0.9 reporter: sva -status: :unstarted -disposition: +status: :closed +disposition: :fixed creation_time: 2014-01-16 00:45:44.257933 Z references: [] @@ -25,3 +25,8 @@ log_events: - sva - created - "" +- - 2014-01-18 00:40:20.315590 Z + - sva + - closed with disposition fixed + - "Actual cause was a bug in pc2line where a diff_line higher than 127 would use\n\ + the full 32-bit (non-diff) encoding, whose value was set incorrectly.\n" diff --git a/bugs/issue-bf104e484a708544e37082142640d9ccd6a291e7.yaml b/bugs/issue-bf104e484a708544e37082142640d9ccd6a291e7.yaml new file mode 100644 index 00000000..4e5708bd --- /dev/null +++ b/bugs/issue-bf104e484a708544e37082142640d9ccd6a291e7.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: runtests prologue should not break a "use strict" in the test case +desc: "" +type: :bugfix +component: duk +release: v0.9 +reporter: sva +status: :unstarted +disposition: +creation_time: 2014-01-17 23:33:27.554424 Z +references: [] + +id: bf104e484a708544e37082142640d9ccd6a291e7 +log_events: +- - 2014-01-17 23:33:27.730450 Z + - sva + - created + - "" diff --git a/bugs/issue-e71a3351ef6d2fe0455e3f0befb87d5260443135.yaml b/bugs/issue-e71a3351ef6d2fe0455e3f0befb87d5260443135.yaml new file mode 100644 index 00000000..7160a924 --- /dev/null +++ b/bugs/issue-e71a3351ef6d2fe0455e3f0befb87d5260443135.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: lineNumber (and fileName) of SyntaxErrors should probably reflect the source being compiled +desc: "" +type: :task +component: duk +release: v0.9 +reporter: sva +status: :unstarted +disposition: +creation_time: 2014-01-17 22:01:49.236704 Z +references: [] + +id: e71a3351ef6d2fe0455e3f0befb87d5260443135 +log_events: +- - 2014-01-17 22:01:49.404640 Z + - sva + - created + - ""