| Port details |
- py-stestr Parallel Python test runner built around subunit
- 4.1.0 devel
 =0      Package not present on quarterly.This port was created during this quarter. It will be in the next quarterly branch but not the current one. - Maintainer: sunpoet@FreeBSD.org
- Port Added: 2024-04-08 20:18:14
- Last Update: 2024-04-08 20:16:40
- Commit Hash: 287df32
- Also Listed In: python
- License: APACHE20
- WWW:
- https://stestr.readthedocs.io/en/latest/
- https://github.com/mtreinish/stestr
- Description:
- stestr is parallel Python test runner designed to execute unittest test suites
using multiple processes to split up execution of a test suite. It also will
store a history of all test runs to help in debugging failures and optimizing
the scheduler to improve speed. To accomplish this goal it uses the subunit
protocol to facilitate streaming and storing results from multiple workers.
stestr originally started as a fork of the testrepository project. But, instead
of being an interface for any test runner that used subunit, like
testrepository, stestr concentrated on being a dedicated test runner for python
projects. While stestr was originally forked from testrepository it is not
backwards compatible with testrepository. At a high level the basic concepts of
operation are shared between the two projects but the actual usage is not
exactly the same.
  ¦  ¦  ¦  ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}stestr>0:devel/py-stestr@${PY_FLAVOR}
- To install the port:
- cd /usr/ports/devel/py-stestr/ && make install clean
- To add the package, run one of these commands:
- pkg install devel/py-stestr
- pkg install py39-stestr
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above.
NOTE: This is a Python port. Instead of py39-stestr listed in the above command, you can pick from the names under the Packages section.- PKGNAME: py39-stestr
- Package flavors (<flavor>: <package>)
- distinfo:
- TIMESTAMP = 1712580500
SHA256 (stestr-4.1.0.tar.gz) = 5f61c369eece63c292d13599e12aa158af7685990643f24dd6fa7fabfe34e98a
SIZE (stestr-4.1.0.tar.gz) = 113187
Packages (timestamps in pop-ups are UTC):
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py39-pbr>=2.0.0 : devel/py-pbr@py39
- py39-setuptools>=0 : devel/py-setuptools@py39
- py39-wheel>=0 : devel/py-wheel@py39
- python3.9 : lang/python39
- py39-build>=0 : devel/py-build@py39
- py39-installer>=0 : devel/py-installer@py39
- Test dependencies:
-
- python3.9 : lang/python39
- Runtime dependencies:
-
- py39-cliff>=2.8.0 : devel/py-cliff@py39
- py39-extras>=1.0.0 : devel/py-extras@py39
- py39-fixtures>=3.0.0 : devel/py-fixtures@py39
- py39-pbr>=2.0.0 : devel/py-pbr@py39
- py39-python-subunit>=1.3.0 : devel/py-python-subunit@py39
- py39-testtools>=2.2.0 : devel/py-testtools@py39
- py39-tomlkit>=0.11.6 : textproc/py-tomlkit@py39
- py39-voluptuous>=0.8.9 : devel/py-voluptuous@py39
- py39-yaml>=3.10.0 : devel/py-yaml@py39
- python3.9 : lang/python39
- There are no ports dependent upon this port
Configuration Options:- No options to configure
- Options name:
- devel_py-stestr
- USES:
- python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
Number of commits found: 1
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
|---|
4.1.0
08 Apr 2024 20:16:40
 |
Po-Chuan Hsieh (sunpoet) |
devel/py-stestr: Add py-stestr 4.1.0
stestr is parallel Python test runner designed to execute unittest test suites
using multiple processes to split up execution of a test suite. It also will
store a history of all test runs to help in debugging failures and optimizing
the scheduler to improve speed. To accomplish this goal it uses the subunit
protocol to facilitate streaming and storing results from multiple workers.
stestr originally started as a fork of the testrepository project. But, instead
of being an interface for any test runner that used subunit, like
testrepository, stestr concentrated on being a dedicated test runner for python
projects. While stestr was originally forked from testrepository it is not
backwards compatible with testrepository. At a high level the basic concepts of
operation are shared between the two projects but the actual usage is not
exactly the same. |
Number of commits found: 1
|
As an Amazon Associate I earn from qualifying purchases.