René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG]: Windows CI Tests False-Positive of Passing","articleBody":"### Description\r\n\r\nAfter reviewing your `Actions`, it is clear tests are not running on Windows machines. On Windows, the `linter and test` script does not output any results and takes 0 or 1s to complete, whereas on Linux/MacOS they take \u003e1 minute and output `pytest` results.\r\n\r\nYour `.github/workflows/pythonpackage.yml` worflow does not specify a shell to use in the `Run tests and linters` step. Hence, on Windows, it defaults to using Powershell. Thus, what is run ([which you can see in this example workflow](https://github.com/commitizen-tools/commitizen/actions/runs/3073641248/jobs/4965906704)) is simply:\r\n\r\n```pwsh\r\npwsh -Command ./scripts/test\r\n```\r\n\r\nThis does nothing more than ask Windows to attempt to open a file it does not know how to handle, which is easily repeated locally:\r\n\r\nhttps://user-images.githubusercontent.com/59346180/196010833-4f63b4b0-864a-496e-9ee9-cdaa490685bf.mp4\r\n\r\nCloning the repo, changing the shebang [to a portable variant](https://www.diskinternals.com/linux-reader/usr-bin-bash/), and running `pytest`, it is clear many tests are failing on Windows. This was first noticed in #602 \r\n\r\nhttps://github.com/commitizen-tools/commitizen/files/9790428/pytest_report.zip\r\n\r\n### Steps to reproduce\r\n\r\n1. Follow the [Contributing](https://commitizen-tools.github.io/commitizen/contributing/) steps to:\r\n    (a) Fork the repo, install dependencies through poetry, and setup the pre-commit hooks\r\n2. Run pre-commit run --all\r\n\r\n### Current behavior\r\n\r\nTests are failing silently on GitHub Actions (i.e. CI), yielding false positives on prior commits. Tests fail explicitly when the repo is cloned and tested on Windows, which also prevents developers using Windows to contribute (`pre-commit` tests fail, preventing pushing to PRs).\r\n\r\n### Desired behavior\r\n\r\n1. Windows tests run on GitHub Actions\r\n2. Windows users can contribute to your repo\r\n\r\nIf you continue to package for Windows, you need to confirm that your tests are actually running and passing. Your tests are failing at this point.\r\n\r\n### Screenshots\r\n\r\nPlease see the `Description`.\r\n\r\n### Environment\r\n\r\nCommitizen Version: 2.35.0\r\nPython Version: 3.8.10 (tags/v3.8.10:3d8993a, May 3 2021, 11:48:03) [MSC v.1928 64 bit (AMD64)]\r\nOperating System: Windows\r\n\r\n### Local `pytest` Report\r\n\r\nAdding the `pytest` run on Windows, first referenced in #602 . This report was generated using the [`pytest-html` plugin](https://pypi.org/project/pytest-html/).\r\n\r\n[pytest_report.zip](https://github.com/commitizen-tools/commitizen/files/9801994/pytest_report.zip)","author":{"url":"https://github.com/adam-grant-hendry","@type":"Person","name":"adam-grant-hendry"},"datePublished":"2022-10-15T23:20:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/604/commitizen/issues/604"}