-
-
Notifications
You must be signed in to change notification settings - Fork 156
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: Test failing in openSUSE package for 0.18.0 #902
Comments
photosheep
changed the title
ci: Test failing in openSUSE package for 1
ci: Test failing in openSUSE package for 0.18.0
Mar 21, 2024
bmwiedemann
pushed a commit
to bmwiedemann/openSUSE
that referenced
this issue
Mar 21, 2024
https://build.opensuse.org/request/show/1160078 by user jubalh + anag+factory - Filter dependencies for vendor tarball - Cleanup changes and comments from last submission - Add eza-fix-test.patch: Fix test in container build environment. See gh/eza-community/eza#902 - Remove unneeded cargo_config - Update to 0.18.8: Bug Fixes: * Avoid deprecation warnings * Rustfmt issues Features: * Add fennel lang icon and associations
@photosheep I wonder if 2e6df0b fixed the issue, can you check? Also, this sounds like an issue that should be opened in opensuse. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If eza fails to compile, or if there is a problem during the build process, then please include the following information in your report:
d0c6fef
rustc 1.76.0 (07dca489a 2024-02-04) (built from a source tarball)
openSUSE Tumbleweed, chroot (local) or xen (OBS)
If you are seeing compilation errors, please include the output of the build process.
One specific test is failing.
Relevant lines
Full buildlog
This doesn't seem to impact functionality so I've fixed it locally with this patch. This seems similar to a dust build issue I ran into a while ago.
Edit: It does't actually seem that similar to the Dust error, outside of them both being weird formatting-related issues. It may be a weird downstream thing on our end, or a shared crate acting odd.
The text was updated successfully, but these errors were encountered: