head	1.20;
access;
symbols
	pkgsrc-2026Q1:1.18.0.2
	pkgsrc-2026Q1-base:1.18
	pkgsrc-2025Q4:1.5.0.2
	pkgsrc-2025Q4-base:1.5;
locks; strict;
comment	@# @;


1.20
date	2026.04.15.11.15.51;	author pin;	state Exp;
branches;
next	1.19;
commitid	0e5Dt4RsHspNV2CG;

1.19
date	2026.03.26.04.33.20;	author pin;	state Exp;
branches;
next	1.18;
commitid	KciAKNgsQ6OylrzG;

1.18
date	2026.03.10.16.27.07;	author pin;	state Exp;
branches;
next	1.17;
commitid	SOkyh5i7kWAkOrxG;

1.17
date	2026.03.03.12.17.31;	author wiz;	state Exp;
branches;
next	1.16;
commitid	PFBM45v6c09DEwwG;

1.16
date	2026.02.23.08.33.58;	author pin;	state Exp;
branches;
next	1.15;
commitid	268sRdzgYyLTFtvG;

1.15
date	2026.02.20.12.29.09;	author pin;	state Exp;
branches;
next	1.14;
commitid	qgaa4wbErPhz47vG;

1.14
date	2026.02.17.13.06.09;	author pin;	state Exp;
branches;
next	1.13;
commitid	axJS8V4brwoenJuG;

1.13
date	2026.01.26.10.26.24;	author pin;	state Exp;
branches;
next	1.12;
commitid	zeBi1oANRnahcTrG;

1.12
date	2026.01.15.09.30.26;	author pin;	state Exp;
branches;
next	1.11;
commitid	GWFQMCkiVnKZetqG;

1.11
date	2026.01.14.14.43.03;	author pin;	state Exp;
branches;
next	1.10;
commitid	hFybKMBAJuGe0nqG;

1.10
date	2026.01.12.12.02.06;	author pin;	state Exp;
branches;
next	1.9;
commitid	fXGa7VnZKZm0b6qG;

1.9
date	2026.01.05.05.49.08;	author pin;	state Exp;
branches;
next	1.8;
commitid	rlFrfAkUTU90lapG;

1.8
date	2026.01.02.17.00.58;	author pin;	state Exp;
branches;
next	1.7;
commitid	VDW4ZsV1WO8s9QoG;

1.7
date	2025.12.30.12.29.12;	author pin;	state Exp;
branches;
next	1.6;
commitid	eaykFHKxOQjdKqoG;

1.6
date	2025.12.30.12.06.11;	author pin;	state Exp;
branches;
next	1.5;
commitid	tsTabdwPA66fCqoG;

1.5
date	2025.12.19.13.17.09;	author pin;	state Exp;
branches;
next	1.4;
commitid	oLwLEGrAyw2Am1nG;

1.4
date	2025.11.20.12.59.20;	author wiz;	state Exp;
branches;
next	1.3;
commitid	Jlctocppk9NecijG;

1.3
date	2025.11.20.12.35.55;	author pin;	state Exp;
branches;
next	1.2;
commitid	XiRipwBywLq94ijG;

1.2
date	2025.11.20.12.24.16;	author pin;	state Exp;
branches;
next	1.1;
commitid	ypkL2HT3MvH80ijG;

1.1
date	2025.11.20.12.16.47;	author pin;	state Exp;
branches;
next	;
commitid	3p6FfwzlJ4AxXhjG;


desc
@@


1.20
log
@devel/cargo-nextest: update to 0.9.133

Added
 - Nextest now supports a group() filterset predicate for CLI filter expressions, allowing tests to be listed or run by their assigned test group. (#3273)
   For example, to run all tests in a specific group:

    cargo nextest run -E 'group(my-group)'

   To list all tests that aren't in the default global group:

    cargo nextest list -E 'not group(@@global)'

 - As part of cargo test binary emulation, --nocapture can now be passed in after --.

Fixed
 - When --status-level fail is set, slow test notifications were previously displayed in a corrupt format (the duration and test name were shown, but the status was omitted). Slow notifications are now correctly hidden. (#3236)
 - On Windows, pressing t for test status info no longer shows the output twice; nextest now only reacts to key-press events, ignoring key-release events. (#3225)

Security

 - Update rand to 0.10.1 for RUSTSEC-2026-0097 / GHSA-cq8v-f236-94qc. Note that based on the advisory description, this unsoundness does not appear to affect nextest, since none of the covered rand versions have the log feature turned on.
 - Update rustls-webpki to 0.103.10.
@
text
@# $NetBSD: Makefile,v 1.19 2026/03/26 04:33:20 pin Exp $

DISTNAME=	cargo-nextest-0.9.133
CATEGORIES=	devel
MASTER_SITES=	${MASTER_SITE_GITHUB:=nextest-rs/}
GITHUB_PROJECT=	nextest
GITHUB_TAG=	${DISTNAME}

MAINTAINER=	pin@@NetBSD.org
HOMEPAGE=	https://nexte.st/
COMMENT=	Next-generation test runner for Rust
LICENSE=	mit OR apache-2.0

.include "cargo-depends.mk"

RUST_REQ=	1.91.0
USE_TOOLS+=	pkg-config

INSTALLATION_DIRS=	bin

MAKE_ENV+=	OPENSSL_DIR=${BUILDLINK_PREFIX.openssl:Q}
RUSTFLAGS+=	-C link-arg=${COMPILER_RPATH_FLAG}${BUILDLINK_PREFIX.openssl}/lib

# Alpine and Arch Linux use '--no-default-features --features default-no-update' to build their packages.
# See, https://gitlab.alpinelinux.org/alpine/aports/-/raw/master/main/cargo-nextest/APKBUILD
# or, https://gitlab.archlinux.org/archlinux/packaging/packages/cargo-nextest/-/raw/main/PKGBUILD?ref_type=heads
#
# But, upstream states:
# We specify default-no-update here because if users just run:
# cargo build --no-default-features --features default-no-update then cargo will unify features for
# cargo-nextest, and it will be built with self-update enabled.
# We could ask distributors to always include `--package cargo-nextest` instead, but they're likely
# to forget.
# None of our current tests depend on self-update, so just don't include it by default.
#
# Reference, https://raw.githubusercontent.com/nextest-rs/nextest/refs/heads/main/Cargo.toml
#
# So, lets stick to what upstream recommends.
# CARGO_NO_DEFAULT_FEATURES=	YES
# CARGO_FEATURES+=		default-no-update

do-install:
	${INSTALL_PROGRAM} ${WRKSRC}/target/release/cargo-nextest \
		${DESTDIR}${PREFIX}/bin

# See, https://github.com/briansmith/ring/issues/1999
.include "../../mk/compiler/i386-sse2.mk"

.include "../../lang/rust/cargo.mk"
.include "../../security/openssl/buildlink3.mk"
.include "../../mk/bsd.pkg.mk"
@


1.19
log
@devel/cargo-nextest: update to 0.9.132

0.9.32

 - Update aws-lc-sys to 0.39.0 to address GHSA-394x-vwmw-crm3.

0.9.31

Added

 - Setup scripts and wrapper scripts can now specify per-command environment variables via the env field in the command configuration. (#3001)

   For example:

   [scripts.setup.script1]
   command = {
    command-line = "cargo run -p setup-test-db",
    env = {
        DB_PATH = "sqlite:/path/to/source.db",
    },
   }

   Keys cannot begin with NEXTEST, as that prefix is reserved for internal use.
   Values defined in env override values set by the environment and by Cargo's
   config.toml (including those with force = true).
   Thanks metatoaster for your first contribution!

 - A new flaky-result configuration field and --flaky-result CLI flag (environment variable NEXTEST_FLAKY_RESULT) controls whether flaky tests are treated as passing or failing.
   When set to "fail", tests that pass on retry are marked as failures. The default remains "pass". flaky-result can be set at the profile level or per-test via overrides. (#3148)

   For more information, see Failing flaky tests.

   [profile.ci]
   retries = 2
   flaky-result = "fail"

 - A new cargo nextest store export-chrome-trace command that exports test run data in the Chrome Trace Event format.
   Traces can be loaded into Perfetto or Chrome's chrome://tracing for a timeline view of test parallelism and execution. (#3163)
   Traces support grouping by binary (default) or by slot (--group-by slot), and can be exported from both on-disk runs and portable recordings. For more, see Perfetto traces.

 - Added release binaries for riscv64gc-unknown-linux-gnu. These binaries are cross-compiled from x86_64 Linux and are not currently tested.

Fixed

 - Nextest now works with the new build directory layout (-Zbuild-dir-new-layout), and with the build directory being separate from the target directory (build.build-dir). (#3168, #3169)

Changed

 - When retries are enabled, nextest no longer shows TRY 1 SLOW messages for the first attempt. TRY N SLOW is still shown for subsequent attempts.

Miscellaneous

 - Self-update (cargo nextest self update) now uses ureq instead of reqwest and replaces the ring dependency with aws-lc-rs.
   This may require you to install CMake if you're on a less-commonly-used platform. (#3141)

Internal improvements

 - Breaking change to the recording format: recordings now include test group and slot information, enabling Chrome trace export from recordings. (#3158)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.18 2026/03/10 16:27:07 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.132
@


1.18
log
@devel/cargo-nextest: update to 0.9.130

Added

    Nextest now sets several new environment variables for tests and setup scripts: (#3103)
        NEXTEST_VERSION: the current nextest version as a semver string.
        NEXTEST_REQUIRED_VERSION and NEXTEST_RECOMMENDED_VERSION: the minimum required and recommended nextest versions from the repository's nextest-version configuration. If not configured, the value is "none".
        NEXTEST_TEST_THREADS: the computed number of test threads for this run.
        NEXTEST_WORKSPACE_ROOT: the absolute path to the workspace root (respects --workspace-remap).

    Nextest now sets CARGO_BIN_EXE_<name> at runtime for integration tests and benchmarks, matching cargo test in Rust 1.94 and above. Nextest sets this variable on all Rust versions. (#3137)

    Previously, nextest only set NEXTEST_BIN_EXE_<name>, which remains available (and, with underscores, continues to be the recommended form). The CARGO_BIN_EXE_<name> form improves compatibility with tests written for cargo test.

Changed

    The automatic migration of recorded test runs from the cache directory to the state directory, introduced in version 0.9.126, has been removed. Records in the old cache directory location will no longer be migrated. (#3101)

Fixed

A couple of displayer fixes:

    Better sorting for the final summary when counters aren't displayed. (#3100)
    Fixed counter width padding in progress output to use the run count rather than the total test count. (#3102)

Internal improvements

    Cargo JSON output is now streamed directly into the binary list, making binary listing around 6% faster on large workspaces. (#3131) Thanks cornmander for your first contribution!
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.17 2026/03/03 12:17:31 wiz Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.130
@


1.17
log
@cargo-nextest: fix i386 build

From pin@@
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.16 2026/02/23 08:33:58 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.129
@


1.16
log
@devel/cargo-nextest: update to 0.1.129

Changed

    --show-progress=only now behaves like the default auto in non-interactive mode, showing successful tests with a counter. This change was made because only is primarily intended for interactive scenarios. (#3087)
    The MSRV for building nextest has been updated to Rust 1.91.

Fixed

    Setup scripts that write NEXTEST-prefixed environment variables to $NEXTEST_ENV now properly report failure. Previously, the setup script would be reported as successful despite invalid variables, and tests would still run. (#3094)

Internal improvements

    Replay output is now only loaded from the archive when needed. This makes replays around 10-15% faster. (#3090)
    Switched from the zip crate to eazip to address repeated semver breakage in the zip crate. (#3093)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.15 2026/02/20 12:29:09 pin Exp $
d46 3
@


1.15
log
@devel/cargo-nextest: update to 0.9128

Fixed
 - Updated the zip crate to 8.0.0 since versions 7.3.0 and 7.4.0 were yanked.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.14 2026/02/17 13:06:09 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.128
d16 1
a16 1
RUST_REQ=	1.89.0
@


1.14
log
@devel/cargo-nextest: update to 0.9.127

v0.9.127
Added

    A new --partition slice:m/n mode for partitioning test runs. Sliced partitioning distributes tests evenly across shards regardless of how tests are distributed across binaries. This addresses the issue where count:m/n operates per-binary, leading to uneven shard sizes when tests span multiple binaries of varying sizes. (#3052)

    The existing count:m/n partitioner is now deprecated in favor of slice:m/n. Hashed sharding (hash:m/n) continues to be available for use cases where stability across test additions/removals matters more than even distribution.

    Replay and rerun commands (cargo nextest replay, cargo nextest run -R) now accept portable recordings from pipes and process substitutions. For example, cargo nextest run -R <(curl url) now works. (#3071)

Changed

    Nextest no longer creates the store directory unless JUnit output is enabled. This is a step towards deprecating the store directory in favor of portable recordings. (#3053)

Fixed

    Fixed display of file sizes near unit boundaries (e.g. sizes near 1 KiB or 1 MiB) in recording output. (#3072)

v0.9.126
Changed

    Recorded test runs are now stored in the system state directory rather than the cache directory, since they are not regenerable. (#3043)

    Platform 	New location
    Linux, macOS, and other Unix 	$XDG_STATE_HOME/nextest/ or ~/.local/state/nextest/
    Windows 	%LOCALAPPDATA%\nextest\ (unchanged)

    The store location can now be overridden via NEXTEST_STATE_DIR (previously NEXTEST_CACHE_DIR).

    For this release, records in the cache directory will be automatically migrated on the next nextest run. Since this feature is experimental, the migration path will be removed soon (in the next 1-2 releases).

v0.9.125
Added

    New cargo nextest store export command to export recorded runs as portable recordings. Portable recordings are zip archives that can be shared and uploaded as CI artifacts. (#3010)

    cargo nextest replay, cargo nextest run -R, and cargo nextest store info now accept paths to portable recordings (.zip files) in addition to run IDs. This enables replaying and rerunning test results from exported archives, including those downloaded from CI. (#3012)

    Nextest now publishes binaries for aarch64-unknown-linux-musl, providing a statically-linked ARM64 Linux binary with no runtime library dependencies. Thanks altendky for your first contribution! (#3025)

Changed

    USDT tracing probes are now an optional default feature, usdt. This fixes cross-compilation for some targets. Thanks konstin for your first contribution! (#3027)

Fixed

    In replay mode, when output was not captured during recording (e.g. with --no-capture), nextest now shows a "(output not captured)" message rather than blank output. (#3028)

Other

    Published a design document describing how nextest does records, replays and reruns. The audience for this document is nextest contributors and curious readers. We hope you enjoy it!

Security

    Update bytes crate to v1.11.1 for a security fix. (#3032)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.13 2026/01/26 10:26:24 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.127
@


1.13
log
@devel/cargo-nextest: update to 0.9.124

0.9.124
Fixed

The unsupported install mechanism, cargo install cargo-nextest without --locked,
now fails with a helpful error message asking you to use cargo install --locked cargo-nextest.

Note that this unsupported method was broken with version 0.9.123 due to a dependency update,
resulting in several issues being filed. We hope that the new mechanism results in clearer, more helpful guidance.

0.9.123
This is a major release with several new features. If you run into issues, please file a bug.

Added

    Major new feature: experimental support for recording, replaying, and rerunning test runs. Enable by adding record = true to the [experimental] section in user config, or by setting NEXTEST_EXPERIMENTAL_RECORD=1.

    Once enabled, recording can be turned on by adding enabled = true to the [record] section in user config. Recorded runs are stored in the system cache directory.

    New commands:
        cargo nextest replay: Replay a test run (by default, the latest completed run).
        cargo nextest run -R latest: Rerun tests that failed the last time.
        cargo nextest store list: List all recorded runs.
        cargo nextest store info: Show details about a specific run.
        cargo nextest store prune: Prune old recorded runs.

    A new --user-config-file option (environment variable NEXTEST_USER_CONFIG_FILE) allows explicit control over user configuration loading. Pass a path to a specific config file, or none to skip user config entirely.

    A new --cargo-message-format option enables live streaming of Cargo's JSON messages to standard out. This feature is equivalent to cargo test --message-format.

Changed

    The experimental section in repository config can now also be a table, not just an array. The previous array syntax is deprecated but still supported. For example:

    # New style (recommended).
    [experimental]
    benchmarks = true

    # Old style (deprecated)
    experimental = ["benchmarks"]

    Note that user configuration's experimental is always a table. The array syntax is not supported in that case.

    This change enables upcoming config set support over the command line.

    When a config file specifies both a future nextest-version and an unknown experimental feature, the version error now takes precedence. This produces clearer error messages for users running older nextest versions.

Fixed

    Fixed another panic with on-timeout = "pass" in a different code path than the 0.9.117 fix. Thanks gakonst for your first contribution! (#2940)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.12 2026/01/15 09:30:26 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.124
@


1.12
log
@devel/cargo-nextest: update to 0.9.102

Added

 - iTerm now supports the OSC 9;4 progress protocol for progress bar integration. Thanks case for your first contribution!

Fixed

 - Fixed an issue where the progress bar displayed stale statistics during test runs (#2930).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.11 2026/01/14 14:43:03 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.122
@


1.11
log
@devel/cargo-nextest: update to 0.9.121

Fixed

 - In custom target JSONs, panic-strategy = "immediate-abort" now parses correctly (#2922).
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.10 2026/01/12 12:02:06 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.121
@


1.10
log
@devel/cargo-nextest: update to 0.9.120

Added

    Support for using a pager like less with nextest's output. Currently supported are:
        cargo nextest list
        cargo nextest show-config test-groups
        -h and --help commands

    The pager support is closely modeled after the Jujutsu version control system. The default pager is less -FRX on Unix platforms, and a builtin pager (based on sapling-streampager) on Windows.

    cargo nextest self update now supports --beta and --rc flags to update to prerelease versions.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.9 2026/01/05 05:49:08 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.120
@


1.9
log
@devel/cargo-nextest: update to 0.9.118

Added

    Nextest now supports user configuration for personal preferences. User config is stored in ~/.config/nextest/config.toml (or %APPDATA%\nextest\config.toml on Windows) and includes the following settings:
        show-progress: Controls progress display during test runs.
        max-progress-running: Maximum number of running tests to show in the progress bar.
        input-handler: Enable or disable keyboard input handling.
        output-indent: Enable or disable output indentation for captured test output.

    User config settings are lower priority than CLI arguments and environment variables. For details, see User configuration.

Fixed

    Fixed an issue where nextest could hang when tests spawn interactive shells (e.g., zsh -ic) that call tcsetpgrp to become the foreground process group. Nextest now ignores SIGTTIN and SIGTTOU signals while input handling is active. (#2884)
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.8 2026/01/02 17:00:58 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.118
@


1.8
log
@devel/cargo-nextest: update to 0.9.117

Added

 - Experimental support for running benchmarks via cargo nextest bench. Set NEXTEST_EXPERIMENTAL_BENCHMARKS=1 to enable.
 - Benchmarks have a separate configuration namespace with dedicated slow-timeout and global-timeout settings:

    [bench]
    slow-timeout = { period = "120s", terminate-after = 2 }
    global-timeout = "1h"

 - Per-test overrides are also supported within the [bench] section.
 - The list command now supports --message-format oneline for grep-friendly output.
 - Nextest now accepts --target host-tuple to explicitly target the host platform, mirroring Cargo's new feature. This resolves to the detected host triple at runtime. (#2872)

Changed

 - The default output style for cargo nextest list has been changed to a new auto value, which is equivalent to human (the previous default) if standard output is an interactive terminal, and oneline if not.

Fixed

 - Fixed a panic when reporting test results with on-timeout = "pass" in slow-timeout configuration.
 - Retry attempts for tests that both fail and leak handles now correctly display as TRY n FL+LK instead of TRY n FAIL.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.7 2025/12/30 12:29:12 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.117
@


1.7
log
@devel/cargo-nextest: update to 0.9.116

Added

    Nextest now sets several new environment variables for each test execution:
        NEXTEST_TEST_NAME: The name of the test being run.
        NEXTEST_ATTEMPT: The current attempt number (starting from 1).
        NEXTEST_TOTAL_ATTEMPTS: The total number of attempts that will be made.
        NEXTEST_BINARY_ID: The binary ID of the test.
        NEXTEST_ATTEMPT_ID: A unique identifier for this specific attempt.
        NEXTEST_STRESS_CURRENT and NEXTEST_STRESS_TOTAL: For stress tests, the current and total iteration counts.

    These variables allow tests to be aware of their execution context, enabling conditional behavior based on retry attempts or stress test iterations.

    Thanks liranco for your first contribution! (#2797)

    With cargo nextest run --verbose, nextest now displays the command line used to run each test. Thanks dangvu0502 for your first contribution! (#2800)

    A new glossary page documents key nextest terminology.

Changed

    The internal __NEXTEST_ATTEMPT environment variable has been removed and replaced by the public NEXTEST_ATTEMPT variable.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.5 2025/12/19 13:17:09 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.116
@


1.6
log
@devel/cargo-nextest: adopt maintainer
@
text
@d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.115
@


1.5
log
@devel/cargo-nextest: update to 0.9.115

Added

    Nextest profiles now support inheritance via the inherits key. For example:

    [profile.ci]
    retries = 2

    [profile.ci-extended]
    inherits = "ci"
    slow-timeout = "120s"

    Thanks asder8215 for your first contribution! (#2786)

    A new on-timeout option for slow-timeout allows tests that time out to be treated as successes instead of failures. This is useful for fuzz tests, or other tests where a timeout indicates no failing input was found. For example:

    [[profile.default.overrides]]
    filter = 'package(fuzz-targets)'
    slow-timeout = { period = "30s", terminate-after = 1, on-timeout = "pass" }

    Tests that time out and pass are marked TMPASS. See Configuring timeout behavior for more information.

    Thanks eduardorittner for your first contribution! (#2742)

Changed

    MSRV updated to Rust 1.89.
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.4 2025/11/20 12:59:20 wiz Exp $
d9 1
a9 1
MAINTAINER=	pkgsrc-users@@NetBSD.org
@


1.4
log
@cargo-nextest: remove duplicate version number
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.3 2025/11/20 12:35:55 pin Exp $
d3 1
a3 1
DISTNAME=	cargo-nextest-0.9.114
d16 1
a16 1
RUST_REQ=	1.88.0
@


1.3
log
@devel/cargo-nextest: pull correct tag
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.2 2025/11/20 12:24:16 pin Exp $
d7 1
a7 1
GITHUB_TAG=	cargo-nextest-0.9.114
@


1.2
log
@devel/cargo-nextest: satisfy pkglint
@
text
@d1 1
a1 1
# $NetBSD: Makefile,v 1.1 2025/11/20 12:16:47 pin Exp $
d7 1
a7 1
GITHUB_TAG=	cargo-nextest-0.9.113
@


1.1
log
@devel/cargo-nextest: import package

Nextest is a next-generation test runner for Rust.
For more information, check https://nexte.st/
@
text
@d1 1
a1 1
# $NetBSD$
d27 1
a27 1
# 
d35 1
a35 1
# 
d37 1
a37 1
# 
@