-
Notifications
You must be signed in to change notification settings - Fork 32
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
fix the slirp related flake in integration tests #110
Comments
Luap99
added a commit
to Luap99/aardvark-dns
that referenced
this issue
Mar 31, 2022
Commit 4a45167 points at the correct error source however the fix for it was not working. ls -l will alwys look differnt when called on different paths. We only want to compare the actual link target. Fix this by using readlink. Fixes containers#110 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99
added a commit
to Luap99/aardvark-dns
that referenced
this issue
Mar 31, 2022
Commit 4a45167 points at the correct error source however the fix for it was not working. ls -l will always look different when called on different paths. We only want to compare the actual link target. Fix this by using readlink. Fixes containers#110 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99
added a commit
to Luap99/aardvark-dns
that referenced
this issue
Mar 31, 2022
Commit 4a45167 points at the correct error source however the fix for it was not working. ls -l will always look different when called on different paths. We only want to compare the actual link target. Fix this by using readlink. Fixes containers#110 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Luap99
added a commit
to Luap99/aardvark-dns
that referenced
this issue
Jul 26, 2022
Commit 4a45167 points at the correct error source however the fix for it was not working. ls -l will always look different when called on different paths. We only want to compare the actual link target. Fix this by using readlink. Fixes containers#110 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
title says it all. we need to fix the flake.
The text was updated successfully, but these errors were encountered: