Copy stable/9 to releng/9.3 as part of the 9.3-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

MFC r259132,r259133:
Per the resolution of POSIX bug 0000779 (note 0002050) add support for using 'i'
as a case insensitive flag.

Add regression test for recently added 'i' flag in r259132.

PR: standards/184641

MFC r244407,r244409:
POSIX requires that non-existent or null arguments be treated as if a
zero argument were supplied.

Add regression tests to catch this case as well.

PR: bin/174521
Approved by: cperciva (mentor, implicit)

MFC: r236338, r236339, r236346, r236347, r236365, & r236977
* Deprecate the FreeBSD make's ":U" (to-upper case) and ":L" (to-lower case)
modifiers for ":tu" and ":tl".
* make it easier to test newly-built make.
* Add "-V '${VAR}'" variable expansion from Portable Berkeley Make.
* regression test for '-V' command line option and the :t[lu] modifiers.

Copy head to stable/9 as part of 9.0-RELEASE release cycle.

Approved by: re (implicit)

printf: Allow multibyte characters for '<char> form, avoid negative codes.

Examples:
LC_ALL=en_US.UTF-8 printf '%d\n' $(printf \'\\303\\244)
LC_ALL=en_US.ISO8859-1 printf '%d\n' $(printf \'\\344)
Both of these should print 228.

Like some other shells, incomplete or invalid multibyte characters yield the
value of the first byte without a warning.

Note that there is no general way to go back from the character code to the
character.

sed: Add test for r217133 (-i race).

PR: bin/153261
MFC after: 2 weeks

printf: Test that the "--" option terminator works.

tr: Fix '[=]=]' equivalence class.

A closing bracket immediately after '[=' should not be treated as special.

Different from the submitted patch, a string ending with '[=' does not cause
access beyond the terminating '\0'.

PR: bin/150384
Submitted by: Richard Lowe
MFC after: 2 weeks

o The typo was intended as it stated in the comment. Revert last.

Spotted by: dfr

o Fix typo: .uudef -> .undef.

PR: misc/147462
Submitted by: Erik Cederstrand

Fix stuttering sequences and reverse ranges

PR: 123635
Submitted by: Ulrich Spörlein, uqs at spoerlein dot net

Replace -b with -C and -B (as proposed by Alexander).
Add -3, -A and -B to the usage.
Update regression test for the new parameters.

Create regression tests for ncal:

- A couple of tests to check if the layout of the generated calenders
is correct.

- A couple of tests to see if impossible combinations for -3, -A,
-m, -y etc properly abort.

- A couple of test to confirm that the order of -A, -B, -3 etc give
the right number of months.

- Use errx(3) instead of err(3) when checking if snprintf(3) succeeded.
snprintf(3) doesn't set errno in the tested cases.
- If the same argument reference (for example %1) was specified more than
once, the command didn't necessarily fit to the final command buffer. Fix
this using a dynamic sbuf buffer. Add a few regression tests for the case.

PR: bin/95079
No objections: freebsd-hackers

Add missing newline in last line of file.

Uncovered via: fromcvs vs. svn
Approved by: ed (co-mentor)

- Implement -q option for pgrep(1).
- Add regression test to test -q option.

Add ability to search up the directory hierarchy for the system directory.
Do by specifying ".../" with '-m' or MAKESYSPATH (new) environment variable.

Reviewed by: <sjg@NetBSD.org>
Obtained from: NetBSD (+ embellishment by me, sent back to NetBSD)

Fix formatting.

There are actually 129 tests here.

Catch up with UNIX98-style PTY's.

'prove -r' isn't as smart as grog thought.

You need to be root to run this test.

Don't process 'lastcomm' if "AUTOMATED" is defined.
The tests for it require manual setup.

It is expected these are chmod +x.

Regression test for r201456.

Provide clean output with 'prove -r'.

Delete the svn:mime-type property from these text files.

Don't read the newline character to line buffer because lines are passed
to wcscoll(3). Newline characters could cause incorrect results when
comparing lines.

Also, if an input line didn't contain a newline character, it was
omitted from the output. According to my interpretation, SUSv3 requires
that the newline is always printed.

Add regression tests for the cases. [1]

PR: bin/140976
Submitted by: D'Arcy Cain (original version) [1]
Approved by: trasz (mentor)

Purge some useless mergeinfo.

Wipe out mergeinfo.

IEEE Std 1003.1, 2004 Edition states:

"The escape sequence '\n' shall match a <newline> embedded in
the pattern space."

It is unclear whether this also applies to a \n embedded in a
character class. Disable the existing handling of \n in a character
class following Mac OS X, GNU sed version 4.1.5 with --posix, and
SunOS 5.10 /usr/bin/sed.

Pointed by: Marius Strobl
Obtained from: Mac OS X

Follow POSIX (IEEE Std 1003.1, 2004 Edition) in the implementation
of the y (translate) command.

"If a backslash character is immediately followed by a backslash
character in string1 or string2, the two backslash characters shall
be counted as a single literal backslash character"

Pointed by: Marius Strobl
Obtained from: Mac OS X

Add correct test results.

Describe how other systems treat this case.

Allow [ to be used as a delimiter.

Pointed by: Marius Strobl
Obtained from: Apple

The transition to Subversion allows us to rename files without
repo-copy hacks.
Remove the test-number prefix from the name of the output files,
so that new test cases can be easily added.

Fix some uninitialise variables.

PR: 136383
Submitted by: Ulrich Spoerlein - uqs at spoerlein dot net
Approved by: re (kib)
MFC after: 3 weeks

Regression test the 'addr1,+N' feature added in r192732

Rename files that collide on case-insensitive file systems by encoding
colliding upper case letters as the lower case letter with a '_' in
front.

MFC after: 3 days
Discussed with: ed
Spotted by: Michael David Crawford <mdc at prgmr.com>

Allow jot(1) regression tests to be checked out on Windows filesystems.

The jot(1) regression tests directory contained two tests named `wx' and
`wX', which doesn't work on case insensitive filesystems. Rename `wX' to
`wX1'.

MFC after: 1 month

Add a test for the "or more" part of the following POSIX specification.

"A function can be preceded by one or more '!' characters, in which
case the function shall be applied if the addresses do not select
the pattern space."

Set magic fbsd:nokeywords property that allows files to bypass
keyword expansion. (file-specific replacement for CVSROOT/exclude)

Attach the tr(1) regression tests to the build.

Approved by: das, dds

Add a new set of regression tests, for the tr(1) utility.

Approved by: das, dds

Make the reported number of tests match their actual number.
This fixes the reporting under prove(1)

cd to the correct directory so that the tests can be run from prove(1)

Add a test case for sed(1) regression - we should not ignore case
when not being asked to do so.

Approved by: re (hrs)

Add case-insensitive matching to sed, using the 'I' flag, similarly to GNU sed.
For example,
sed /foo/Id
sed s/foo/bar/Ig

Reviewed by: dds
Approved by: re (hrs)

Don't forget to clear out the hold space for each subsequent file
when in -i mode so that each file gets a clean context of its own.

Add a regression test for the bug.

Tested with: regression tests

Updated tests for changed features.

Submitted by: edwin@

Use correct comment syntax for $FreeBSD$. This file gets put through
cpp, not a shell script.

Pointy hat to: grog

Add regression tests for calendar.

Submitted by: edwin@
PR: bin/113275
MFC after: 2 weeks

Add sparc64 regression test files.

Submitted by: Carl Johan Gustavsson

Modify file generation instructions to remove the tty field:
the mapping from number to name differs between systems,
and will cause tests to fail.

Regression tests for sparc64 record formats.

Submitted by: Carl Johan Gustavsson

Regression tests for amd64 file and record formats.

Submitted by: Larry Rosenman (who also provided access to a testing host)

Regression tests for the new and legacy process accounting formats.

Change the semantics of -i (in-place editing) so that it treats
each file independently from other files. The new semantics are
desired in the most of practical cases, e.g.: delete lines 5-9
from each file.

Keep the previous semantics of -i under a new option, -I, which
uses a single continuous address space covering all files to edit
in-place -- they are too cool to just drop them.

Add regression tests for -i and -I.

Approved by: dds
Compared with: GNU sed
Discussed on: -hackers
MFC after: 2 weeks

Logically separate the complex `hanoi' and `math' tests from basic tests.

Don't forget to close the range if we branched over its end
and had no chance to match it by the 2nd address precisely.
Otherwise the unclosed range would bogusly extend to the end
of stream.

Add a basic regression test for the bug fixed. (This change
also fixes the more complex case 5.3 from `multitest.t'.)

Compared with: SUN and GNU seds
Tested by: regression tests
MFC after: 1 week

Today SUN and GNU seds fully agree on test 5.3 and behave
in a more reasonable way than BSD sed does: they properly
close the range even if we branched over its end. No doubt,
the range `1,5' should not match lines from 9 through 14.

This trivial change should fix at least 3 similar bugs. All of
them are related to the `c' function's need to know if we are at
the actual end of the address range. (It must print the text not
earlier than the whole pattern space was deleted.) It appears the
only sed function with this requirement.

There is `lastaddr' set by applies(), which is to notify the `c'
function, but it can't always help because it's false when we are
hitting the end of file early. There is also a bug in applies()
due to which `lastaddr' isn't set to true on degenerate ranges such
as `$,$' or `N,$' if N appears the last line number.

Handling early EOF condition in applies() could look more logical,
but it would effectively revert sed to the unreasonable behaviour
rev. 1.26 of main.c fought against, as it would require lastline()
be called for each line within each address range. So it's better
to call lastline() only if needed by the `c' function.

Together with this change to sed go regression tests for the bugs
fixed (c1-c3). A basic test of `c' (c0) is also added as it helped
me to spot my own error.

Discussed with: dds
Tested by: the regression tests
MFC after: 1 week

Rename sed.test to multitest.t to comply with the naming scheme of
the regression suite.

Reinstate error-testing regression tests.

Integrate the tests I wrote in 1992 with our current regression
testing framework and protocol.

Reference results for sed.test (to be renamed into multitest.t).
I have verified these with GNU sed 4.1.5 (and in some cases with Solaris
sed) and they are identical, with the following exceptions:
5.3: The result is unspecified and BSD sed behaves differently.
6.3: GNU sed gets it wrong
7.1: GNU sed gets it wrong
7.8: BSD sed gets it wrong

- Uncomment tests that were commented out
- Update platform-conditional tests to reflect current reality
- Fix conditional for test 7.8: it is the fault of BSD sed

- It looks like BSD and GNU sed can nowadays pass two more tests.
- Test 7.8 fails for GNU sed not BSD.

Use another non-printing test; address 0 now has a special meaning in GNU sed.

Update tests to reflect the state of the art of sed in HEAD and
GNU sed 4.1.5.
Almost all of the tests that were skipped for BSD or GNU sed
now appear to work.

Add sed math regression test.

Add Towers of Hanoi regression test.

Add missing newline to correct failure of the regression test.
According to IEEE Std 1003.1, 2004 "Whenever the pattern space is
written to standard output or a named file, sed shall immediately
follow it with a <newline>."

An attempt at the same correction might have been made with r1.3,
which is however identical with r1.2.

New test cases demonstrating fixed bugs, and the reason why
fmtcheck can't be used.

Fix and extend the -j option to pkill/pgrep WRT the jail
wildcard specifications. Earlier the only wildcard syntax
was "-j 0" for "any jail". There were at least
two shortcomings in it: First, jail ID 0 was abused; it
meant "no jail" in other utils, e.g., ps(1). Second, it
was impossible to match processed not in jail, which could
be useful to rc.d developers. Therefore a new syntax is
introduced: "-j any" means any jail while "-j none" means
out of jail. The old syntax is preserved for compatibility,
but now it's deprecated because it's limited and confusing.

Update the respective regression tests. While I'm here,
make the tests more complex but sensitive: Start several
processes, some in jail and some out of jail, so we can
detect that only the right processes are killed by pkill
or matched by pgrep.

Reviewed by: gad, pjd
MFC after: 1 week

Add the examples from the manual page.

Updated results for bin/68981

PR: bin/68981

Regress.out is now regress.x.out.

Test the handling of supplied and default parameters.

Add tests for -t option with short tty name - pkill(1) should accept both
(eg. "ttyv0" and "v0").

Add first tests for semicolon handling. The first test fails. This is
probably a bug in the parser.

Add more tests for escaped newline handling and fix a test that currently
should fail because of a bug in the parser (test 2).

Add regression tests for '-L' option.

'-F' option behaviour was reverted, so revert previous commit.

'-F' option now needs locked pidfile. Modify regression tests respectively.

Correct one regression test (which was expected an incorrect answer), and
add a few more tests. This matches bug fixes recently committed to 'env'.

Upgrade these regression tests to track recent changes to `env'.

Approved by: re (blanket `env')

Add a suite of regression tests for all the recent changes to `env',
using my own script to handle it. I wrote my own partially because
of all the quoting-issues involved with testing what I wanted to test,
and partially because this lets me commit one script and one data file,
instead of one-file-per-regression-test.

This suite was good enough for my initial testing (and it did help me
find a few bugs that would have otherwise been missed). I'm not sure
how well it will work in general use, but I figured I might as well
commit it. It won't *hurt* to have it available. At the worst, people
can just ignore it.

Approved by: re (blanket `env')

Add a test for escaped newline handling.

Add support for TODO tests. These are tests that are supposed to fail,
because of a make bug that should be fixed.

Change the test infrastructure so that tests are easier to maintain and
so that make(1) will run in an almost clean environment and enhance the
description of the test infrastructure.

Add the ability to have multiple tests carried out per test script.

Give some tests more meaningful names.

Fix the usage message from the test scripts.

Make it possible to pass several commands to the test scripts like:
'sh test.t setup run compare clean'.

Add a test to check whether in compat mode make detectes builtins
on the command line and really executes the shell instead of directly
executing the command.

Add a test to ensure that in compat mode when a line contains no
shell meta characters it is not passed to the shell, but the command
is executed directly (given that the line is not a shell builtin) and
that the line with a meta character is passed to the shell.

Add a test that test whether we can replace the shell to use by
make with another shell and set all its parameters (meta and builtins
not tested here).

Some test cases for .SHELL target: builtin shell selection and
changing the path of a builtin shell.

o -n option added.
o -x option added.

Add an initial regression test suite for make(1).

Submitted by: Max Okumoto <okumotu@ucsd.edu> (partly, initial version)

Also test \0 in the format string.

Add a few regression tests for printf(1).

Add regression tests for pkill/pgrep.

MFC after: 3 days

Repo-copy tools/regression/usr.bin/make to tools/build/make_check
and adjust the path in the Makefile for the upgrade_checks target.
These checks are really feature upgrade checks that should be fast
and just find out whether we need to build a new make before
proceeding with other targets like buildworld. This makes the
place free for a real regression test suite in the old place.

Fix builds with a read-only directory and a make upgrade. This is done
by forcing the creation of an object directory for the make regression
tests. Let make handle the tracking of the dependency and installation
of test_shell script.

Submitted by: ru

Make this work under debugging, e.g., "make -dl".

Make the tests runnable on a read-only src. To do this you must make sure
that you create one of the object directories make knows (see make(1)).
This uses the -C flag, so add a test that checks that make actually accepts
-C. Also fix the test that selects csh via the .SHELL target to work for
tcsh users too.

This commit renames shell_test to shell_test.sh. There is no history
to preserve so go without a repo-copy.

Reviewed by: ru

Chmod the shell testscript to be executable if it isn't already. According
to the CVS-Meisters x-mode just happens to work, but is not guaranteed to
do so. Try to be on the safe side.

Add some regression tests for the .SHELL target. I'm not sure that the
output of shell_2j is actually correct - it just tests what make currently
does. Make should switch on echoing for the second line, shouldn't it?

Switch over to a different, more flexible test output protocol that's
understood by Perl's Test::Harness module and prove(1) commands.

Update README to describe the new protocol. The work's broken down into
two main sets of changes.

First, update the existing test programs (shell scripts and C programs)
to produce output in the ok/not ok format, and to, where possible, also
produce a header describing the number of tests that are expected to be
run.

Second, provide the .t files that actually run the tests. In some cases
these are copies of, or very similar too, scripts that already existed.
I've kept the old scripts around so that it's possible to verify that
behaviour under this new system (in terms of whether or not a test fails)
is identical to the behaviour under the old system.

Add a TODO file.

Add a regression test for the alternate shell specification.

Now that make more correctly handles variable assignments
in .MAKEFLAGS targets enable the regression test for this.

Per letter dated July 22, 1999 remove 3rd clause of Berkeley derived
software (original contributor).

Reviewed by: imp

Back out something I'm working on that crept in with the last commit.

Spotted by: ru

Remove extra spaces. Remove double quotes around error messages -
they are not needed and will actually be printed.

Submitted by: ru

Add another test that checks for a working '+' command flag.

Add a regression test for the passing of command line
variable assignments via the MAKEFLAGS environment variable.

A new version that does exponents and lots of other neat things. Update
from the original author of math.sed.

Submitted by: K S Braunsdorf <sed@ksb.npcguild.org>

Add a test for what was broken in rev. 1.28 and fixed in rev. 1.29
of make/str.c.

Add a test for what was fixed in revs. 1.28 and 1.29 of make/str.c.

Fix a bug that prevented exists() from finding "foo/", "foo/."
and "foo/.." when ".PATH: foo" was also given.

PR: bin/34062

Test 8.16 in sed.test tests the ability of a sed to handle an empty
regular expression as the first argument to a substitute command. If
used to test a sed which (erroneously) evaluates this at translation
time rather than at execution time, the bugged sed is put into an
infinite loop. This mode of failure seems excessive. Such a failing
sed is the Free Software Foundation's sed 3.02.

The specific test was also not being executed for the BSD sed.

Both problems are now fixed.

PR: misc/25585
Submitted by: Walter Briscoe <w.briscoe@ponl.com>
Approved by: schweikh (mentor)
MFC after: 2 weeks

Fixed broken arithmetic expression parser.

Reminded by: bde
In memory of: alane

Add tests for the behaviour of substitution when the regex can match
a zero-length string. This shows bugs in the s///g and s///2+ cases.

The regression-tests for 'make' *expect* to trigger make's warning:
warning: duplicate script for target "double" ignored
The regression-tests do try to hide that message, but the message does
still appear when using -j (eg: 'make -j5 buildworld'). This changes the
regression-test so the expected warning message will not be seen even
when -j is specified.

Reviewed by: jmallett ru

Add a test for what was fixed in revisions 1.39 and 1.50 of
make/parse.c (allow embedded `:' and `!' in target names).

Approved by: re

Moved make(1) regression tests from src/Makefile to where they
belong (src/tools/regression/usr.bin/make), and use the latter
to test if make(1) is adequate for building the world.

Approved by: re

Hide the test in <target> under '.if make(<target>)' so as to not get any
errors/warnings related to crud in said test block.

As of revision 1.38 of make/parse.c, our make(1) will warn too. Note that
this isn't just for the sake of testing behaviour, and that things really
do break if this regression occurs.

Update another mention of <CR><CR> I missed the first time around (rev 1.2)

Note that two carriage returns aren't required after entering the
initial setup anymore (since process.c rev. 1.25). Add $FreeBSD$.

MFC after: 2 weeks

The wrong y/// output got spammed into this file; from green@ indirectly.

Correct the psl regression test for sed(1)'s now-fixed newline
behavior. Add the bcb regression test which checks for failures due
to a backslash ('\') coinciding with the very last character of the
command buffer. The regression test is cf. this PR (which I did not
know about) and has a different fix for the bug.

PR: bin/22351
Submitted by: Stefan Duerholt <stefan.duerholt@t-online.de>

Erk, I forgot that regress.in has an ending newline, so change the test for
transliterate to use echo -n to supress newline and a simple string.

Reduce internal code duplication, add REGRESSION_PASSFAIL([testname]) to
handle printing of the PASS/FAIL messages. Suffix PASS/FAIL/FATAL with the
string (in $directory) where $directory is ${.CURDIR} from make(1), to
make it easier to use grep(1) and a bit of sed/awk to do statistics of
failure for some utilities over time, etc.

Add a regression test for transliterate which happens to match characters
at an EOL/EOF, and therefore should catch the broken behaviour fixed by
Tim J. Robbins in sed(1) recently.

Suggested by: obrien

I explicitly meant to not move any of this over to the new m4(1) framework,
even slightly. Grrr CVS.

Move all remaining tests except for:
make(1): Does not work like the other tests. Its Makefile is
self-testing.
m4(1): It uses complex voodo to test GNU m4(1) features.

To the new framework. I had worried about passing the binary data that
uudecode(1)'s test passes to diff(1) might give a user something nasty,
but this is unlikely to happen as even with an unmodified old nasty
diff(1) which doesn't recognise many binary files, these binary files
are recognised. Using $DIFF instead of `diff' in the library and making
it possible to override this with `cmp -s' might be nice some day, but
as of this second, there's no immediate need.

Add two new mostly freeform types of regression tests, and a macro for dying
ungracefully.

Comments to describe what these macros do, so that someone other than me
might be able to figure out how to write some of these tests (hint hint).

Convert straightforward regression tests to use regress.m4.

Goodbye, duplicated code, you will certainly not be missed.

Add a simple (to be expanded) library of functions for the regression tests,
to handle the ones which output to stdout and have output in regress.$test.out,
etc. More freeform macros should and will be written, but these are the most
prominent and most straightforward sort of tests we have around, so it makes
sense to try to accomodate them.

Grrr, make the test for embedded variables in the left-hand-side actually do
the right thing in every case. Yuck.

Add a test for what was fixed in revision 1.27 and 1.28 of make(1)'s var.c,
expansion of embedded variables in the left-hand-side of an assignment
expression, using the simplest case - hiding recursion using nil-expanded
variables.

Add the m4(1) regression test.

Add a regression test for m4(1).

This checks the behaviour of changecom() in both GNU and BSD modes of our m4.

Regenerate with new output grouping in uuencode -m.

Add a regression test for bin/5297, regarding sysv substitution with a nil
left-hand-side.

Add a test for the -R option.

Regenerate -I output since an argument bogon in the -I code was fixed, among
other things.

Redirect stdin from the input file, rather than passing the input file to
uuencode(1), and set a umask, so that the mode in the header is predictable.

If it varies, then the test is right to fail.

Remove the note about this test falsely failing, with that in mind.

Prefix tests with PASS and FAIL, to make grepping easier, and note this in
the README.

This affects only the base-system regression tests, of course.

For the P function, the newline must be considered a part of the pattern
space, so when printing it, don't let the pattern space and the output run
into eachother by omitting the \n when printing.

Add sed(1) tests for proper behaviour of the G option as fixed in PR 26152,
and for proper behaviour of some sed functions given a nil pattern space,
as fixed in PR 34813.

The test for G was based on the test in the PR. The nil pattern space test
is slightly different as we need to get *some* output, as the core dump will
also produce no output (old behaviour) and turn up falsely that the utility
is working fine.

Check to see if make(1)'s handling of doubly-defined targets is busted or
not. A lot relies on this.

Only exit at the end of a test, exit with the last value of $? that was not 0.

This way the entire regression test is looked at as a pass/fail, not just one
sub-test.

Add a test of variable evaluation and substitution for make(1), as a start
of tests for it.

Add a test for jot(1).

A simple test for join(1) based on tjr's test case for -o 0.

Partially based on: PR standards/36072

Add an exceedingly simple regression test for the file2c program. One would
hope that it would never regress, but this is a straightforward test, so add
it.

Add regression tests for parts of xargs(1).

Add a comment regarding the file header, and the mode that the file is created
with.

This should be fixed shortly by adding the (desirable) option to set the file
creation mode on the command line.

Add uuencode(1) and uudecode(1) regression test input and output.

Start adding framework for userland regression tests, and tests for
uuencode and uudecode.

Make it at least semi-worked

BSD 4.4 Lite Usr.bin Sources