Make test for output of backtrace less specific

usev6 · usev6 · commit cce58c243d54 · 2016-12-02T21:25:26.000+01:00
After the recent changes to backtrace handling this test
started to fail on rakudo-j. There are references to lines
in gen/jvm/CORE.setting which are causing the test to fail
because of the 's' in 'setting'.

Allowing additional lines in the backtrace still fits the test
description 'Thrown Failure outputs dual backtraces'.
diff --git a/integration/error-reporting.t b/integration/error-reporting.t
@@ -168,7 +168,7 @@ ok $b1 === $b2, "Backtrace does not change on additional .backtrace";
 }
 
 is_run 'sub s1 { sub s2 { fail("foo"); }; s2()(); }; s1();', {
-            err => rx/sub\ss2.*sub\ss1.*thrown<-[s]>+sub\ss1/
+            err => rx/sub\ss2.*sub\ss1.*thrown.*sub\ss1/
         }, "Thrown Failure outputs dual backtraces";
 
 # see http://irclog.perlgeek.de/perl6/2015-07-24#i_10947364 and commit c683fe9

Original file line number	Diff line number	Diff line change
`@@ -168,7 +168,7 @@ ok $b1 === $b2, "Backtrace does not change on additional .backtrace";`
`168`	`168`	`}`
`169`	`169`
`170`	`170`	`is_run 'sub s1 { sub s2 { fail("foo"); }; s2()(); }; s1();', {`
`171`		`- err => rx/sub\ss2.sub\ss1.thrown<-[s]>+sub\ss1/`
	`171`	`+ err => rx/sub\ss2.sub\ss1.thrown.*sub\ss1/`
`172`	`172`	`}, "Thrown Failure outputs dual backtraces";`
`173`	`173`
`174`	`174`	`# see http://irclog.perlgeek.de/perl6/2015-07-24#i_10947364 and commit c683fe9`