You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
diff --git a/tests/cmd/absolute_recurse_unix.stdout b/tests/cmd/absolute_recurse_unix.stdout
index 44233b9..9c56e28 100644
--- a/tests/cmd/absolute_recurse_unix.stdout
+++ b/tests/cmd/absolute_recurse_unix.stdout
@@ -36,7 +36,7 @@ tests/itest/vagrant:
tests/itest/vagrant/debug:
[CWD]/tests/itest/vagrant/debug/a
[CWD]/tests/itest/vagrant/debug/symlink -> a
-[CWD]/tests/itest/vagrant/debug/symlink-broken -> ./b
+[CWD]/tests/itest/vagrant/debug/symlink-broken -> b
tests/itest/vagrant/dev:
[CWD]/tests/itest/vagrant/dev/main.bf
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:
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
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
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: