Skip to content
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

ci: fix tests running #85

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

ci: fix tests running #85

wants to merge 8 commits into from

Conversation

vinitkumar
Copy link
Member

Description

Related resources

  • #...
  • #...

Checklist

  • I have opened this pull request against master
  • I have added or modified the tests when changing logic
  • I have followed the conventional commits guidelines to add meaningful information into the changelog
  • I have read the contribution guidelines and I have joined #workgroup-pr-review on
    Slack to find a “pr review buddy” who is going to review my pull request.

@fsbraun
Copy link
Member

fsbraun commented Dec 12, 2024

@vinitkumar It seems the compiled test requirements do not contain a pinned version of django CMS and the tests always install the latest django CMS 4. I guess the compilescript needs an update to include the django-cms version.

@marksweb I am not sure it is a good idea to pin the installed versions for tests. We miss incompatibilities from changes in libraries after the compile time. What do you think?

@marksweb
Copy link
Member

@fsbraun do you specifically mean pinning cms?

@fsbraun
Copy link
Member

fsbraun commented Dec 12, 2024

@marksweb The requirements.in did not include django-cms and hence the compile.py did not pin the django-cms version in the compiled requirements (e.g., missing here). Since the package itself depends on django-cms, the latest django-cms was installed for each of the tests letting them fail (since the tests do not run on django CMS 4 yet).

I've added django-cms to requirements.in to let the tests run against the specified django-cms version.

But my question was a different one: I would prefer not to compile the requirements for tests to always run against the latest dependencies. Otherwise, we will not notice incompatibilities introduced in new releases of dependencies after the compile time. Am I missing something?

@marksweb
Copy link
Member

@fsbraun you're probably not missing anything but this was a pattern I picked up from Adam Johnson. And I quite like how easy it makes updating and maintaining requirements. I get the point about missing new releases. But maybe we can script /automate the updating of requirements a bit like how dependant can. Or maybe the requirements themselves can be more broad and just be greater than a given version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants