#
1.9 |
|
24-May-2022 |
andvar |
fix various typos in comment, documentation and log messages.
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1
|
#
1.8 |
|
19-May-2021 |
kre |
With the (very) recent changes to printf(1), a numeric conversion from data of the form '+1 (two (or more) characters after the quote) will now generate an error message, and cause printf(1) to exit(1) when it is done.
Adapt the test cases which use that data form to handle that.
|
#
1.7 |
|
19-May-2021 |
kre |
Fix a truly embarrassing quoting screwup. There is an explanation as to why this didn't cause any failures, but I won't go into it here. This was detected by the about to be committed printf changes.
While here also correct a couple of minor comment layout issues.
|
Revision tags: cjep_staticlib_x-base
|
#
1.6 |
|
24-Apr-2020 |
kre |
branches: 1.6.2;
ATF runs shell script tests with "sh -e" (WHY???)
Compensate for that by adding an explicit test to a command so -e will not kill the shell when the command (expectedly) fails.
Previously this was saved by /bin/sh disabling -e in command subs.
|
Revision tags: phil-wifi-20200421 phil-wifi-20200411 is-mlppp-base phil-wifi-20200406 phil-wifi-20191119
|
#
1.5 |
|
12-Nov-2019 |
kre |
Add a missing ("quoting") '>' in an atf_fail error message string. Since the tests don't (usually) fail no-one ever noticed the missing char.
That is, the "received this" and "expected this" strings were supposed to appear in the output err message as "<<string>>" but one of those closing '>' chars was missing.
No-one should ever notice this change in normal operation, as the tests are not intended to fail.
|
Revision tags: netbsd-9-2-RELEASE netbsd-9-1-RELEASE netbsd-9-0-RELEASE netbsd-9-0-RC2 netbsd-9-0-RC1 netbsd-9-base
|
#
1.4 |
|
21-Jul-2019 |
kre |
Stop assuming that printf handles options in any way at all (it doesn't - that is, shouldn't) which includes processing -- as an "end of options". The first arg is (always) the format string.
Remove/fix tests that assumed the contrary.
Problem (with printf) pointed out on tech-userlevel by Thierry Laronde.
|
Revision tags: phil-wifi-20190609 pgoyette-compat-20190127 pgoyette-compat-20190118 pgoyette-compat-1226 pgoyette-compat-1126 pgoyette-compat-1020 pgoyette-compat-0930
|
#
1.3 |
|
14-Sep-2018 |
kre |
branches: 1.3.2;
Move the tests of character value args to floating conversions out of the %e test and into the NetBSD specific tests, while POSIX once (apparently) required (or seemed to require) support for that, it no longer does (and character value args to float conversions do not make much sense - char valuse are always integers).
When char conversions are supported, test that \' (or \" ) (that is, no character following the quote) works as an arg (should result in zero, as there's a \0 in the arg after the quote char).
Add some big/small number %g conversion tests.
|
#
1.2 |
|
10-Sep-2018 |
kre |
Add a test where printf is run twice in the same shell, and the first invocation uses \c in a %b arg - make sure that 2nd invocation is not affected by that (it was until recently, for a very long time).
|
Revision tags: pgoyette-compat-0906
|
#
1.1 |
|
05-Sep-2018 |
kre |
branches: 1.1.2; Add ATF tests for printf(1)
Two new test programs, one for the version of printf in /bin/sh and one for the command /usr/bin/printf (t_builtin and t_command)
Each test program has 28 test cases (the same in each) of which currently 27 pass, and 1 is skipped.
See the test scripts themselves for more information.
|
#
1.8 |
|
19-May-2021 |
kre |
With the (very) recent changes to printf(1), a numeric conversion from data of the form '+1 (two (or more) characters after the quote) will now generate an error message, and cause printf(1) to exit(1) when it is done.
Adapt the test cases which use that data form to handle that.
|
#
1.7 |
|
19-May-2021 |
kre |
Fix a truly embarrassing quoting screwup. There is an explanation as to why this didn't cause any failures, but I won't go into it here. This was detected by the about to be committed printf changes.
While here also correct a couple of minor comment layout issues.
|
Revision tags: cjep_staticlib_x-base
|
#
1.6 |
|
24-Apr-2020 |
kre |
ATF runs shell script tests with "sh -e" (WHY???)
Compensate for that by adding an explicit test to a command so -e will not kill the shell when the command (expectedly) fails.
Previously this was saved by /bin/sh disabling -e in command subs.
|
Revision tags: phil-wifi-20200421 phil-wifi-20200411 is-mlppp-base phil-wifi-20200406 phil-wifi-20191119
|
#
1.5 |
|
12-Nov-2019 |
kre |
Add a missing ("quoting") '>' in an atf_fail error message string. Since the tests don't (usually) fail no-one ever noticed the missing char.
That is, the "received this" and "expected this" strings were supposed to appear in the output err message as "<<string>>" but one of those closing '>' chars was missing.
No-one should ever notice this change in normal operation, as the tests are not intended to fail.
|
Revision tags: netbsd-9-2-RELEASE netbsd-9-1-RELEASE netbsd-9-0-RELEASE netbsd-9-0-RC2 netbsd-9-0-RC1 netbsd-9-base
|
#
1.4 |
|
21-Jul-2019 |
kre |
Stop assuming that printf handles options in any way at all (it doesn't - that is, shouldn't) which includes processing -- as an "end of options". The first arg is (always) the format string.
Remove/fix tests that assumed the contrary.
Problem (with printf) pointed out on tech-userlevel by Thierry Laronde.
|
Revision tags: phil-wifi-20190609 pgoyette-compat-20190127 pgoyette-compat-20190118 pgoyette-compat-1226 pgoyette-compat-1126 pgoyette-compat-1020 pgoyette-compat-0930
|
#
1.3 |
|
14-Sep-2018 |
kre |
branches: 1.3.2;
Move the tests of character value args to floating conversions out of the %e test and into the NetBSD specific tests, while POSIX once (apparently) required (or seemed to require) support for that, it no longer does (and character value args to float conversions do not make much sense - char valuse are always integers).
When char conversions are supported, test that \' (or \" ) (that is, no character following the quote) works as an arg (should result in zero, as there's a \0 in the arg after the quote char).
Add some big/small number %g conversion tests.
|
#
1.2 |
|
10-Sep-2018 |
kre |
Add a test where printf is run twice in the same shell, and the first invocation uses \c in a %b arg - make sure that 2nd invocation is not affected by that (it was until recently, for a very long time).
|
Revision tags: pgoyette-compat-0906
|
#
1.1 |
|
05-Sep-2018 |
kre |
branches: 1.1.2; Add ATF tests for printf(1)
Two new test programs, one for the version of printf in /bin/sh and one for the command /usr/bin/printf (t_builtin and t_command)
Each test program has 28 test cases (the same in each) of which currently 27 pass, and 1 is skipped.
See the test scripts themselves for more information.
|
#
1.6 |
|
24-Apr-2020 |
kre |
ATF runs shell script tests with "sh -e" (WHY???)
Compensate for that by adding an explicit test to a command so -e will not kill the shell when the command (expectedly) fails.
Previously this was saved by /bin/sh disabling -e in command subs.
|
Revision tags: phil-wifi-20200421 phil-wifi-20200411 is-mlppp-base phil-wifi-20200406 phil-wifi-20191119
|
#
1.5 |
|
12-Nov-2019 |
kre |
Add a missing ("quoting") '>' in an atf_fail error message string. Since the tests don't (usually) fail no-one ever noticed the missing char.
That is, the "received this" and "expected this" strings were supposed to appear in the output err message as "<<string>>" but one of those closing '>' chars was missing.
No-one should ever notice this change in normal operation, as the tests are not intended to fail.
|
Revision tags: netbsd-9-0-RELEASE netbsd-9-0-RC2 netbsd-9-0-RC1 netbsd-9-base
|
#
1.4 |
|
21-Jul-2019 |
kre |
Stop assuming that printf handles options in any way at all (it doesn't - that is, shouldn't) which includes processing -- as an "end of options". The first arg is (always) the format string.
Remove/fix tests that assumed the contrary.
Problem (with printf) pointed out on tech-userlevel by Thierry Laronde.
|
Revision tags: phil-wifi-20190609 pgoyette-compat-20190127 pgoyette-compat-20190118 pgoyette-compat-1226 pgoyette-compat-1126 pgoyette-compat-1020 pgoyette-compat-0930
|
#
1.3 |
|
14-Sep-2018 |
kre |
branches: 1.3.2;
Move the tests of character value args to floating conversions out of the %e test and into the NetBSD specific tests, while POSIX once (apparently) required (or seemed to require) support for that, it no longer does (and character value args to float conversions do not make much sense - char valuse are always integers).
When char conversions are supported, test that \' (or \" ) (that is, no character following the quote) works as an arg (should result in zero, as there's a \0 in the arg after the quote char).
Add some big/small number %g conversion tests.
|
#
1.2 |
|
10-Sep-2018 |
kre |
Add a test where printf is run twice in the same shell, and the first invocation uses \c in a %b arg - make sure that 2nd invocation is not affected by that (it was until recently, for a very long time).
|
Revision tags: pgoyette-compat-0906
|
#
1.1 |
|
05-Sep-2018 |
kre |
branches: 1.1.2; Add ATF tests for printf(1)
Two new test programs, one for the version of printf in /bin/sh and one for the command /usr/bin/printf (t_builtin and t_command)
Each test program has 28 test cases (the same in each) of which currently 27 pass, and 1 is skipped.
See the test scripts themselves for more information.
|
#
1.5 |
|
12-Nov-2019 |
kre |
Add a missing ("quoting") '>' in an atf_fail error message string. Since the tests don't (usually) fail no-one ever noticed the missing char.
That is, the "received this" and "expected this" strings were supposed to appear in the output err message as "<<string>>" but one of those closing '>' chars was missing.
No-one should ever notice this change in normal operation, as the tests are not intended to fail.
|
Revision tags: netbsd-9-base
|
#
1.4 |
|
21-Jul-2019 |
kre |
Stop assuming that printf handles options in any way at all (it doesn't - that is, shouldn't) which includes processing -- as an "end of options". The first arg is (always) the format string.
Remove/fix tests that assumed the contrary.
Problem (with printf) pointed out on tech-userlevel by Thierry Laronde.
|
Revision tags: phil-wifi-20190609 pgoyette-compat-20190127 pgoyette-compat-20190118 pgoyette-compat-1226 pgoyette-compat-1126 pgoyette-compat-1020 pgoyette-compat-0930
|
#
1.3 |
|
14-Sep-2018 |
kre |
branches: 1.3.2;
Move the tests of character value args to floating conversions out of the %e test and into the NetBSD specific tests, while POSIX once (apparently) required (or seemed to require) support for that, it no longer does (and character value args to float conversions do not make much sense - char valuse are always integers).
When char conversions are supported, test that \' (or \" ) (that is, no character following the quote) works as an arg (should result in zero, as there's a \0 in the arg after the quote char).
Add some big/small number %g conversion tests.
|
#
1.2 |
|
10-Sep-2018 |
kre |
Add a test where printf is run twice in the same shell, and the first invocation uses \c in a %b arg - make sure that 2nd invocation is not affected by that (it was until recently, for a very long time).
|
Revision tags: pgoyette-compat-0906
|
#
1.1 |
|
05-Sep-2018 |
kre |
branches: 1.1.2; Add ATF tests for printf(1)
Two new test programs, one for the version of printf in /bin/sh and one for the command /usr/bin/printf (t_builtin and t_command)
Each test program has 28 test cases (the same in each) of which currently 27 pass, and 1 is skipped.
See the test scripts themselves for more information.
|
#
1.4 |
|
21-Jul-2019 |
kre |
Stop assuming that printf handles options in any way at all (it doesn't - that is, shouldn't) which includes processing -- as an "end of options". The first arg is (always) the format string.
Remove/fix tests that assumed the contrary.
Problem (with printf) pointed out on tech-userlevel by Thierry Laronde.
|
Revision tags: phil-wifi-20190609 pgoyette-compat-20190127 pgoyette-compat-20190118 pgoyette-compat-1226 pgoyette-compat-1126 pgoyette-compat-1020 pgoyette-compat-0930
|
#
1.3 |
|
14-Sep-2018 |
kre |
branches: 1.3.2;
Move the tests of character value args to floating conversions out of the %e test and into the NetBSD specific tests, while POSIX once (apparently) required (or seemed to require) support for that, it no longer does (and character value args to float conversions do not make much sense - char valuse are always integers).
When char conversions are supported, test that \' (or \" ) (that is, no character following the quote) works as an arg (should result in zero, as there's a \0 in the arg after the quote char).
Add some big/small number %g conversion tests.
|
#
1.2 |
|
10-Sep-2018 |
kre |
Add a test where printf is run twice in the same shell, and the first invocation uses \c in a %b arg - make sure that 2nd invocation is not affected by that (it was until recently, for a very long time).
|
Revision tags: pgoyette-compat-0906
|
#
1.1 |
|
05-Sep-2018 |
kre |
branches: 1.1.2; Add ATF tests for printf(1)
Two new test programs, one for the version of printf in /bin/sh and one for the command /usr/bin/printf (t_builtin and t_command)
Each test program has 28 test cases (the same in each) of which currently 27 pass, and 1 is skipped.
See the test scripts themselves for more information.
|