Skip to content

Run pytest again on CI #40446

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

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Conversation

tobiasdiez
Copy link
Contributor

Pytest used to run on CI, but this is no longer the case. Here, we reactivate it by removing some safe-guards that are no longer necessary as pytest is a standard package now.

📝 Checklist

  • The title is concise and informative.
  • The description explains in detail what this PR is about.
  • I have linked a relevant issue or discussion.
  • I have created tests covering the changes.
  • I have updated the documentation and checked the documentation preview.

⌛ Dependencies

@tobiasdiez
Copy link
Contributor Author

No idea about the failing tests in test-long....

@orlitzky
Copy link
Contributor

I guess the CI is invoking pytest via the ./sage script and a doctest wrapper? I was just typing pytest like a crazy person.

@tobiasdiez
Copy link
Contributor Author

I guess the CI is invoking pytest via the ./sage script and a doctest wrapper? I was just typing pytest like a crazy person.

Yes, pytest is called as part of sage -t (that was supposed to work already). I don't get the test failures in dev_tools.py - they seem to be unrelated.

@user202729
Copy link
Contributor

Maybe you should retrigger the CI (e.g. by pushing an empty commit) just in case.

@tobiasdiez
Copy link
Contributor Author

Maybe you should retrigger the CI (e.g. by pushing an empty commit) just in case.

15f17bb is almost such an empty commit but didn't fix it. I've now opened #40474 for a minimally invasive solution.

vbraun pushed a commit to vbraun/sage that referenced this pull request Aug 1, 2025
sagemathgh-40474: Add pytest command to run tests in CI workflow
    
<!-- ^ Please provide a concise and informative title. -->
<!-- ^ Don't put issue numbers in the title, do this in the PR
description below. -->
<!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method
to calculate 1 + 2". -->
<!-- v Describe your changes below in detail. -->
<!-- v Why is this change required? What problem does it solve? -->
<!-- v If this PR resolves an open issue, please link to it here. For
example, "Fixes sagemath#12345". -->

Alternative to sagemath#40446. This time
running pytest directly in the CI, instead of as part of `sage -t`.

Removed one old test file that fails with meson since the sage cli is
different then.

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->

- [ ] The title is concise and informative.
- [ ] The description explains in detail what this PR is about.
- [ ] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] I have updated the documentation and checked the documentation
preview.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on. For example,
-->
<!-- - sagemath#12345: short description why this is a dependency -->
<!-- - sagemath#34567: ... -->
    
URL: sagemath#40474
Reported by: Tobias Diez
Reviewer(s):
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants