PR bin/55979

Add a sh ATF test to demonstrate a bug in the way that \0 characters
are dropped from scripts. This test will eventually be extended to
test other potential sh script input related issues.

When initially committed, this test should fail. It should succeed
when the fix for the PR is committed (soon).

Nb: this tests only the \0 related issues from the PR, the MSAN
detected uninitialised variable (struct field) can only be detected
by MSAN, as it has no visible impact on the operation of the shell
when running on any real (or even emulated) hardware.
(It will, however, also be fixed).

Add a new test program to test the "intermediate" shell built in
utilities. That is, not the low level ones that look like syntax,
but aren't: break/continue/return; not those which are really
just external programs that are built in for efficiency (printf,
test, and kill - though kill really needs to be built in) - those
should all have separate test programs (there is a test here for the
built-in echo, as that is an entirely different thing to /bin/echo);
and also not those for which there are other tests because of the
nature of the built-in (like exit, wait, shift, ...). Lastly not
"times" either as that just seems to be too hard to test rationally.

There is a test (well, framework) for ulimit and there's also t_ulimit.sh
one of those should go, but I am not yet sure which is the best way
to reconcile things.

Note: many (in fact) most of the test cases added here are either
entirely empty (no tests at all, beyond testing that the built-in is
in fact a shell built-in) or only very rudimentary tests - assistance
in fleshing those out would be welcome (the boilerplate is all here,
all that is needed is some actual tests to run...)

Add tests for pattern matching (filename expansion (glob), case statement
patterns, and variable expansion substring matching)

Currently (2018-07-10) all 3 sub-tests fail (sh bugs...)
Expect to see 14 (of 261) case matching sub-tests fail, 11 (of 167) filename
expansion (glob) sub-tests fail, and 6 (of 87) var substring sub-tests fail.

Also expect those numbers to reduce as sh bugs are fixed.

branches: 1.12.8; 1.12.10;

Add a test of sh syntax & parsing (first attempt anyway.)

new command substitution test from kre

Better tests for redircloexec and add t_shift (from kre)

New tests from kre

Add some redir-close-on-exec tests

remove old test

Add t_option, from kre (with minor edits from me)

Add new test

Visit the Bureau of Redundancy Department.
From Henning Petersen in PR 49191.

PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.2.2; 1.2.8;
New testcase to check limits flags for ulimit builtin.

branches: 1.1.2;
Deprecate tests/util.

Avoid using optional features in an unrelated test

In the additional tests just added, a use of the post-increment
++ operator was added. That was not the right thing to do,
as that operator isn't required to be implemented, and if not
would appear as if a ',' operator test had failed.

The actual tests of the ++ and -- operators verify that the shell
being tested actually implements them, before running the tests.
Doing that here would be overly burdensome, so instead just
use i += 1 (which is required) instead of i++ which is not. For
the purposes of the test it makes no difference (i ends up 1 bigger).

Note that this was not the (sub-)test that will currently fail, the
NetBSD shell does support ++ (and --) both pre & post, which is
why I didn't initially think of this issue.

More arithmetic tests for the optional ',' operator

The tests for the ',' operator were somewhat simplistic.
Add a few more (valid tests) that are slightly less so.

Expect the optional_comma subtest (of t_arith) to fail
after these changes, until a fix to /bin/sh is committed.
(Coming soon to a repository near you).

While here, fix a typo in a comment before andvar@ discovers it!

branches: 1.8.2;

Add basic tests for the forthcoming ',' '++' and '--' operators.
Until the support for those is committed to /bin/sh (and when testing
any other sh that does not support them) the new tests will be skipped.

Add a new test case "nested_arith" (that is, things like $(( 1 + $(( 2 )) ))
which will currently fail (some of the sub-tests, but this one stops on
first failure, so the test simply fails.) This will be corrected later today.

Add tests for the $(( )) assignment operators PR bin/50958

branches: 1.5.2; 1.5.4;

Grunge. I know I fixed this typo before... must have been in a different
couy of the test.

Verify that questionable characters don't have bad associates.

ok christos@

Don't confuse more capable shells by writing operator combinations
that could be interpreted as something different. That is, for our
shell +4++3 is just (+4)+(+3) and works fine. But others treat ++
as the increment operator. Same for --. Sprinkle spaces to taste.
(from kre@)

remove binary test and other cleanups (from kre)

New tests from kre

builting -> built-in, builtin in documentation and test description.

Add two new sub-tests to the echo test case of the t_builtins shell ATF test.

The first verifies that echo exits >0 when it encounters an I/O error on
its output (this part would have succeeded for a long time). It also
verifies the POSIX requirement that when most standard utilities (or
perhaps many rather than most) exit(>0) they must write a message to stderr.
Our sh's built in echo did not do that (nor does /bin/echo but that's not
relevant here).

The second demonstrates (on an unfixed built-in echo) a bug reported in
private e-mail by Oguz <oguzismailuysal@gmail.com> where once an instance of
the built-in echo has detected an I/O error, all later invocations of
the built-in echo, with no I/O errors of their own, also exit(1) (the error
status on stdout is not cleared, each echo sees the "I/O error occurred" and
does exit(1)).

In this second sub-test, the "2>&-" on the first echo command is simply
an artifact caused by the test harness - the "check" function verifies
that exit((>0) requires a message on stderr (and vice versa), but that
only applies to most (or many) utilities, echo is one, but sh is not.
In the second test, the exit status comes from sh - sh is permitted to
write to stderr (via the echo command it runs in this case) and still
exit(0). But the check function in the test does not understand that
subtlety. So, we simply suppress the stderr message by closing stderr
(the first of these two new sub-tests has verified that the message exists)..

branches: 1.5.2; 1.5.8;

Add several sub-tests to the test for the "eval" builtin,
including testing correct handling of error cases.
One of these new tests located a bug which will be fixed
within minutes of this commit ...

While doing this, move the test that was used only in the
echo builtin test case (testing if the NetBSD shell was being
tested) into a utility function, and also call it in the eval
test, so NetBSD specific behaviour of what is unspecified in
the standard can be checked to ensure it is not accidentally
altered.

branches: 1.4.2;
Add a new test case for NetBSD specific readonly tests.
Add more sub-tests to the export_nbsd test case.
In both cases the new -q and -p VAR options are tested.

Add more subtests to the export and readonly built-in commands test cases.

In particular, add a readonly test to detect the bug that was just fixed...
(but there is more than that one added here).

Also, allow zsh to run more of these tests than it did, what is a builtin
command most places (including in POSIX) can be a reserved word in zsh!

Oops, this is 2018, not 2017 ... cut&paste (affects just copyright notice)

Add a new test program to test the "intermediate" shell built in
utilities. That is, not the low level ones that look like syntax,
but aren't: break/continue/return; not those which are really
just external programs that are built in for efficiency (printf,
test, and kill - though kill really needs to be built in) - those
should all have separate test programs (there is a test here for the
built-in echo, as that is an entirely different thing to /bin/echo);
and also not those for which there are other tests because of the
nature of the built-in (like exit, wait, shift, ...). Lastly not
"times" either as that just seems to be too hard to test rationally.

There is a test (well, framework) for ulimit and there's also t_ulimit.sh
one of those should go, but I am not yet sure which is the best way
to reconcile things.

Note: many (in fact) most of the test cases added here are either
entirely empty (no tests at all, beyond testing that the built-in is
in fact a shell built-in) or only very rudimentary tests - assistance
in fleshing those out would be welcome (the boilerplate is all here,
all that is needed is some actual tests to run...)

t_cmdsub.sh: fix naming of head() of cmdsub_paren_tests

Add a new test to verify correct operation when a command substitution
produces output with a very large number of consecutive embegged \n
characters.

This test is currently expected to fail (as of commit date) but is not
marked as atf_expect_fail as the shell should be fixed to avoid the
problem quite soon. Until then almost anything might happen to the
sh that runs this test (from just plain wrong results, to core dumps,
even possibly the right results, though that's unlikely).

Whie doing this, get rid of the duplicate implementation of the
nested_cmdsubs_in_heredoc test (which was achieving nothing). I know
how I managed to do that, but on advice of counsel, I ... (it was
just a harmless waste of a tiny amount of CPU time "compiling" the test,
just like writing "x=0;" on consecutive lines....)

Add a test case for here documents positioned outside `` with the
redirect operator inside the ``. Move the one similar test using
$( ) into its own test case (and expand that test as well.
The `` case was omitted before, as no shells (including NetBSD) were
parsing it correctly, Now the NetBSD shell does, so ... (from kre@)

Added tests collected by Sven Mascheck
http://www.in-ulm.de/~mascheck/various/cmd-subst/
which test cases of ')' being embedded in command substitutions.
(from kre@)

Finish these tests (or at least, fill in the place holder tests
with actual code ... tests are never really finished.) One of these
new tests was how the bug in PR bin/50993 was discovered. (from kre@)

new command substitution test from kre

This test tests nothing not tested elsewhere, and doesn't
do a very good job of that. Bang! (from kre)

branches: 1.1.2;
Deprecate tests/util.

Finish TEST_SH - all tests should support it now.
Misc other KNF changes, minor bug fixes, and a few minor
extra tests added. (from kre@)

branches: 1.1.2;
Deprecate tests/util.

Remove the trap_zero__explicit_return test case - it was testing undefined
behaviour (and failed with the NetBSD shell, and was marked as expected to
fail.) Other shells do different things. The test was worthless, and is
now gone.

OK christos@

Improved handling of TEST_SH so that it is possible to define it
to the name of a shell, plus options that shell needs to run it
in the correct mode to be tested: eg: TEST_SH='bash -o posix'
Also finished the implementation of tests of "set -n" now that
the NetBSD shell supports that as it should. (from kre)

Test improvements from kre

branches: 1.3.2;
Although this does not fail, add a case for the discussion in PR bin/46327.

ksh trap has been fixed.

Deprecate tests/util.

Adjust the tilde expansion test to deal with (very) recent changes
to what the shell produces for tilde expansions, when the expansion
of the tilde prefix ends with '/' and the character immediately following
is another '/' - previously /bin/sh (and most other shells, but not all)
retained both slashes, and this test expected that behaviour.

No longer, now only one of the two will appear. Adjust the expected
test results accordingly, and add an extra loop iteration to make sure
this is thoroughly tested (one more tilde expansion value).

Also, add two new test cases that test for the new (explicit - though
it was always stated this way, but not as explicitly) that if HOME is
an empty string (not unset - that remains an unspecified case, as it
was) then the expansion of ~ must generate "", and not nothing.
The current test was unable to distinguish those two, since it
simply looked for characters in the output, so add a new test cases
explicitly to test for this particular case. This also means (also
previously in the standard, but not as explicitly) that shells are
not permitted to decide "The ~ expansion produces an empty string, that
is weird, let's generate something else instead" which some shells were
doing.

Fix an (apparent) ancient ash bug, that was apparently fixed sometime
in the past, but managed to re-surface...

The expression "${0+\}}" should expand to "}" not "\}"
Almost all other shells handle it that way (incl FreeBSD & dash).

Issue pointed out by Martijn Dekker.

Add ATF sub-tests for the 4 old var expand operators (${var+word}
${var-word} ${var-word} and ${var?word} - including the forms
with the ':' included) and amongst those tests include test cases
for this issue, so if the bug tries to appear again, we can squash
it quicker. (The newer pattern matching operators are already
well tested as part of testing patterns.)

PR bin/54112

Fix handling of "$@" (that is, double quoted dollar at), when it
appears in a string which will be subject to field splitting.

Eg:
${0+"$@" }

More common usages, like the simple "$@" or ${0+"$@"} end up
being entirely quoted, so no field splitting happens, and the
problem was avoided.

See the PR for more details.

This ends up making a bunch of old hack code (and some that was
relatively new) vanish - for now it is just #if 0'd or commented out.
Cleanups of that stuff will happen later.

That some of the worst $@ hacks are now gone does not mean that processing
of "$@" does not retain a very special place in every hackers heart.
RIP extreme ugliness - long live the merely ordinary ugly.

Added a new bin/sh ATF test case to verify that all this remains fixed.

Add two new test cases to add more tests for $@ expansions
(and a few more subtests in an existing test case).

The two new test cases currently fail, because of issues with
expanding "${1+$@}" which will (hopefully) be fixed soon.
(This looks to have been broken sometime during 2013 ... then I
made it even worse with some of the parser changes a while ago,
though the end result is that it appears less broken than it
really is.)

branches: 1.19.2;

Add a test case for PR bin/53201

Currently this test case will fail, a fix is coming soon (not worth
marking this as an expected failure.)

This test case and the initial bug report comes from
Martijn Dekker's modernish (shell/test set).

branches: 1.18.2;

Add a new sub-test to validate ~ expansions.

Currently testing ~user is too much effort to contemplate (other than
assuming that it works in order to verify that it works...) so only bare ~
is being tested for now. Maybe someday...

Right now (@ time of commit), this new test is expected to fail, as ~
expansions are horribly badly broken (have been for months, some forms
for much longer) in all but the simplest of uses. Fix for that coming
very soon.

Complete the special request by quoting chapter & verse from POSIX
as to why ${011} is ${11} and not ${9} (that is, why we interpret it
that way, the "why could it not be the other way?" is just "because
that is not how it was ever implemented".

By special request, add a check that ${011} is ${11} not ${9} (etc) and
that ${08} is not an error.

Add 3 new subtests to the shell_params test case. These test currently
broken behaviour (so for now, 3 of 15 subtests will fail). This will
be corrected later today.

Add a new test case wrap_strip based upon strip (ie: cut&paste.. to start)
but with \ newline line continuations inserted at strange places.

For the shell as it is today, since strip passes, wrap_strip should
automaticallty pass as well (and does), as the \ newline combination
is simply removed, producing identical input to that of strip.

However, for accurate line counting ($LINENO: coming soon) newlines (no
matter the context) cannot simply "go away" - we have to know where they
occur(ed) (perhaps long after the text was read) so we know what line
number we are actually processing. This new test case is (perhaps just
part) of future-proofing that the modified code does not break anything.

More test sub-cases for the dollar_hash ( ${#...} ) test.
Upi really (really!) don't want to know!

Also, add a comment (in another section) and avoid giving messages
to atf_fail that include newlines - AFT really doesn't like that.
Instead, convert the \n's to ;'s so at least the content is retained.

Add a test case for the various ways that ${xxx} expansions, which
contain a # character, can get parsed (which amounts to 86 extra checks,
any Australian can tell you why I decided to stop there and not add one
more...)

branches: 1.11.2;

PR bin/52090 - the $* tests are no longer expected to fail.

PR bin/52090

Add 5 new test cases to test various ways that $* can be expanded.
Currently 3 of the 5 are marked as "expected to fail" because of the
bug in this PR.

Add new test case in to check (coming) bug fix for newly discovered
ash based shell bug
echo ${unset_var##$(echo a)}$(echo b)
should say "b" but instead says "a" ... the first "echo a" is not
evaluated because it cannot possibly match an unset variable, but is
not removed from the list of command substitutions, when the shell
needs to execute the 2nd cmdsub, "echo b" should be at the head of
the list, but isn't, "echo a" is still there...

This test should fail (for now) - should show 4 of 40 subtests failing.
It isn't marked as atf_expect_fail as the fix for this will be coming
later today (I will just wait at least 1 b5 build cycle so the failure
can be observed).

Detecting the bug, and the fix, are from FreeBSD.

branches: 1.8.2; 1.8.4;
use "" so ${TEST_SH} is expanded.

PR bin/51027 - tests for shell positional parameters, including
testing that $10 is correctly parsed as ${1}0 and not as ${10}.
More than that though. (from kre@)

Added more test cases, more exhaustive testing. (from kre)

PR/43469 has been fixed

undo accidental commit

Add a test for PR/50827

Fix PR bin/48202 [non-critical/low]:
sh +nounset and `for X; do` iteration fails if parameter set empty
by applying and testing FreeBSD's patch of Oct 24 2009 for this; see
http://svnweb.freebsd.org/base/head/bin/sh/expand.c?r1=198453&r2=198454
Also created an ATF test in tests/bin/sh/t_expand.sh for this error and
corrected a space->tabs problem there as well.

branches: 1.1.2; 1.1.4;
Deprecate tests/util.

Delete the dummy "always fail" test.

It has demonstrated that the code elsewhere will successfully
handle sub-test errors, should any occur, so has served its purpose.

Always run all sub-tests in a test case.

Previously, as soon as a sub-test in a test case failed,
the sub-test failed along with it, and no further sub-tests
were run, which would mean "fix one, run it again, fix
another, run it again, ...". Now all the sub-tests that
fail are reported in each run. Many of the other sh
ATF tests work the same way (approximately anyway).

This does mean that it is no longer possible to do (as was
once done here)

atf_expect_fail "whatever reason"
run_the_sub_test
atf_expect pass

to allow for just one known sub-test to fail, and expect all
the others to work, as the individual sub-tests no longer atf_fail.

This change would have made no observable difference, as all
the sub-tests in all the test cases currently pass.

That's no fun! So I added a new test case which contains a
bunch of sub-tests, some of which fail. Don't bother attempting
to work out why, they fail because they were deliberately broken,
that is, broken in the test, not in sh.

Once this update has settled for a day or so, I'll remove that
new test case again (its sub-tests were simply stolen from other
test-cases, there's nothing new, and then some mangled, so they
fail).

While here, since there were (more or less rote) changes throughout,
some sh formatting style changes, 80-col, ..., slipped in as well.

Test field splitting as used by the read built-in.

This includes a couple of sub-tests which test for the bug from
PR bin/58749

Other aspects of read should be tested elsewhere (someday).

branches: 1.7.18;

NFC: Added some comments (about other comments)

We currently parse var expansions like "${x-"a b c"}" incorrectly
according to POSIX (and ancient tradition) though in a way that is
generally unexpcted (there are 2 quoted strings there, according
to the standard, "${x-" and "}" and 'a b c' is unquoted.) This has
never been fixed in our sh, as like in many other shells, it is just
a little unbelievable, most people expect that inside the {} is a
whole new ballpark, and everything starts again, and it does in cases
like "${x%"a b c"}" (the newer matching operators.) There have been
comments in this test explaining how the test is actually testing for
incorrect behaviour for a while now.

But I have since learned of POSIX bug #221 (2010), the resolution of which is
to make the problem case unspecified. This will not actually become part
of posix until the next major version (POSIX 8) whenever that appears (still
years away I expect) - but at least we now can feel happier about the
way our code works and not worry quite so much about testing that incorrect
code keeps working incorrectly....

Paranoia: add a new test case testing that $(( )) results get split
by IFS just the same as any other expansion (split when they should be,
and not when they shouldn't).

Good thing I did ... this discovered a regression in the new expand
code (from an hour or three ago) where quoted arith expansions are
being split, and shouldn't be. (on the other hand, when they should
be split, they are being split correctly, so that's good...)

No need to worry too much about this, in real life (as opposed to
torture tests) no-one ever puts digits in IFS, and a $(( )) expansion
only ever contains digits, so in practice, splitting never happens,
whether because it is quoted, or just becaue there is nothing to split.

The FreeBSD shell does it correctly (they do word splitting using a
totally different mechanism than we do) - I will find where I missed
testing for quoted expansions later tonight. Until that happens,
expect a test failure from t_fsplit:split_arith

While here add more comments in the other test casess (one had a comment
already) that our shell parses incorrectly (this is a parsing problem,
not an expansion problem, and the bug has existed forever .. and is
shared by bash).

That is, in an expression like "${var:-word}" the whole thing (including
word) is quoted by the double quotes, and in "${var:-"word"}" the
expansion is quoted, but 'word' is not, the 2nd " (the one before 'w')
ends the opening quote, and the third (before }) turns quoting on
again (it is required that there be an even number of unquoted quotes inside
a ${} expression, so things like "${var:-"word} are simply invalid.)
Another way of saying this, is that if the { is quoted (for which the
only way is using " to get to this kind of expansion at all) the }
must also be quoted (" quoted). There is no quote nesting here.

This also means that in "${var:-'word'}" the single quotes are just
characters, they are quoted by the "" that surround them, just as in
"a 'string' containing quotes", but "${var:-"'word'"}} is valid and
contains a single quoted word.

Note that this is different than the patetrn-match/trim expansions
( ${var%pattern} etc) where any surrounding quotes do not affect the
pattern, and all forms of quoting can be used in it - but it always
parses as a pattern, and is never subject to filename expansion, so
a '*' in it that is to mean "match any string" does not need special
quoting to avoid it expanding to file names, regardless of whether
the ${var%*} is quoted or not, but a * that is to be matched as a
character literally does need to be quoted.

I will probably file a PR about this bug sometime, but as it is
very old, and doesn't every seem to bother anyone (and is shared by
bash) there isn't any big hurry to open yet another verry messy can
of excrement to fix it...

This does mean that the FreeBSD shell "fails" some of our tests.
(The test is wrong, their shell is correct.)

Add some extra sub-tests checking splitting of ${#var} - just for my
piece of mind (to verify I was not breaking anything here.)

Also added some commentary better explaining why one of the tests of splitting
quoted variable expansions is almost certainly incorrect (both the tests,
and what sh does) ... though bash does the same as us, so all is not lost!

Finish TEST_SH - all tests should support it now.
Misc other KNF changes, minor bug fixes, and a few minor
extra tests added. (from kre@)

Set TEST_SH

Added more test cases, more exhaustive testing. (from kre)

branches: 1.1.2;
Deprecate tests/util.

PR bin/53550

/bin/sh's processing of here doc expansions has changed. Now it happens
in the context of the parent shell, so side effects are visible there,
just like all other redirection expansions.

We need to stop testing that that doesn't happen, and instead test
that it does. This is that change.

Add another test case which is testing exactly the example from the PR
(well, with a different exit status, 1 is too generic and could happen
by accident) to make sure we don't reintroduce that bug sometime.

Add a new test case to check for correct parsing and execution
of a few bizarre here document usages, such as

: << do | for x in xxx
do
do echo $x
done

which should work, but never have done. (See the source for others).

This test case will currently fail, until the bug is fixed
(already done, to be committed very soon).

Add sub tests to the quoting test case, to demonstrate a parsing
bug (and its fix (depending upon whether the test is run against
an unfixed, or fixed, shell).

An obvious indication of the failure is the following (one of the
new sub-tests)

p=A
cat <<EOF
${p+\%$p\%}
${p+%$p%}
EOF

which should output

\%A\%
%A%


as a here doc is treated as a double quoted string, except
that the " character is just a character. In such a string,
the \ is only an escape character when the following character
is special, otherwise it represents a literal \ (which is the
case here).

An unfixed shell will omit the backslashes in the output.

It gets even more wrong if the % chars are replaced by "
(double quote) chars, which should make no difference, other
than the corresponding change, in the output. But doesn't
(it doesn't even produce output broken in a similar way).

This one is a harder case to be specific about however,
as while the fixed (and expected in the test) output is what
is technically correct, only a few shells actually produce
it, most generate something different (but not all the same.)

branches: 1.6.14; 1.6.16;
Added lots more end delimiter tests (some weird cases...). Also
use printf %s instead of echo, as there are embedded \ chars in
some of the strings, and some other (nameless) shells insist on
treating \ in the args to echo as something special... (from kre@)

PR bin/50993 - lots of new here document tests to validate all of
the changes made to fix that PR. LOTS more tests... A few general
improvements to the way the tests work and results are reported
as well. (from kre@)

Cleanup left over (dead) debugging code (from kre)

Improved handling of TEST_SH so that it is possible to define it
to the name of a shell, plus options that shell needs to run it
in the correct mode to be tested: eg: TEST_SH='bash -o posix'
Also finished the implementation of tests of "set -n" now that
the NetBSD shell supports that as it should. (from kre)

more tests from kre

branches: 1.1.2;
Deprecate tests/util.

This test just tested that nul chars in shell input were silently
ignored. Since we no longer do that, the test is kind of pointless.
But rather than delete it, just mark it as "expected fail" for now,
until it is clear that the changed nul behaviour is to remain.
Then the test can be changed to validate that nul chars cause errors...

branches: 1.1.8;
PR bin/55979

Add a sh ATF test to demonstrate a bug in the way that \0 characters
are dropped from scripts. This test will eventually be extended to
test other potential sh script input related issues.

When initially committed, this test should fail. It should succeed
when the fix for the PR is committed (soon).

Nb: this tests only the \0 related issues from the PR, the MSAN
detected uninitialised variable (struct field) can only be detected
by MSAN, as it has no visible impact on the operation of the shell
when running on any real (or even emulated) hardware.
(It will, however, also be fixed).

fix various small typos, mainly in comments.

More tests that were doing ... | atf_check ...

which allows the atf_check to fail without causing the test to fail
(unless this is the (very) last command in the test case, in which case it
will fail with what can be interpreted as an internal error)/

Check for this failing and explicitly atf_fail whwn it does.

Fix typo (s/supress/suppress/).

branches: 1.6.4;
Add a test case for "set -X".

Currently (or when testing any shell that does not support -X) the
test will be skipped (also for [m]ksh (but not ksh93 etc) where there
is an absurdly badly named -X option, skip the new test for them as well.)

When -X appears in /bin/sh, this will verify that it is probably working
(the test is MUCH more gruelling than any rational use of -X would be.)

branches: 1.5.2;

Add some tests for the (likely forthcoming) pipefail option (modelled
after than in ksh and bash, and the similar thing in zsh) for which a
request has been made for support in the NetBSD sh.

Until the support is committed, the test will be skipped.

Guard against EVN being set, and possibly referencing an unset
variable, when we are running tests with sh -u

Correct the way that TEST_SH is used so that the tests work as
intended when TEST_SH is specifies a shell that needs options (like
sh -F, or bash -o posix). (from kre)

Improved handling of TEST_SH so that it is possible to define it
to the name of a shell, plus options that shell needs to run it
in the correct mode to be tested: eg: TEST_SH='bash -o posix'
Also finished the implementation of tests of "set -n" now that
the NetBSD shell supports that as it should. (from kre)

Add t_option, from kre (with minor edits from me)

Fix building the debugging tarball of the directory tree created for
the pathname matching tests ... this is not used in any way in a normal
test run, but if there are problems, one needs a mechanism to discover
whether the issue is with the code that creates the directory tree in the
test, or with the matching (either what the test expects to happen, or
what the shell actually does). The couple of lines being fixed here make
that mechanism work --- I have had this in my private sources for years
now, but never got around to committing it. It is time. NFC for any
normal test run.

t_patterns.sh: fix naming of head() of filename_expansion

Make sure we have enough free inodes before running the filename_expansion
test.

branches: 1.4.2;

It turns out there are more cases where escaping of meta-chars
was not being done properly (too many different code paths inside sh)
so add even more subtests to the case_matching test case to verify
that all (that I can think of for now anyway) get fixed when this
gets cleaned up. The case_matching test case still fails, but now
6 of its subtests should fail (until sh is corrected ... soon).

Add some tests to detect the presence of a bug in sh reported by
Martijn Dekker (private e-mail.) Variable expansions that are
double quoted result in literal characters (nver pattern matching
meta chars.) This includes '\' (that one was the bug.)
[On the other hand, a variable in a case pattern expansion that is
unquoted, produces a pattern, and in that the \ character can be
used to excape other pattern meta-chars (and itself.]

This addition will cause the case_matching test case to fail (two
of the newly added sub-tests fail) until fixes to /bin/sh are made.
(That is comiung soon, the code exists already.)

branches: 1.2.2;

Several improvements to this test...

In the filename expansion test, don't insist on testing cases
of [^a] anything not an a) (etc) - while almost all shells allow
^ there (as in regular expressions) this is not standard sh/glob syntax
(! is used for that, not ^). Use of ^ as first char after '[' in a []
match has unspecified behaviour. So, check if the shell being
tested supports ^ used this way before running the tests of ^ in [].
This makes no difference at all when testing the NetBSD sh which
does allow ^ for that use case.

Fix an obvious (in hindsight) stupidity in the case pattern tests
(a cut/paste/forget-to-fix type error).

Many cleanups, including some additional sub-tests, for the var
substring matching (just a couple of actual fixes to the tests).
(This was the last added, and least polished part - still is.)

This makes no difference to the filename expansion tests (11 of 167
still fail), the fix reduces the failing case match tests from
14 of 261 to 13 of 261. For var substring tests, the failure
has changed from 6 of 87 to 8 of 99. (Some) Fixes to sh will appear
soon.

For comparison, using this version of the test, dash passes all case
and var substring tests, and (aside from the [^...] tests which it
does not implement) fails 4 of the filename tests. bash fails one
case test (a bash oddity in interpretation of the spec, which is unique
to bash amongst shells I have tested) and one filename expansion (all
var substring tests pass). Other shells are much worse (though the
freebsd shell results were coloured by the version of their shell I
tested still having the [[:xxx:]] always matches '[' bug, which is
fixed in later versions of their shell)

Add tests for pattern matching (filename expansion (glob), case statement
patterns, and variable expansion substring matching)

Currently (2018-07-10) all 3 sub-tests fail (sh bugs...)
Expect to see 14 (of 261) case matching sub-tests fail, 11 (of 167) filename
expansion (glob) sub-tests fail, and 6 (of 87) var substring sub-tests fail.

Also expect those numbers to reduce as sh bugs are fixed.

Deal with a lot more pipes into atf_check missed last time.

Fix a test that has been (unnoticed) failing ever since printf(1) was
changed to exit(1) when it detects a write error to stdout.

Running printf with stdout closed is guaranteed to generate such a
condition.

Until the previous commit, while the test case was actually failing
(stderr was expected to be empty. and was not) this was unnoticed.
We don't want the output (obviously), we also don't want the error
message, so just direct the latter to /dev/null.

Correct a systematic atf_check usage error. One must not pipe into
atf_check and simply expect it to work - the shell is permitted to,
and our shell currently does, run all commands in a pipeline in subshell
environments - when atf_check attempts to exit to indicate failure, it
only exits from that subshell, and the rest of the test continues, usually
to indicate success

Instead, when it is necessary (or just convenient) to pipe into atf_check
check the exit status of the pipeline (if atf_check is not last, which it
would usually be, then we would need the pipefail option set - there are
currently no such cases), and explicitly fail if atf_check did not exit(0).

Handle the (very) recent change to printf(1) - when writing to a closed
stdout printf(1) now issues an error message, hence stderr in such cases
should not be empty, rather than should be empty. Adapt to that.

branches: 1.10.6;

Add a new test case to test <> (open for input & output),
includion a test to make sure that the file doesn't get truncated.

Add new subtests to the "incorrect redirections" test case, to
validate correct behaviour of the shell when redirections fail in
various scenarios, including when the redirect is the whole command.

More along these lines are really needed, but this is better than nothing.

All the added tests pass on the /bin/sh currently in netbsd HEAD.

branches: 1.9.14; 1.9.16;

Add another test for the 48875 fix fallout...

Add a test for fd redirections on functions in loops (the etcupdate issue)
and also fix a quoting bug which was causing a test to fail, though
ATF was ignoring (an ATF bug to be investigated later.)

OK christos@

PR bin/48875 PR bin/51123 This adds tests more that verify fide descriptor
redirection works correctly (including that the bugs reported in those PRs
are fixed.) Note that the tests for 48875 are slow, so one of the new
test cases ends up running > 25 seconds (just doing sleeps) - each individual
test is just a few seconds, but there are several of them.

OK christos@

More redirect tests, in particular, tests for redirects to/from
file descriptors outside the 0..9 range, and complex fd
reassignments. Also test that the shell can cope with the
value of ulimit -n changing (downwards, up is harmless)
(Freom kre@)

Avoid relying on the test shell correctly implementing $(( ))
in order for some of the redirect tests to terminate. (from kre@)

Added more test cases, more exhaustive testing. (from kre)

Improved handling of TEST_SH so that it is possible to define it
to the name of a shell, plus options that shell needs to run it
in the correct mode to be tested: eg: TEST_SH='bash -o posix'
Also finished the implementation of tests of "set -n" now that
the NetBSD shell supports that as it should. (from kre)

Add new redirection test, from kre

Add new test

Skip the test of non-posix behaviour if we are deliberately trying
to be posix compatible (POSIXLY_CORRECT is set).

Add a test for opening files with exec "when" in posix mode (close-on-exec
should not get set.) While here, remove the (unused) runhelper() function.

branches: 1.3.6;

Add a new test case to validate N>&N redirect disables close-on-exec.
OK christos@

Better tests for redircloexec and add t_shift (from kre)

Add some redir-close-on-exec tests

When embedding a command in a subshell "( ... )" avoid accidentally
producing (( (when the cmd starts with a '(' as that as a reserved
sequence (according to posix) and some shells do treat it specially.
So, force a space after the enclosing '(' to avoid the problem.
For symmetry, put a space before the concluding ')' as well, though
there is nothing special about )). (from kre@)

Finish TEST_SH - all tests should support it now.
Misc other KNF changes, minor bug fixes, and a few minor
extra tests added. (from kre@)

Correct one test that (while OK for NetBSD) insisted on behaviour
that is not required by the standard. The test now allows either
of the two allowed responses. Also add commentary correcting
erroneous comments about what is correct, and incorrect. (from kre)

branches: 1.1.2;
Deprecate tests/util.

In !TINYPROG versions of sh, make the builtin "shift" builtin command
perform a rotate instead or shift if given a numeric arg (which is
otherwise an error).

"set -- a b c; shift -1; echo $*" will echo "c a b".

While here, make the shift builtin comply with POSIX, and accept
(and ignore) a '--' arg before the shift (or rotate) count.

Document the variant of shift in sh(1)

Adapt the shell test for shift to not expect "shift -1" to be an
error, test that rotate works as expected, and include some tests
that use the (useless, but required) "--" arg.

branches: 1.2.28;

Use valid (standard) shell syntax, in anticipation of /bin/sh enforcing
it sometime soon (perhaps.)

Tests for the shift builtin (from kre)

s/synax/syntax/ in test description.

More tests that were doing ... | atf_check ...

which allows the atf_check to fail without causing the test to fail
(unless this is the (very) last command in the test case, in which case it
will fail with what can be interpreted as an internal error)/

Check for this failing and explicitly atf_fail whwn it does.

Correct a systematic atf_check usage error. One must not pipe into
atf_check and simply expect it to work - the shell is permitted to,
and our shell currently does, run all commands in a pipeline in subshell
environments - when atf_check attempts to exit to indicate failure, it
only exits from that subshell, and the rest of the test continues, usually
to indicate success

Instead, when it is necessary (or just convenient) to pipe into atf_check
check the exit status of the pipeline (if atf_check is not last, which it
would usually be, then we would need the pipefail option set - there are
currently no such cases), and explicitly fail if atf_check did not exit(0).

Add a test for the bug in PR bin/53712 ( " { } > out " core dump )
Tested with both fixed, and unfixed, versions of /bin/sh (and in
posix mode, where that is a syntax error).

branches: 1.9.2; 1.9.4;

Make the $'...' syntax tests test what is supposed to work, rather than
what I thought was required (just a couple of changes...).

Add a few more sub-tests to the $'...' syntax tests.
Remove dome debug noise accidentally left in when the test was first added.
(This still does not matter just yet, but should do soon.)

Add a basic test for $'...' quoting (roughly C ctyle strings).
This test will be skipped on shells (such as /bin/sh in -current as of
the date of this commit) which do not support $'...'

While here fix a typo in a comment (there are probably more...)

PR bin/48498 PR bin/52426

Add two new sh syntax test cases to check for bug fixes for the parser
problems (syntax errors unidentified) reported in the two PRs.

In the latter case, also include some tests that test similar
looking, valid, syntax - to make sure the fix for the PR does not
break code that should not fail. This is not needed for the earlier
PR as other tests, and just normal parsing, is sufficient.

These tests have been verified to fail with a current /bin/sh and to
pass with the sh updates that are to be committed soon -- and because that
fix is expected within hours, the tests are not marked as expected to
fail, just let them actually fail for now.

Give this test a promotion! This was the test that enabled the sh's
STACKSTRNUL() bug to eventually be found. Not any of the test cases
directly - the shell running the tests (the same /bin/sh) managed to
build one of the f_variable_syntax sub-tests incorrectly, and that was
enough to eventually allow the bug to be located and squashed.

Like all good promotions, this one comes with increased work, and no extra pay.

Fix a really stupid typo/thinko that was preventing many of the
redirect syntax sub-tests from being attempted.

Add two new sub-tests to the c_line_wrapping test case.

These should detect if the errors that caused MAKDEV to fail and
pkgsrc/pkgtools/cwrappers to fail to build (problem detected in
libnbcompat/configure) ever return.

Also fixed one of the other sub-tests so that it actually does what
it should - no idea how this one has been passing, it did not for me
when I was checking the new ones (but perhaps in the interim I have
fixed something else in sh, the problem was in the area I have been
playing, and I originally debugged the new tests using a newer version
of /bin/sh than has yet been committed.)

One more weird test of parsing (and correctly understanding) words
whose meaning is defined entirely by context.

For those who read commit messages, and want a (small) challenge,
work out where (and what) to insert as punctuation/operator chars
in the following to produce 3 ines of output, and what those will be:

for in in in do in do case in in in echo do do echo in esac done

(There are no comments, quotes of any kind, or any kind of sub-shell,
including cmd substitutions) With correct non alpha-numeric chars added,
it works.

Add a test of sh syntax & parsing (first attempt anyway.)

tests: replace deprecated '-s eq:...' with '-s exit:...'

Finish TEST_SH - all tests should support it now.
Misc other KNF changes, minor bug fixes, and a few minor
extra tests added. (from kre@)

more robust ulimit test that works with most variants of bourne shells.

branches: 1.1.4;
New testcase to check limits flags for ulimit builtin.

tests: replace deprecated '-s eq:...' with '-s exit:...'

Finish TEST_SH - all tests should support it now.
Misc other KNF changes, minor bug fixes, and a few minor
extra tests added. (from kre@)

Implement TEST_SH for this test, add a test or two, and also some
commentary to explain some of the weirdness of shell quoting. (from kre@)

Add a test for PR/50827

branches: 1.2.2;
PR/43597 was fixed

Deprecate tests/util.

More tests that were doing ... | atf_check ...

which allows the atf_check to fail without causing the test to fail
(unless this is the (very) last command in the test case, in which case it
will fail with what can be interpreted as an internal error)/

Check for this failing and explicitly atf_fail whwn it does.

New tests from kre

Avoid leaving turds in /tmp. (from kre@)

More tests, add protection against shells that allow wait N
to wait for the same process over and over again (forever) (???)
This test now takes slightly over 20 seconds to complete (elapsed
time) caused by all the waiting on sleep commands being run in
the background. (from kre@)

Complete implementation of TEST_SH, use builting kill (which does
work, now anyway) rather than working around a defect by using
/bin/kill (if the shell is broken, the test should fail, not succeed)
and test more aspects of the wait builtin in the kill test. (from kre)

uncomment clean up

Test improvements from kre

Add delay to improve stability of test

another wait test.

branches: 1.1.2;
Deprecate tests/util.

Allow for testing other than /bin/sh using TEST_SH (from kre@)

branches: 1.2.2; 1.2.6;
Run scripts at build time via ${HOST_SH}

PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

Supply a missing \ ... this missing has meant that these tests
have not been testing everything they should have been testing.
Never mind, they still all succeed.

branches: 1.2.14; 1.2.16;
Allow for testing other than /bin/sh using TEST_SH (from kre@)

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

Allow for testing other than /bin/sh using TEST_SH (from kre@)

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.

branches: 1.1.2; 1.1.6;
PR/48843: Jarmo Jaakkola: Test cses for break/continue/return broken
inside dot commands:

The test cases are named with the pattern
dotscope_cmd_cmdscope,
where dotscope is the scope in which the dot command is and cmdscope
is the scope where cmd is in the sourced file.