ci: Test failing in openSUSE package for 0.18.0
If eza fails to compile, or if there is a problem during the build process, then please include the following information in your report:
- The exact eza commit you are building:
d0c6fef - The version of rustc you are compiling it with:
rustc 1.76.0 (07dca489a 2024-02-04) (built from a source tarball) - Your operating system and hardware platform:
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
[ 111s] Testing tests/cmd/absolute_recurse_unix.toml ... failed
[ 111s] 39 - [CWD]/tests/itest/vagrant/debug/symlink-broken -> ./b
[ 111s] 39 + [CWD]/tests/itest/vagrant/debug/symlink-broken -> b
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.
@photosheep I wonder if 2e6df0b fixed the issue, can you check?
Also, this sounds like an issue that should be opened in opensuse.
Same is happening for follow-symlinks_unix and tree_unix now.
trycmd has been acting weird recently, I wonder if distros that see these issues don't build with our deps