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

test_suite.pl failing on 55 tests #35

Open
tuxlifan opened this issue Apr 9, 2017 · 2 comments
Open

test_suite.pl failing on 55 tests #35

tuxlifan opened this issue Apr 9, 2017 · 2 comments

Comments

@tuxlifan
Copy link

tuxlifan commented Apr 9, 2017

Hello,

Is the test_suite.pl supposed to be up-to-date and succeeding for all test cases?
When I run it there are 55 tests failing.

I'm attaching the script log of the test run, a debug log with all debug options enabled (by adding the other codes to the call in test_suite.pl) and a tarball of the repository.

I'm running Bedrock Linux with Devuan Jessie 1.0 Beta2 as stratum. Other versions are as follow:
$> ./tagsistant/src/tagsistant --version
Tagsistant (tagfs) v.0.8.1a (codename: Berlin)
Build: 578.20160403.000004 FUSE_USE_VERSION: 26
FUSE library version: 2.9.3
fusermount version: 2.9.3
using FUSE kernel interface version 7.19

$> perl --version
This is perl 5, version 20, subversion 2 (v5.20.2) built for x86_64-linux-gnu-thread-multi

$> uname -r
4.8.0-0.bpo.2-amd64

$> id
uid=1000(tags) gid=1006(fuse) groups=1006(fuse)
$> echo $HOME
/tmp/tags
$> mount | grep /tmp
/dev/mapper/vg-Root on /tmp type ext4 (rw,relatime,errors=remount-ro,data=ordered)

Please let me know if you need more information or want me to try something else.

PS: Sorry for the zip madness, github is apparently quite peculiar in the attachment types it allows...

tagsistant_failed_test_suite.zip

@StrumentiResistenti
Copy link
Owner

Hi @tuxlifan, the test suite is probably outdated. I don't run it since long time. I'll check it as soon as possible.

By the way it's really unsatisfying to me the chaining of unrelated tests as a sequence inside the same environment. I would like to split each test (or groups of test) in separate executions to make them more isolated and effective.

@zkol
Copy link

zkol commented Jul 10, 2020

As of now, is there any sort of tests recommended/available to check if a build was successful?

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

No branches or pull requests

3 participants