• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

zhmcclient / zhmccli / test-1431
39%

Build:
DEFAULT BRANCH: master
Ran 05 Aug 2024 11:22AM UTC
Jobs 10
Files 33
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

05 Aug 2024 11:20AM UTC coverage: 36.575% (+0.08%) from 36.495%
test-1431

push

github

andy-maier
Migrated to use pyproject.toml

Details:

* Dev: Migrated from setup.py to pyproject.toml with setuptools as build
  backend. This provides for automatic determination of the package version
  without having to edit a version file.

More internal details (not in change log):

* setuptools-scm generates the versions into a new file
  zhmccli/_version_scm.py, which gets imported into
  zhmccli/_version.py to maintain its interface. The new
  _version_scm.py file is ignored by git and excluded from any check tools
  (e.g. flake8 or pylint where it would fail).

* Removed creation and use of MANIFEST.in in Makefile.

* Removed _check_version make target, since the version is now always
  determined (from git data), regardless of the build state.

* Removed inclusion of other requirements/constraints files with '-r' and '-c'
  because the dynamic support for dependencies in setuptools does not
  support these options. This has been replaced by ensuring that the
  "included" files are honored, in the Makefile.

* Related to that, renamed minimum-constraints.txt to
  minimum-constraints-develop.txt because it no longer includes
  minimum-constraints-install.txt.

* Related to that, renamed .safety-policy-all.yml to .safety-policy-develop.yml
  to match its scope of only covering development dependencies.

* Updated the base-requirements.txt file to add setuptools-scm.

* Adjusted the retrieval of the package version in docs/conf.py to the new
  version file created by setuptools-scm. This caused any Sphinx commands
  now to depend on the wheel archive, since that is the step that creates
  the setuptools-scm version file.

* Updated the release description in docs/development.rst to no longer edit
  the version file, but to set tags. A new initial tag is now used on the
  master branch that makes setuptools-scm increase the correct version
  number. For consistency, that approach is also used for stable branches.

Signed-off-by: Andreas Maier <maiera@de.ibm.com>

4 of 4 new or added lines in 1 file covered. (100.0%)

2843 of 7773 relevant lines covered (36.58%)

3.66 hits per line

Jobs
ID Job ID Ran Files Coverage
1 macos-latest,3.12,minimum - test-1431.1 05 Aug 2024 11:27AM UTC 0
36.56
GitHub Action Run
2 macos-latest,3.12,latest - test-1431.2 05 Aug 2024 11:27AM UTC 0
36.56
GitHub Action Run
3 ubuntu-latest,3.8,latest - test-1431.3 05 Aug 2024 11:27AM UTC 0
36.58
GitHub Action Run
4 ubuntu-latest,3.12,minimum - test-1431.4 05 Aug 2024 11:27AM UTC 0
36.56
GitHub Action Run
5 windows-latest,3.12,minimum - test-1431.5 05 Aug 2024 11:27AM UTC 0
36.56
GitHub Action Run
6 macos-latest,3.8,minimum - test-1431.6 05 Aug 2024 11:27AM UTC 0
36.58
GitHub Action Run
7 windows-latest,3.12,latest - test-1431.7 05 Aug 2024 11:27AM UTC 0
36.56
GitHub Action Run
8 macos-latest,3.8,latest - test-1431.8 05 Aug 2024 11:27AM UTC 0
36.58
GitHub Action Run
9 windows-latest,3.8,latest - test-1431.9 05 Aug 2024 11:27AM UTC 0
36.58
GitHub Action Run
10 ubuntu-latest,3.12,latest - test-1431.10 05 Aug 2024 11:27AM UTC 0
36.56
GitHub Action Run
Source Files on build test-1431
Detailed source file information is not available for this build.
  • Back to Repo
  • 9f2e8b3a on github
  • Prev Build on master (#TEST-1429)
  • Next Build on master (#TEST-1435)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc