-
Notifications
You must be signed in to change notification settings - Fork 214
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
Comments
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. |
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. |
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? |
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
test-suite.log
The text was updated successfully, but these errors were encountered: