Comments (3)
brarcher
commented on July 21, 2024
Part of the unit tests run without emitting any output for a bit, then emit the results of all the tests which were run. How long did you wait for the unit tests to complete? As many of the tests are checking that Check's test timeouts work as expected, the portion where nothing is emitted may be a few minutes. As an example, the last build on Travis-CI which ran on GNU/Linux and used gcc/CMake took 6.5 minutes, where most of the time was spent in unit tests. If the timeout tests are disabled the unit tests run in a matter of seconds. An example of this is the MSVC build on AppVeyor, where the unit tests take less than a second.
from check.
nicola-lunghi
commented on July 21, 2024
Ok thanks sorry my bad :-)
from check.
commented on July 21, 2024
I thought there was something wrong that they just hang... especially seeing they fail instead, with CK_FORK=no:
$ export CK_FORK=no
/home/user/build/1packages/3rarelyused/check/makepkg_pacman/check/src/check
$ make check
Making check in lib
make[1]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/lib'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/lib'
Making check in src
make[1]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/src'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/src'
Making check in doc
make[1]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/doc'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/doc'
Making check in .
make[1]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check'
make[1]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check'
Making check in checkmk
make[1]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/checkmk'
make check-TESTS
make[2]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/checkmk'
make[3]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/checkmk'
PASS: test/check_checkmk
============================================================================
Testsuite summary for Check 0.12.0
============================================================================
# TOTAL: 1
# PASS: 1
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
make[3]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/checkmk'
make[2]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/checkmk'
make[1]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/checkmk'
Making check in tests
make[1]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/tests'
make check-TESTS
make[2]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/tests'
make[3]: Entering directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/tests'
FAIL: check_check
FAIL: check_check_export
PASS: test_check_nofork.sh
PASS: test_check_nofork_teardown.sh
FAIL: test_xml_output.sh
FAIL: test_log_output.sh
PASS: test_set_max_msg_size.sh
FAIL: test_tap_output.sh
FAIL: test_output.sh
============================================================================
Testsuite summary for Check 0.12.0
============================================================================
# TOTAL: 9
# PASS: 3
# SKIP: 0
# XFAIL: 0
# FAIL: 6
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
Please report to check-devel at lists dot sourceforge dot net
============================================================================
make[3]: *** [Makefile:1341: test-suite.log] Error 1
make[3]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/tests'
make[2]: *** [Makefile:1449: check-TESTS] Error 2
make[2]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/tests'
make[1]: *** [Makefile:1578: check-am] Error 2
make[1]: Leaving directory '/home/user/build/1packages/3rarelyused/check-git/makepkg_pacman/check/src/check/tests'
make: *** [Makefile:561: check-recursive] Error 1
========================================
Check 0.12.0: tests/test-suite.log
========================================
# TOTAL: 9
# PASS: 3
# SKIP: 0
# XFAIL: 0
# FAIL: 6
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: check_check_export
========================
Running suite(s): Fork Sub
100%: Checks: 3, Failures: 0, Errors: 0
check_check_fork.c:38:P:Core:test_inc:0: Passed
check_check_fork.c:47:P:Core:test_nofork_sideeffects:0: Passed
check_check_fork.c:54:P:Core:test_nofork_pid:0: Passed
Running suite(s): Check Servant
FAIL check_check_export (exit status: 1)
FAIL: check_check
=================
Running suite(s): Fork Sub
100%: Checks: 3, Failures: 0, Errors: 0
check_check_fork.c:38:P:Core:test_inc:0: Passed
check_check_fork.c:47:P:Core:test_nofork_sideeffects:0: Passed
check_check_fork.c:54:P:Core:test_nofork_pid:0: Passed
Running suite(s): Fix Sub
0%: Checks: 1, Failures: 1, Errors: 0
check_check_fixture.c:36:S:Fix Sub:unchecked_setup:0: Test failure in fixture
Running suite(s): Check Servant
FAIL check_check (exit status: 1)
FAIL: test_output.sh
====================
Problem with ex_output CK_MINIMAL STDOUT NORMAL
Expected:
Running suite(s): S1
S2
XML escape " ' < > &
X� tests
37%: Checks: 8, Failures: 4, Errors: 1
Got:
Running suite(s): S1
FAIL test_output.sh (exit status: 1)
FAIL: test_xml_output.sh
========================
Problem with ex_xml_output
Expected:
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="http://check.sourceforge.net/xml/check_unittest.xslt"?>
<testsuites xmlns="http://check.sourceforge.net/ns">
<suite>
<title>S1</title>
<test result="success">
<fn>ex_output.c:31</fn>
<id>test_pass</id>
<iteration>0</iteration>
<description>Core</description>
<message>Passed</message>
</test>
<test result="failure">
<fn>ex_output.c:37</fn>
<id>test_fail</id>
<iteration>0</iteration>
<description>Core</description>
<message>Failure</message>
</test>
<test result="error">
<fn>ex_output.c:46</fn>
<id>test_exit</id>
<iteration>0</iteration>
<description>Core</description>
<message>Early exit with return value 1</message>
</test>
</suite>
<suite>
<title>S2</title>
<test result="success">
<fn>ex_output.c:66</fn>
<id>test_pass2</id>
<iteration>0</iteration>
<description>Core</description>
<message>Passed</message>
</test>
<test result="failure">
<fn>ex_output.c:72</fn>
<id>test_loop</id>
<iteration>0</iteration>
<description>Core</description>
<message>Iteration 0 failed</message>
</test>
<test result="success">
<fn>ex_output.c:72</fn>
<id>test_loop</id>
<iteration>1</iteration>
<description>Core</description>
<message>Passed</message>
</test>
<test result="failure">
<fn>ex_output.c:72</fn>
<id>test_loop</id>
<iteration>2</iteration>
<description>Core</description>
<message>Iteration 2 failed</message>
</test>
</suite>
<suite>
<title>XML escape " ' < > & 	 
X tests</title>
<test result="failure">
<fn>ex_output.c:78</fn>
<id>test_xml_esc_fail_msg</id>
<iteration>0</iteration>
<description>description " ' < > & 	 
X end</description>
<message>fail " ' < > & 	 
X message</message>
</test>
</suite>
</testsuites>
Got:
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="http://check.sourceforge.net/xml/check_unittest.xslt"?>
<testsuites xmlns="http://check.sourceforge.net/ns">
<suite>
<title>S1</title>
<test result="success">
<fn>ex_output.c:31</fn>
<id>test_pass</id>
<iteration>0</iteration>
<description>Core</description>
<message>Passed</message>
</test>
<test result="failure">
<fn>ex_output.c:37</fn>
<id>test_fail</id>
<iteration>0</iteration>
<description>Core</description>
<message>Failure</message>
</test>
FAIL test_xml_output.sh (exit status: 1)
FAIL: test_log_output.sh
========================
Problem with ex_log_output CK_SILENT LOG NORMAL
Expected:
Running suite S1
ex_output.c:31:P:Core:test_pass:0: Passed
ex_output.c:37:F:Core:test_fail:0: Failure
ex_output.c:46:E:Core:test_exit:0: (after this point) Early exit with return value 1
Running suite S2
ex_output.c:66:P:Core:test_pass2:0: Passed
ex_output.c:72:F:Core:test_loop:0: Iteration 0 failed
ex_output.c:72:P:Core:test_loop:1: Passed
ex_output.c:72:F:Core:test_loop:2: Iteration 2 failed
Running suite XML escape " ' < > &
X� tests
ex_output.c:78:F:description " ' < > &
X� end:test_xml_esc_fail_msg:0: fail " ' < > &
X� message
Results for all suites run:
37%: Checks: 8, Failures: 4, Errors: 1
Got:
Running suite S1
ex_output.c:31:P:Core:test_pass:0: Passed
ex_output.c:37:F:Core:test_fail:0: Failure
FAIL test_log_output.sh (exit status: 1)
FAIL: test_tap_output.sh
========================
Problem with ex_tap_output
Expected:
ok 1 - ex_output.c:Core:test_pass: Passed
not ok 2 - ex_output.c:Core:test_fail: Failure
not ok 3 - ex_output.c:Core:test_exit: Early exit with return value 1
ok 4 - ex_output.c:Core:test_pass2: Passed
not ok 5 - ex_output.c:Core:test_loop: Iteration 0 failed
ok 6 - ex_output.c:Core:test_loop: Passed
not ok 7 - ex_output.c:Core:test_loop: Iteration 2 failed
not ok 8 - ex_output.c:description " ' < > &
X� end:test_xml_esc_fail_msg: fail " ' < > &
X� message
1..8
Got:
ok 1 - ex_output.c:Core:test_pass: Passed
not ok 2 - ex_output.c:Core:test_fail: Failure
FAIL test_tap_output.sh (exit status: 1)
but this issue tells me I'm wrong and I need to wait for 7 mins... :)
oh it took less! only 2mins 57seconds!
all passed!
from check.
Related Issues (20)
- Issue: Not able use Check-C framework with arm-none-eabi-gcc compiler HOT 3
- Question: make subunit dependency explicit HOT 1
- cmake_minimum_required(...) has a wrong version required HOT 2
- Restore scan-build checks for snprintf replacement
- Undefined references HOT 2
- check_check and check_check_export fail on Guix powerpc64le-linux HOT 3
- Glenn Washburn's JUnit patch was never merged back then. What happened? HOT 2
- migrate open SourceForge bugs and features to GitHub
- several potential bugs of NULL Pointer Dereference HOT 3
- Wrong binaries on Windows HOT 2
- Enhancement: Adding Check test discovery for CMake
- Check Installation on Windows 64 Bit HOT 3
- Can't compile on Ubuntu with Codeblocks HOT 1
- Add assert functions for ASCII character
- Add assert functions for wide character and string of wide characters
- Deeper integration in CLion for detailed information HOT 1
- MacOS M1 with brew & CMAKE installation has missing files
- Custom report output HOT 1
- Feedback: it feels like libcheck's default setup is hostile to debuggers
- cmake deprecation warning - policy CMP0076
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from check.