Age | Commit message (Collapse) | Author |
|
Relying on the live snmpd(8) metrics is brittle and this regress test
should probably move to a custom agent in a similar fashion to the
custom manager from the snmpd(8) regress.
Pointed out by anton@
|
|
longer possible to register objects underneath this region. This
effectively made a few snmp(1) regress tests unusable, which essentially
don't belong here. Simply remove these tests.
|
|
examining the outcome.
ok bluhm@
|
|
test failures in -portable when running tests prior to installation.
|
|
|
|
|
|
little sense here since there are multiple possible errnos that could
be returned. On OpenBSD this returns EISDIR and not EBUSY.
OK mbuhl@ millert@
|
|
the directory and so checking against getgid() makes no sense.
OK mbuhl@ millert@
|
|
closed.
OK mbuhl@ millert@
|
|
check if we're using sudo since we don't want to chown unecessarily,
as on some platforms this causes an error which pollutes stderr.
We also don't want to unnecessarily invoke sudo, since it's running
in the context of the proxycommand, on *other* platforms it may not
be able to authenticate, and if we're using SUDO then it should
already be privileged.
|
|
then we won't need to chmod.
|
|
|
|
Replace the use of a perl script to delete the controlling TTY with a
SSH_ASKPASS script to directly load the PIN.
Move PKCS#11 setup code to functions in anticipation of it being used
elsewhere in additional tests.
Reduce stdout spam
|
|
Until OpenSSL 3.1 has replaced OpenSSL 3.0 on most architectures, run
both tests. Installed packages of OpenSSL 3.0 will update automatically
to 3.1, so regress runners should not need to do anything.
|
|
instance with a registered region above cause a recursion in the tree.
|
|
searchrange.end are rejected.
|
|
|
|
protocol error-ed message and immediately followed up by a connection
close.
OK tb@
|
|
on why this occasionally fails.
|
|
|
|
|
|
Once we remove X509_ALGOR_set_md() we can link this test statically and use
X509_ALGOR_set_evp_md() but for now make sure the documented workaround for
this garbage API works.
|
|
|
|
The syntax and semantics is almost identical to mdoc(7) .Xr.
This will be needed for reading the groff manual pages once our port
will be updated to 1.23, and the Linux Manual Pages Project is also
determined to start using it sooner or later. I did not advocate for
this new macro, but since we want to remain able to read all manual
pages found in the wild, there is little choice but to support it.
At least it is easy to do, they basically copied .Xr.
|
|
There are still many test cases left to write, so leave snmpd.sh in place
to test for cases not yet implemented by the new code.
|
|
|
|
inside \w arguments, and skip most other escape sequences when measuring
the output length in this way because most escape sequences contribute
little or nothing to text width: for example, consider font escapes in
terminal output.
This implementation is very rudimentary. In particular, it assumes that
every character has the same width. No attempt is made to detect
double-width or zero-width Unicode characters or to take dependencies on
output devices or fonts into account. These limitations are hard to
avoid because mandoc has to interpolate \w at the parsing stage when the
output device is not yet known. I really do not want the content of the
syntax tree to depend on the output device.
Feature requested by Paul <Eggert at cs dot ucla dot edu>, who also
submitted a patch, but i chose to commit this very different patch
with almost the same functionality.
His input was still very valuable because complete support for \w is
out of the question, and consequently, the main task is identifying
subsets of the feature that are needed for real-world manual pages
and can be supported without uprooting the whole forest.
|
|
ok dtucker@
|
|
|
|
BPFTrace's exit() statement executes the END probe (if any) and prints
the contents of all non-empty maps before terminating the interpreter.
Implement this in btrace(8) with a halting check after each statement.
If a statement causes the program to halt, the condition bubbles up to
the top-level evaluation loop and causes rules_teardown() to run
immediately.
btrace(8) still performs a full rules_setup() if exit() is called
during the BEGIN probe, though the top-level evaluation loop is never
run.
One edge-like case: an exit() from the END probe is treated as an
early return; END is not executed multiple times.
Thread: https://marc.info/?l=openbsd-tech&m=169765169420751&w=2
ok mpi@
|
|
infinite recursion in macro argument expansion
|
|
|
|
recursive delayed expansion of escape sequences in macro arguments
|
|
we do for the PuTTY ones.
|
|
Dropbear server since it won't currently run as a ProxyCommand.
|
|
|
|
Reducing the risk tests conflicting with each other.
ok bluhm@
|
|
|
|
|
|
These are expected failures for BN_mod_exp_simple() and the internal
BN_mod_exp_recp(), which will be fixed shortly.
|
|
server has terminated before examining the outcome.
|
|
|
|
The code allready supports matching of templates with a scope id and
fe80::%pair11/64 and fe80::%gif11/64 are different to session_match_mask().
|
|
|
|
|
|
|
|
tests.
|
|
in regress already does.
|
|
|
|
predictable.
|