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 is failing #867

Open
goneall opened this issue Nov 1, 2023 · 3 comments
Open

CI is failing #867

goneall opened this issue Nov 1, 2023 · 3 comments
Labels

Comments

@goneall
Copy link
Member

goneall commented Nov 1, 2023

It looks like there is a problem in some of the dependencies needing an update.

Below is the output from the failed run:

        File "/tmp/pip-build-env-cdrc14e2/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 251, in add_defaults
          self._add_defaults_ext()
        File "/tmp/pip-build-env-cdrc14e2/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/sdist.py", line 336, in _add_defaults_ext
          self.filelist.extend(build_ext.get_source_files())
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "<string>", line 201, in get_source_files
        File "/tmp/pip-build-env-cdrc14e2/overlay/lib/python3.12/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
          raise AttributeError(attr)
      AttributeError: cython_sources
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Notice:  A new release of pip is available: 23.2.1 -> 23.3.1
Notice:  To update, run: pip install --upgrade pip
Error: Process completed with exit code 1.

Complete CI output:
errors.txt

@goneall
Copy link
Member Author

goneall commented Apr 4, 2024

@licquia - can you take a look?

@licquia
Copy link
Collaborator

licquia commented Apr 5, 2024

Ref: yaml/pyyaml#702

The odd thing is that there's no reason why we shouldn't always be building this test with newer PyYAML, which has a workaround for this problem. I'll try pushing an extra requirement on newer PyYAML to see if that fixes the problem.

licquia pushed a commit that referenced this issue Apr 5, 2024
Due to a build incompatibility between PyYAML and Cython 3.0.0, builds
of PyYAML from source to satisfy a dependency will fail without a
workaround introduced in PyYAML 6.0.1.  Therefore, we should insist on
installing at least that version.

Fixes #867.

Signed-off-by: Jeff Licquia <jeff@licquia.org>
licquia pushed a commit that referenced this issue Apr 5, 2024
Due to a build incompatibility between PyYAML and Cython 3.0.0, builds
of PyYAML from source to satisfy a dependency will fail without a
workaround introduced in PyYAML 6.0.1.  Therefore, we should insist on
installing at least that version.

Fixes #867.

Signed-off-by: Jeff Licquia <jeff@licquia.org>
@licquia
Copy link
Collaborator

licquia commented Apr 5, 2024

Tried pulling that fix into the 2.3.1 build, but it doesn't work there. One of the requirements there requires PyYAML 5, and so the requirements are uninstallable if we insist on 6.

I've pushed a new workaround on the 2.3.1 branch which looks like it works on my system.

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

No branches or pull requests

2 participants