#111 "No messaging setup" in check_msg causes test failure

[Kalle Richter]

Running make check in an autotools-based project causes all tests to fail and check_msg.c:80: No messaging setup to be logged to test-suite.log. I found http://sourceforge.net/p/check/bugs/74/ which doesn't apply because I don't use Windows and http://sourceforge.net/p/check/mailman/message/2750522/ which doesn't contain any replies.

The issue occurs with commit 054d8457ad057dd24fb31ba0d9a8cab8ee174561 of auto-apt.

I'm using Ubuntu 15.04 amd64 with Linux 4.1.4.

[Kalle Richter]

Please try 85397d394231bd03bc8897ba9f671f03032bb417. Of course, I can create a minimal example reproducing the case if you don't figure it out immediately.

[Kalle Richter]

This is most likely related to low test coverage (< 90 %) in check_msg.c. The output of gcovr:

{{{
------------------------------------------------------------------------------
GCC Code Coverage Report
Directory: .
------------------------------------------------------------------------------
File Lines Exec Cover Missing
------------------------------------------------------------------------------
check.c 222 218 98% 65,114,315,545
check_check_exit.c 21 18 85% 39,41-42
check_check_export_main.c 13 13 100%
check_check_fixture.c 309 275 88% 73,76,99,101,138,140-142,144,146-148,150,152,197,200,323,326,414,417,460,463,512,515,565,568-572,574-576,578
check_check_fork.c 67 67 100%
check_check_limit.c 20 20 100%
check_check_log.c 134 133 99% 26
check_check_log_internal.c 3 3 100%
check_check_main.c 23 23 100%
check_check_master.c 188 158 84% 282,285,289,291-292,295,299,324-325,334-335,337,370,375,426-427,429,442-443,452-453,455,602-603,609-610,616-617,648,650
check_check_msg.c 98 98 100%
check_check_pack.c 235 223 94% 37,40,68,71,75,78,103,105-106,129-130,282
check_check_selective.c 133 133 100%
check_check_sub.c 699 315 45% 9,11-12,33,35-36,47,49-50,54,56-57,62,64-65,69,71-72,77,79-80,84,86-89,91,93,95-98,100,102,104-107,112,115-116,121,123-124,128,130-131,136,138-139,146,148-155,157,159,161-162,166,168-170,172,174,176-181,183,185,187-190,192,194,196-201,203,205,207-210,212,214,216-220,222,224,226-229,231,233,235-240,242,244,246-249,251,253,255-259,261,263,265-268,270,272,274-279,281,283,285-288,290,300,302-307,309,311,313-316,318,320,322-327,329,331,333-336,338,340,342-346,348,350,352-355,357,359,361-366,368,370,372-375,377,379,381-385,387,389,391-394,396,398,400-405,407,409,411-414,416,426,428-431,433,435,437-442,444,446,448-452,454,456,458-463,465,467,469-473,475,477,479-484,486,498,500-505,507,509,511-518,520,523,529,531,533,535-536,538,540,542-543,545,561,564-569,575,577,579,600,602-603,605,614,616-617,619,627,629-630,632,640,642-643,645,647,649-650,652,671,676-684,689,691-696,706,712-713,723-726,730-731,741,756,758-759,772,775,792,795,797-798,824,853,855-856,873,878-879,882,884-885,887,889-890
check_list.c 92 92 100%
check_log.c 169 163 96% 220,259,333,378,461,548
check_msg.c 109 98 89% 80,129,137,300,311-313,322-324,329
check_nofork.c 15 13 86% 19,21
check_nofork_teardown.c 17 17 100%
check_pack.c 174 165 94% 288,293,295-296,308,317,330,344,384
check_print.c 78 73 93% 133,167,186-188
check_run.c 303 277 91% 114,116,118-119,123,126,131-133,136,235,410,458,497,505,525,553-554,556,558,565,576,586,598,713,765
check_str.c 36 31 86% 50,55,57,60,101
ex_output.c 106 83 78% 15,17,56,58,112,114,118-126,175-176,210-211,242-243,256-257
------------------------------------------------------------------------------
TOTAL 3264 2709 82%
------------------------------------------------------------------------------
}}}

[Branden Archer]

Kalle,

Thanks for your interested in Check. Sorry for not replying earlier.

If you are able to create a minimal example, it would help greatly. With
such an example we would be able to more easily determine the failure, as
well as use the example as the basis for a unit test once the issue is
resolved.

• Branden

On Thu, Sep 10, 2015 at 4:34 PM, Kalle Richter krichter722@users.sf.net
wrote:

