Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No coverage report data on windows-latest workflows #140

Closed
stephane-caron opened this issue Dec 26, 2022 · 2 comments
Closed

No coverage report data on windows-latest workflows #140

stephane-caron opened this issue Dec 26, 2022 · 2 comments

Comments

@stephane-caron
Copy link

stephane-caron commented Dec 26, 2022

Describe the bug
Since the release of tox-gh-actions 3.0.0 the qpsolvers project has been experiencing Windows CI issues qpsolvers/qpsolvers#141. The symptom is:

py37-windows: commands[7]> coverage report --include=\"qpsolvers/*\"
  No data to report.

Which makes the CI fail. Version-pinning tox-gh-actions to 2.12.0 removes the symptom, as done e.g. in this job.

To Reproduce

  • GitHub Actions configuration: test.yml
  • tox and tox-gh-actions configuration: tox.ini
  • Link to the GitHub Actions job if a repository is public: for instance this one

Expected behavior

Successful coverage report generation.

Additional context

  • The issue only happens only on windows-latest images (ubuntu-latest and macos-latest images work fine).
  • The issue started happening two days ago with this job, which is a minor change following a successful build.
  • Previously this job worked fine. It installed tox-4.0.16 and tox_gh_actions-2.12.0.
  • Version-pinning tox-gh-actions to 2.12.0 removes the symptom, as done e.g. in this job. It installs tox-3.28.0 and tox_gh_actions-2.12.0.
@stephane-caron stephane-caron changed the title No coverage report data on windows-latest builds No coverage report data on windows-latest workflows Dec 26, 2022
@stephane-caron
Copy link
Author

Actually the cure seems to come from tox being downgraded from >=4 to 3.28.0. This job was successful by version-pinning tox to 3.28.0, with no version pin on tox-gh-actions (that is, it installed tox==3.28.0 and tox_gh_actions-3.0.0).

Closing this issue in favor of tox-dev/tox#2778.

@ymyzk
Copy link
Owner

ymyzk commented Dec 27, 2022

@stephane-caron, FYI, we now need to install a different version of tox-gh-actions depending on the tox version.

  • tox-gh-actions v2 must be used with tox v3
  • tox-gh-actions v3 must be used with tox v4

Please see https://github.com/ymyzk/tox-gh-actions#versions-and-compatibility for more details.

Repository owner locked and limited conversation to collaborators Apr 5, 2023
@ymyzk ymyzk converted this issue into discussion #173 Apr 5, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants