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

Fedora 28 (x86_64) test fails #157

Open
spotrh opened this issue May 30, 2018 · 3 comments
Open

Fedora 28 (x86_64) test fails #157

spotrh opened this issue May 30, 2018 · 3 comments

Comments

@spotrh
Copy link

spotrh commented May 30, 2018

With check 0.12.0:
make check-TESTS
make[2]: Entering directory '/home/spot/git/check/check-0.12.0/tests'
make[3]: Entering directory '/home/spot/git/check/check-0.12.0/tests'
FAIL: check_check_export
FAIL: check_check
PASS: test_output.sh
PASS: test_check_nofork.sh
PASS: test_check_nofork_teardown.sh
PASS: test_xml_output.sh
PASS: test_log_output.sh
PASS: test_set_max_msg_size.sh
PASS: test_tap_output.sh

==========================================================================
Testsuite summary for Check 0.12.0
============================================================================
# TOTAL: 9
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

test-suite.log

@brarcher
Copy link
Contributor

Is the device where the tests are being run dedicated hardware or a VM? I see a few cases of tests timing out instead of completing, which may indicate they did not have enough time to complete. I've seen that on my machine if I'm running a VM and the performance is sluggish. If it is not a VM, let me know.

@spotrh
Copy link
Author

spotrh commented Jun 1, 2018

This is on dedicated hardware (Thinkpad T460). It is also failing in the Fedora buildsystem, which uses VMs, but I wanted to reproduce it locally first.

@brarcher
Copy link
Contributor

brarcher commented Sep 7, 2018

Hm, I've not been able to reproduce this on my own. I installed Fedora 28 on a VM without any windows manager and was able to build Check and run its unit tests without a failure.

The logs you posted earlier show that one or more of the tests timed out instead of completing. I've only seen that when the system running the tests is otherwise bogged down, not letting the unit tests run with the resources required to succeed.

Without being able to reproduce it myself, I'm not sure how much help I can provide. Are you seeing it every time you run the unit tests?

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

2 participants