summaryrefslogtreecommitdiffstats
path: root/tools/regression/bin
Commit message (Collapse)AuthorAgeFilesLines
* Migrate tools/regression/bin/ tests to the new layout.jmmv2013-12-11411-6857/+0
| | | | | | | | | | | | | | | | | | | | This change is a proof of concept on how to easily integrate existing tests from the tools/regression/ hierarchy into the /usr/tests/ test suite and on how to adapt them to the new layout for src. To achieve these goals, this change: - Moves tests from tools/regression/bin/<tool>/ to bin/<tool>/tests/. - Renames the previous regress.sh files to legacy_test.sh. - Adds Makefiles to build and install the tests and all their supporting data files into /usr/tests/bin/. - Plugs the legacy_test test programs into the test suite using the new TAP backend for Kyua (appearing in 0.8) so that the code of the test programs does not have to change. - Registers the new directories in the BSD.test.dist mtree file. Reviewed by: freebsd-testing Approved by: rpaulo (mentor)
* sh: Make <&0 disable the </dev/null implicit in a background command.jilles2013-11-242-0/+5
| | | | | | Although <&0 does nothing, it is a redirection affecting standard input and should therefore disable the </dev/null redirection implicit in a background command.
* sh: Add more tests for the </dev/null implicit in a background command.jilles2013-11-243-0/+15
|
* sh: Add tests for the </dev/null implicit in a background command.jilles2013-11-223-0/+9
|
* sh: Properly quote alias output from command -v.jilles2013-11-101-0/+7
| | | | | An alias should be printed by command -v as a command line; therefore, make the alias definition suitable for re-input to the shell.
* sh: Add a test case for would-be assignments that are not due to quoting.jilles2013-11-101-0/+19
|
* sh: Allow trapping SIGINT/SIGQUIT after ignore because of '&'.jilles2013-10-302-0/+18
| | | | | | | | | | | | | | If job control is not enabled, background jobs started with ... & ignore SIGINT and SIGQUIT so that they are not affected by such signals that are intended for the foreground job. However, this should not prevent reassigning a different action for these signals (as if the shell invocation inherited these signal actions from its parent). Austin group issue #751 Example: { trap - INT; exec sleep 10; } & wait A Ctrl+C should terminate the sleep command.
* sh: Make return return from the closest function or dot script.jilles2013-09-041-0/+13
| | | | | | | | | | | | | Formerly, return always returned from a function if it was called from a function, even if there was a closer dot script. This was for compatibility with the Bourne shell which only allowed returning from functions. Other modern shells and POSIX return from the function or the dot script, whichever is closest. Git 1.8.4's rebase --continue depends on the POSIX behaviour. Reported by: Christoph Mallon, avg
* sh: Recognize "--" as end of options in type builtin.jilles2013-08-301-0/+3
| | | | | This implementation makes minimal changes: command names starting with "-" (other than "--") can still be queried normally.
* sh: Recognize "--" as end of options in alias builtin.jilles2013-08-251-0/+4
| | | | | Aliases starting with "-" (which are non-POSIX) will need to be preceded by an alias not starting with "-" or the newly added "--".
* sh: Disallow empty simple commands.jilles2013-08-251-0/+3
| | | | | | | | | | As per POSIX, a simple command must have at least one redirection, assignment word or command word. These occured in rare cases such as eval "f()" . The extension of allowing no commands inside { }, if, while, for, etc. remains.
* sh: Reject ++ and -- in arithmetic.jilles2013-08-241-0/+6
| | | | | | | | | | POSIX does not require ++ and -- in arithmetic. It is probably more useful to reject them than to treat ++x and --x as x silently. Note that the behaviour of increment and decrement can be obtained via (x+=1), ((x+=1)-1), (x-=1) and ((x-=1)+1). PR: bin/176444
* sh: Recognize "--" as end of options in bg/fg/jobid builtins.jilles2013-08-161-0/+9
|
* sh: Add test for the non-standard jobid builtin.jilles2013-08-161-0/+7
|
* sh: Recognize "--" as end of options in local builtin.jilles2013-08-141-0/+12
|
* sh: Allow a lone redirection before '|', ';;' or ';&'.jilles2013-08-143-0/+6
| | | | | | | Example: </dev/null | : PR: 181240 MFC after: 1 week
* sh: Do not read from stdin if an error occurs during -i -c cmd.jilles2013-07-121-0/+3
| | | | | | | | | | | | Although using -i with -c does not seem very useful, it seems inappropriate to read commands from the terminal in this case. Side effect: if the -s -c extension is used and the -s option is turned off using 'set +s' during the interactive part, the shell now exits after an error or interrupt. Note that POSIX only specifies -s as option to sh, not to set. See also Austin Group issue #718.
* sh: Add tests for 'local -' (save shell options).jilles2013-06-152-0/+43
|
* sh: Return status 127 for unknown jobs in wait builtin.jilles2013-06-052-0/+8
| | | | | | | | | | This is required by POSIX, at least for pids that are not known child processes. Other problems with job specifications still cause wait to abort with exit status 2. PR: 176916
* sh: Allow multiple operands in wait builtin.jilles2013-06-051-0/+7
| | | | | | | | This is only part of the PR; the behaviour for unknown/invalid pids/jobs remains unchanged (aborts the builtin with status 2). PR: 176916 Submitted by: Vadim Goncharov
* test: Remove -ntXY and -otXY primaries.jilles2013-05-311-64/+1
| | | | | | | | | | | | | | | This reverts commit r247274. As maintainer of sh, I disapprove of this feature addition. It is too specific and can be done without easily using find(1) or stat(1). I will add some hints to the test(1) man page shortly. In general, FreeBSD sh is not the place to invent new shell language features. This is how it has been maintained and adding features randomly does not work with that. The new syntax (e.g. [ FILE1 -ntca FILE2 ]) looks cryptic to me.
* sh: Add test cases for break outside a loop.jilles2013-05-312-0/+19
| | | | | | In most shells (including our sh), break outside a loop does nothing with status 0, or at least does not abort. Therefore, scripts sometimes (buggily) depend on this.
* sh: Remove racy test case for read builtin.jilles2013-05-031-13/+0
| | | | | | | This test case sometimes fails because of an EINTR-related race condition. Fixing this race condition likely requires an extra system call per byte, which would make the read builtin even slower than it already is, or very complicated trickery. Therefore, remove the test case for now.
* sh: Improve error handling in read builtin:jilles2013-05-032-0/+18
| | | | | | | | | | | | * If read -t times out, return status as if interrupted by SIGALRM (formerly 1). * If a trapped signal interrupts read, return status 128+sig (formerly 1). * If [EINTR] occurs but there is no trap, retry the read (for example because of a SIGWINCH in interactive mode). * If a read error occurs, write an error message and return status 2. As before, a variable assignment error returns 2 and discards the remaining data read.
* sh: Don't modify exit status when break/continue/return passes !.jilles2013-04-122-0/+10
| | | | | | | | This matches what would happen if ! P were to be replaced with if P; then false; else true; fi. Example: f() { ! return 0; }; f
* sh: Add a variation on builtins/eval4.0 where the cmdsubst returns 0.jilles2013-04-061-0/+5
|
* sh: Recognize "--" and explicitly reject options in wait builtin.jilles2013-03-152-0/+7
| | | | | | If syntactically invalid job identifiers are to be taken as jobs that exited with status 127, this should not apply to options, so that we can add options later if need be.
* sh: When executing a trap, keep exit status along with evalskip.jilles2013-03-031-0/+10
| | | | | | | This ensures 'return' in a trap returns the correct status to the caller. If evalskip is not set or if it is overridden by a previous evalskip, keep the old behaviour of restoring the exit status from before the trap.
* Enhance test(1) by adding provision to compare any combination of thepeterj2013-02-251-1/+64
| | | | | | | | | access, birth, change and modify times of two files, instead of only being able to compare modify times. The builtin test in sh(1) will automagically acquire the same expansion. Approved by: grog MFC after: 2 weeks
* sh: If a SIGINT or SIGQUIT interrupts "wait", return status 128+sig.jilles2013-02-232-0/+24
|
* sh: Test that the exit status is 1 if read encounters EOF.jilles2013-02-231-0/+5
|
* sh: Pass $? to command substitution containing compound/multiple commands.jilles2013-01-141-0/+5
| | | | | Example: false; echo $(echo $?; :)
* sh: Add testcase that $? is preserved into a simple command substitution.jilles2013-01-131-0/+5
| | | | | The test builtins/trap6.0 already uses this but having it separate eases diagnosis if this would break.
* sh: Add some testcases related to subshells.jilles2013-01-135-0/+25
| | | | | These failed in earlier attempts to execute more subshells without forking. The patches are uncommitted.
* sh: Fix crash when parsing '{ } &'.jilles2013-01-131-0/+7
| | | | MFC after: 1 week
* sh: Don't lose $? when backquoted command ends with semicolon or newline.jilles2013-01-132-0/+10
| | | | | | | | | An empty simple command was added and overwrote the exit status with 0. This affects `...` but not $(...). Example: v=`false;`; echo $?
* sh: Detect and flag write errors on stdout in builtins.jilles2012-12-121-0/+3
| | | | | | | If there is a write error on stdout, a message will be printed (to stderr) and the exit status will be changed to 2 if it would have been 0 or 1. PR: bin/158206
* sh: Apply rlimits to parser/alias10.0 so it fails fast.jilles2012-11-181-0/+4
| | | | Requested by: uqs
* sh: Add tests for modifying an alias (r242766).jilles2012-11-083-0/+21
| | | | | Note: parser/alias10.0 will eat a lot of memory/cpu time when it fails (with the old sh).
* sh: Test that a redefined alias works.jilles2012-11-071-0/+6
|
* sh: Add some tests for aliasing a utility to itself.jilles2012-09-222-0/+8
|
* sh: Add a simple test for the "local" builtin.jilles2012-07-151-0/+13
|
* sh: Expand assignment-like words specially for export/readonly/local.jilles2012-07-155-0/+123
| | | | | | | | | | | | | | | | | | | | | | | | | | Examples: export x=~ now expands the tilde local y=$1 is now safe, even if $1 contains IFS characters or metacharacters. For a word to "look like an assignment", it must start with a name followed by an equals sign, none of which may be quoted. The special treatment applies when the first word (potentially after "command") is "export", "readonly" or "local". There may be quoting characters but no expansions. If "local" is overridden with a function there is no special treatment ("export" and "readonly" cannot be overridden with a function). If things like local arr=(1 2 3) are ever allowed in the future, they cannot call a "local" function. This would either be a run-time error or it would call the builtin. This matches Austin Group bug #351, planned for the next issue of POSIX.1. PR: bin/166771
* sh: Add tests where "export" does not parse differently.jilles2012-07-131-0/+13
| | | | | | | | It is planned to expand variable assignments as assignments (no word splitting, different tilde expansion) when they follow a "declaration utility" (export, readonly or local). However, a quoted character cannot be part of a "name" so things like \v=~ are not assignments, and the existing behaviour applies.
* sh: Do not assume that SIGPIPE will only kill a subshell in builtins/wait3.0jilles2012-06-081-1/+1
| | | | | | | | | | | | | | test. POSIX says that SIGPIPE affects a process and therefore a SIGPIPE caused and received by a subshell environment may or may not affect the parent shell environment. The change assumes that ${SH} is executed in a new process. This must be the case if it contains a slash and everyone appears to do so anyway even though POSIX might permit otherwise. This change makes builtins/wait3.0 work in ksh93.
* sh: Add a test for variables with underscores in arithmetic.jilles2012-03-111-0/+4
| | | | | Things like $((_x+1)) are broken in stable/8 sh but work in stable/9 and head.
* sh: Make 'hash' return 1 if at least one utility is not found.jilles2012-02-111-0/+6
| | | | Reported by: lme
* sh: Fix $? in the first command of a 'for'.jilles2012-01-222-0/+17
| | | | | | In the first command of a 'for', $? should be the exit status of the last pipeline (command substitution in the word list or command before 'for'), not always 0.
* sh: Fix execution of multiple statements in a trap when evalskip is setdumbbell2012-01-162-0/+14
| | | | | | | | | | | Before this fix, only the first statement of the trap was executed if evalskip was set. This is for example the case when: o "-e" is set for this shell o a trap is set on EXIT o a function returns 1 and causes the script to abort Reviewed by: jilles MFC after: 2 weeks
* sh: Test EXIT trap with multiple statements in itdumbbell2012-01-161-0/+3
| | | | | Reviewed by: jilles MFC after: 2 weeks
OpenPOWER on IntegriCloud