This is most likely related to low test coverage (< 90 %) in check_msg.c.
The output of gcovr:

{{{

---

GCC Code Coverage Report
Directory: .

---

File Lines Exec Cover Missing

---

check.c 222 218 98% 65,114,315,545
check_check_exit.c 21 18 85% 39,41-42
check_check_export_main.c 13 13 100%
check_check_fixture.c 309 275 88%
73,76,99,101,138,140-142,144,146-148,150,152,197,200,323,326,414,417,460,463,512,515,565,568-572,574-576,578
check_check_fork.c 67 67 100%
check_check_limit.c 20 20 100%
check_check_log.c 134 133 99% 26
check_check_log_internal.c 3 3 100%
check_check_main.c 23 23 100%
check_check_master.c 188 158 84%
282,285,289,291-292,295,299,324-325,334-335,337,370,375,426-427,429,442-443,452-453,455,602-603,609-610,616-617,648,650
check_check_msg.c 98 98 100%
check_check_pack.c 235 223 94% 37,40,68,71,75,78,103,105-106,129-130,282
check_check_selective.c 133 133 100%
check_check_sub.c 699 315 45%
9,11-12,33,35-36,47,49-50,54,56-57,62,64-65,69,71-72,77,79-80,84,86-89,91,93,95-98,100,102,104-107,112,115-116,121,123-124,128,130-131,136,138-139,146,148-155,157,159,161-162,166,168-170,172,174,176-181,183,185,187-190,192,194,196-201,203,205,207-210,212,214,216-220,222,224,226-229,231,233,235-240,242,244,246-249,251,253,255-259,261,263,265-268,270,272,274-279,281,283,285-288,290,300,302-307,309,311,313-316,318,320,322-327,329,331,333-336,338,340,342-346,348,350,352-355,357,359,361-366,368,370,372-375,377,379,381-385,387,389,391-394,396,398,400-405,407,409,411-414,416,426,428-431,433,435,437-442,444,446,448-452,454,456,458-463,465,467,469-473,475,477,479-484,486,498,500-505,507,509,511-518,520,523,529,531,533,535-536,538,540,542-543,545,561,564-569,575,577,579,600,602-603,605,614,616-617,619,627,629-630,632,640,642-643,645,647,649-650,652,671,676-684,689,691-696,706,712-713,723-726,730-731,741,756,758-759,772,775,792,795,797-798,824,853,855-856,873,878-879,882,884-885,887,889-890
check_list.c 92 92 100%
check_log.c 169 163 96% 220,259,333,378,461,548
check_msg.c 109 98 89% 80,129,137,300,311-313,322-324,329
check_nofork.c 15 13 86% 19,21
check_nofork_teardown.c 17 17 100%
check_pack.c 174 165 94% 288,293,295-296,308,317,330,344,384
check_print.c 78 73 93% 133,167,186-188
check_run.c 303 277 91%
114,116,118-119,123,126,131-133,136,235,410,458,497,505,525,553-554,556,558,565,576,586,598,713,765
check_str.c 36 31 86% 50,55,57,60,101
ex_output.c 106 83 78%
15,17,56,58,112,114,118-126,175-176,210-211,242-243,256-257

---

TOTAL 3264 2709 82%

---

}}}

• [bugs:#111] http://sourceforge.net/p/check/bugs/111/ "No messaging
  setup" in check_msg causes test failure*

Status: open
Group: v1.0 (example)
Created: Sun Aug 23, 2015 08:40 PM UTC by Kalle Richter
Last Updated: Mon Aug 24, 2015 08:06 AM UTC
Owner: nobody

Running make check in an autotools-based project causes all tests to fail
and check_msg.c:80: No messaging setup to be logged to test-suite.log. I
found http://sourceforge.net/p/check/bugs/74/ which doesn't apply because
I don't use Windows and
http://sourceforge.net/p/check/mailman/message/2750522/ which doesn't
contain any replies.

The issue occurs with commit 054d8457ad057dd24fb31ba0d9a8cab8ee174561 of
auto-apt https://github.com/krichter722/auto-apt.

I'm using Ubuntu 15.04 amd64 with Linux 4.1.4.

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/check/bugs/111/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Branden Archer]

We've not heard anything back yet. We you able to identify the issue or create a minimal test case demonstrating the issue? If so, and you are interested in pursuing this further, open an issue against Check in its new home here:

https://github.com/libcheck/check

[Kalle Richter]

continuing at https://github.com/libcheck/check/issues/18