Exclude test data files (4 of them) based on existing feature tags:
`codeset-utf8` and `Unicode`.
Add the new keyword `non-ascii` to mark remaining exceptions (9 files).
Follow-up to
838dc53bb7bf52039b23af0e9ccffa51cf9ad7d0 #17247
Closes #17329
12 files changed:
"docs/THANKS",
"docs/THANKS-filter",
"tests/libtest/lib1560.c",
- "^tests/data/test",
);
sub fn_match {
$content =~ s/[$non_ascii_allowed]//g;
if(!fn_match($filename, @non_ascii) &&
- $content =~ /([\x80-\xff]+)/) {
+ ($content =~ /([\x80-\xff]+)/ && $content !~ /^(codeset-utf8|Unicode|non-ascii)/m)) {
push @err, "content: has non-ASCII: '$1'";
}
These are intended to eventually be treated specially on CI builds which are
often run on overloaded machines with unpredictable timing.
+Tests using non-7-bit-ASCII characters, and not using features `Unicode` or
+`codeset-utf8`, need to add the `non-ascii` keyword to tell the code checker
+to allow these characters.
+
## `<reply>`
### `<data [nocheck="yes"] [sendzero="yes"] [hex="yes"] [nonewline="yes"] [crlf="yes"]>`
HTTP
HTTP GET
followlocation
+non-ascii
</keywords>
</info>
#
HTTP
HTTP GET
cookies
+non-ascii
</keywords>
</info>
FTP
HTTPS proxy
flaky
+non-ascii
</keywords>
</info>
FTP
HTTPS proxy
flaky
+non-ascii
</keywords>
</info>
HTTP GET
cookies
cookiejar
+non-ascii
</keywords>
</info>
# Server-side
<info>
<keywords>
HTTP
+non-ascii
</keywords>
</info>
<info>
<keywords>
HTTP
+non-ascii
</keywords>
</info>
<keywords>
HTTP
HTTP GET
+non-ascii
</keywords>
</info>
<keywords>
HTTP
HTTP GET
+non-ascii
</keywords>
</info>
<keywords>
SMTP
MULTIPART
+non-ascii
</keywords>
</info>