summaryrefslogtreecommitdiff
path: root/regress/tools
AgeCommit message (Collapse)AuthorFilesLines
2021-05-24*: recursive bump for perl 5.34wiz1-1/+2
2020-05-02regress/tools: reduce the number of backslashes in the coderillig1-2/+2
2020-05-02regress/tools: adjust COMMENTrillig1-7/+4
2020-05-02regress: move tests for platform tools to tools-platformrillig7-269/+1
2019-05-22mk/tools: in the wrapper log, quote arguments containing = naturallyrillig2-3/+12
2019-03-24mk/tools: correctly quote arguments in the tool wrapper logrillig3-46/+85
Before, the tool arguments were written to the log as plain strings. Now the arguments are properly quoted, which makes it possible to replay the commands by copying them from the .work.log file. This only affects tools that are shell builtins (echo, true, false), get additional arguments (mkdir -p) or define a custom TOOLS_SCRIPT (pkg-config, to set an environment variable; or autotools). Tools that are symlinked to the real tool are not affected. The calls to the compiler are already properly logged since cwrappers takes care of that. This commit therefore makes the log entries for the compilers and the other tools more similar.
2019-03-24mk/tools: fix quoting when logging tool invocationsrillig2-12/+49
When a package or the infrastructure defined a tool with custom TOOLS_ARGS or TOOLS_SCRIPT containing special characters, these could lead to unintuitive interactions at the time when that tool invocation was logged in the tool wrapper log. Some of the logging output ended up on stdout, while some of the normal output ended up in the log, and parts of the quoted arguments were even evaluated as shell commands. The logging of the wrapped tool commands is not perfect yet, but at least it's much more predictable now.
2019-03-23regress/tools: show that TOOLS_SCRIPT is not always logged properlyrillig3-42/+118
2019-03-22regress/tools: demonstrate wrong shell quoting in the tools wrapperrillig2-2/+33
2019-03-22mk/tools: fix unintended filename expansion in the tool wrapper log filerillig1-8/+33
2019-03-22regress/tools: demonstrate wrong quoting in tools wrapper loggingrillig3-8/+48
2018-12-05regress/tools: clarify that only the NetBSD 7 shell exhibits this bugrillig1-4/+4
The test has been changed again to fail since making the test pass would mean this bug could later silently show up inside a large GNU configure script where it would be impossible to find. Therefore, when using pkgsrc on NetBSD 7, it is better to switch to another shell for doing pkgsrc work. The comment has been updated to be more accurate.
2018-11-30regress/tools: disable failing test on NetBSDrillig1-1/+4
See bin/53754.
2016-06-11Fixed pkglint warnings.rillig2-3/+6
2014-06-21Add PLISTs for all regression tests. The infrastructure now setsbsiegert1-0/+0
PKG_FAIL_REASON if there is no PLIST, breaking all but one test. Goes from "1 passed, 12 failed" to "6 passed, 7 failed" on Mac OS. "haha" schmonz@
2009-04-09Remove redundant EXTRACT_ONLY and NO_CHECKSUM declarations.joerg1-2/+1
Retire NO_PACAKGE as there is no technical reason for it.
2008-03-04Resign from maintaining a lot of packages, so everyone is free to updaterillig1-2/+2
them at will.
2007-09-09Added a testcase for tar.rillig2-3/+27
2006-11-09Added a test new case for /bin/sh.rillig2-4/+45
2006-09-20Added a testsuite for sed(1) to make sure it can handle characterrillig2-3/+42
classes.
2006-06-25Added a test for the "sort" tool. Fixed pkglint warnings.rillig2-6/+47
2006-05-31Double the length of the command line argument after each iteration.rillig1-1/+2
2005-11-24Added more tests for tr(1), including one that feeds 65536 bytes throughrillig1-1/+20
tr(1). Let's see if there's an implementation with bounded line lengths.
2005-11-24Added testsuite for tr(1).rillig2-3/+40
2005-11-24Oops. I had put the awk-specific functions into test.subr. Moved back.rillig2-19/+27
2005-11-24Factored out the generally useable shell functions into tests.subr, as theyrillig2-31/+36
will be used by almost all test cases.
2005-11-19Don't require too much from a simple awk. 6144 bytes per line must berillig1-3/+6
enough. At least for Solaris.
2005-11-19Print the name of the test case when starting it. This helps in detectingrillig2-3/+10
which test case fails.
2005-11-19Make sure that awk can handle strings of length 4096 on the command linerillig1-14/+45
and of length 2^20 when copying from stdin to stdout.
2005-11-19Added comments.rillig1-1/+4
2005-11-19Regression test for the capabilities of the TOOLS. Most of them haverillig3-0/+53
many different implementations and are by no way easy to use. This test collects some assumptions about what the tools must be able to handle. It is also meant as a guide on using these tools correctly and reliably.