You can subscribe to this list here.
2008 |
Jan
|
Feb
|
Mar
(10) |
Apr
(6) |
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: SourceForge.net <no...@so...> - 2011-10-22 09:19:32
|
Bugs item #3383253, was opened at 2011-07-31 23:49 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3383253&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Report inconsistencies with failling sub-threads Initial Comment: If a test case run many threads which have failing assertions, the report at the end of the execution of the test suite is weird. If I add a single test within an existing project which runs 64 threads which will fail, I have te following: 1) Failure: test_foo plop test_foo.c:18: foo_thread(): cut_fail("plop") 2) Failure: test_foo plop test_foo.c:18: foo_thread(): cut_fail("plop") [...] 64) Failure: test_foo plop test_foo.c:18: foo_thread(): cut_fail("plop") 65) Omission: test_mac_link At least two NFC devices must be plugged-in to run this test test_mac_link.c:46: cut_setup(): cut_omit("At least two NFC devices must be plugged-in to run this test") Finished in 0,193801 seconds (total: 0,148543 seconds) 26 test(s), 715 assertion(s), 64 failure(s), 0 error(s), 0 pending(s), 1 omission(s), 0 notification(s) 100% passed Each fialing thread has been counted as a failing test (while only a single test fails), and the percentage of success is inconsistant. ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2011-10-22 18:19 Message: I'm sorry for my late response. I've fixed inconsistancy of the percentage of success but count of failures isn't touched. Because "XX failure(s)" means number of failures not number of failed tests. So "64 failure(s)" is correct. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3383253&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-07-31 14:49:46
|
Bugs item #3383253, was opened at 2011-07-31 16:49 Message generated for change (Tracker Item Submitted) made by smortex You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3383253&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Report inconsistencies with failling sub-threads Initial Comment: If a test case run many threads which have failing assertions, the report at the end of the execution of the test suite is weird. If I add a single test within an existing project which runs 64 threads which will fail, I have te following: 1) Failure: test_foo plop test_foo.c:18: foo_thread(): cut_fail("plop") 2) Failure: test_foo plop test_foo.c:18: foo_thread(): cut_fail("plop") [...] 64) Failure: test_foo plop test_foo.c:18: foo_thread(): cut_fail("plop") 65) Omission: test_mac_link At least two NFC devices must be plugged-in to run this test test_mac_link.c:46: cut_setup(): cut_omit("At least two NFC devices must be plugged-in to run this test") Finished in 0,193801 seconds (total: 0,148543 seconds) 26 test(s), 715 assertion(s), 64 failure(s), 0 error(s), 0 pending(s), 1 omission(s), 0 notification(s) 100% passed Each fialing thread has been counted as a failing test (while only a single test fails), and the percentage of success is inconsistant. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3383253&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-07-31 11:27:29
|
Bugs item #3341429, was opened at 2011-06-29 02:30 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3341429&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Random crashes when assertions are failling from threads Initial Comment: Hello I am using cutter to do test with hardware and run two threads (one per device) and check that they communicate correctly. I recentry realised that a failling assertion cause a crash of cutter. A simple test case is attached. Uncommenting the cut_fail line produce crashes. Running cutter a few times produce different crashes. Tested on GNU/Linux and FreeBSD with latest released cutter version (1.1.7) and on FreeBSD with trunk version of cutter. ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2011-07-31 20:27 Message: I've fixed it in trunk. I'll release a new version soon. ---------------------------------------------------------------------- Comment By: Kouhei Sutou (ktou) Date: 2011-07-03 17:34 Message: Sorry for my late response. It's Cutter's bug. I found that Cutter can't handle assertion failures in thread. I'll try to support assertion failures in thread but it'll not be done soon... I don't have time for now... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3341429&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-07-03 08:34:12
|
Bugs item #3341429, was opened at 2011-06-29 02:30 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3341429&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Random crashes when assertions are failling from threads Initial Comment: Hello I am using cutter to do test with hardware and run two threads (one per device) and check that they communicate correctly. I recentry realised that a failling assertion cause a crash of cutter. A simple test case is attached. Uncommenting the cut_fail line produce crashes. Running cutter a few times produce different crashes. Tested on GNU/Linux and FreeBSD with latest released cutter version (1.1.7) and on FreeBSD with trunk version of cutter. ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2011-07-03 17:34 Message: Sorry for my late response. It's Cutter's bug. I found that Cutter can't handle assertion failures in thread. I'll try to support assertion failures in thread but it'll not be done soon... I don't have time for now... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3341429&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-06-28 17:30:52
|
Bugs item #3341429, was opened at 2011-06-28 19:30 Message generated for change (Tracker Item Submitted) made by smortex You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3341429&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Random crashes when assertions are failling from threads Initial Comment: Hello I am using cutter to do test with hardware and run two threads (one per device) and check that they communicate correctly. I recentry realised that a failling assertion cause a crash of cutter. A simple test case is attached. Uncommenting the cut_fail line produce crashes. Running cutter a few times produce different crashes. Tested on GNU/Linux and FreeBSD with latest released cutter version (1.1.7) and on FreeBSD with trunk version of cutter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3341429&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-01-09 23:12:17
|
Bugs item #3153801, was opened at 2011-01-10 06:08 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3153801&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: randomaction () Assigned to: Nobody/Anonymous (nobody) Summary: test failure: cut_utils_compare_string Initial Comment: Cutter fails one of the self-tests when building for powerpc architecture on Debian [1] or Ubuntu [2]. The reason is that strcmp is assumed to return -1, 0, or 1. It is, however, not guaranteed. According to strcmp(3), "The strcmp() function compares the two strings s1 and s2. It returns an integer less than, equal to, or greater than zero if s1 is found, respectively, to be less than, to match, or be greater than s2." On powerpc, strcmp("a", "b") returns -2^24, and the test in test_compare_string() which compares result to -1 fails. Either the tests must be modified to assert that the result is positive/negative, or cut_utils_compare_string() modified to return -1, 0, or 1. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599980 [2] https://launchpad.net/ubuntu/+source/cutter-testing-framework/1.1.3-1ubuntu1/+build/2137955 ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2011-01-10 08:12 Message: > I've fixed it in trunk. (r3833) r3833 and r3834. ---------------------------------------------------------------------- Comment By: Kouhei Sutou (ktou) Date: 2011-01-10 08:09 Message: Thanks for your report! I've fixed it in trunk. (r3833) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3153801&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-01-09 23:09:06
|
Bugs item #3153801, was opened at 2011-01-10 06:08 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3153801&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: randomaction () Assigned to: Nobody/Anonymous (nobody) Summary: test failure: cut_utils_compare_string Initial Comment: Cutter fails one of the self-tests when building for powerpc architecture on Debian [1] or Ubuntu [2]. The reason is that strcmp is assumed to return -1, 0, or 1. It is, however, not guaranteed. According to strcmp(3), "The strcmp() function compares the two strings s1 and s2. It returns an integer less than, equal to, or greater than zero if s1 is found, respectively, to be less than, to match, or be greater than s2." On powerpc, strcmp("a", "b") returns -2^24, and the test in test_compare_string() which compares result to -1 fails. Either the tests must be modified to assert that the result is positive/negative, or cut_utils_compare_string() modified to return -1, 0, or 1. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599980 [2] https://launchpad.net/ubuntu/+source/cutter-testing-framework/1.1.3-1ubuntu1/+build/2137955 ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2011-01-10 08:09 Message: Thanks for your report! I've fixed it in trunk. (r3833) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3153801&group_id=208375 |
From: SourceForge.net <no...@so...> - 2011-01-09 21:08:49
|
Bugs item #3153801, was opened at 2011-01-10 00:08 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3153801&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: randomaction () Assigned to: Nobody/Anonymous (nobody) Summary: test failure: cut_utils_compare_string Initial Comment: Cutter fails one of the self-tests when building for powerpc architecture on Debian [1] or Ubuntu [2]. The reason is that strcmp is assumed to return -1, 0, or 1. It is, however, not guaranteed. According to strcmp(3), "The strcmp() function compares the two strings s1 and s2. It returns an integer less than, equal to, or greater than zero if s1 is found, respectively, to be less than, to match, or be greater than s2." On powerpc, strcmp("a", "b") returns -2^24, and the test in test_compare_string() which compares result to -1 fails. Either the tests must be modified to assert that the result is positive/negative, or cut_utils_compare_string() modified to return -1, 0, or 1. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599980 [2] https://launchpad.net/ubuntu/+source/cutter-testing-framework/1.1.3-1ubuntu1/+build/2137955 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3153801&group_id=208375 |
From: SourceForge.net <no...@so...> - 2010-08-31 12:11:55
|
Bugs item #3056684, was opened at 2010-08-31 20:04 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3056684&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Add support for lcov 1.9 Initial Comment: lcov 1.9 is out: http://ltp.sourceforge.net/coverage/lcov/changes.php Thi patch adds version 1.9 to the list of supported versions. ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2010-08-31 21:11 Message: Thanks! I've applied your patch! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3056684&group_id=208375 |
From: SourceForge.net <no...@so...> - 2010-08-31 11:04:29
|
Bugs item #3056684, was opened at 2010-08-31 13:04 Message generated for change (Tracker Item Submitted) made by smortex You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3056684&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: Add support for lcov 1.9 Initial Comment: lcov 1.9 is out: http://ltp.sourceforge.net/coverage/lcov/changes.php Thi patch adds version 1.9 to the list of supported versions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=3056684&group_id=208375 |
From: SourceForge.net <no...@so...> - 2010-03-26 13:45:06
|
Bugs item #2976775, was opened at 2010-03-26 09:03 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2976775&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: cut_omit() / cut_pend() in setup() Initial Comment: Hi Using cut_omit() in a setup() function stops the execution of the current setup() function but do not prevents the test from being actually run. The cut_pend() function called in a setup() function do prevent the test from being run. In both case, the teardown() function is executed; in the first case cutter returns 0, in the second one cutter returns 1. The documentation lacks details about the differences between these functions for the developer to decide which to choose from. Additionally, another behaviour might be of interest: stopping the current setup() function, skipping the test, running the teardown() function and returning 0: when testing code that interact with hardware devices (e.g. contactless card reader), different test environments (e.g. different devices) and configurations (e.g. number of cards on the device) may be suitable for a set of tests and all developers of the project may not be able to have the same hardware configuration. A convenient way for them to test the area they are working on is to just ignore tests that cannot run with their configuration; however cut_pend() will make cutter return 1, and cut_omit() require the "overhead" of setting a flag in the setup() function that is read in tests to return silently. Branching directly from setup() to teardown() and exiting with an error code of 0 would be really handy in such a situation. Is calling cut_omit() / cut_pend() from a setup() function a "supported" feature ? Can we imagine a new API providing the previously described behaviour (e.g. cut_stop()) ? Or have I missed one in the documentation ? If cut_omit was not designed to be run from setup(), maybe it could be changed to not run the test and match that behaviour ? Thanks! Romain ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2010-03-26 22:45 Message: Thanks for reporting. I've fixed it in trunk. Now, cut_omit() is supported in cut_setup(). Here are difference between cut_omit() and cut_pend(): cut_omit(): The test is meaningless on the environment. It's OK that the test isn't run. (It means cutter returns 0.) cut_pend(): The test should be completed but it's not the current work. It's not OK that the test isn't run and doesn't pass correct assertions. (It means cutter returns non-0.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2976775&group_id=208375 |
From: SourceForge.net <no...@so...> - 2010-03-26 00:03:20
|
Bugs item #2976775, was opened at 2010-03-26 01:03 Message generated for change (Tracker Item Submitted) made by smortex You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2976775&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Tartière (smortex) Assigned to: Nobody/Anonymous (nobody) Summary: cut_omit() / cut_pend() in setup() Initial Comment: Hi Using cut_omit() in a setup() function stops the execution of the current setup() function but do not prevents the test from being actually run. The cut_pend() function called in a setup() function do prevent the test from being run. In both case, the teardown() function is executed; in the first case cutter returns 0, in the second one cutter returns 1. The documentation lacks details about the differences between these functions for the developer to decide which to choose from. Additionally, another behaviour might be of interest: stopping the current setup() function, skipping the test, running the teardown() function and returning 0: when testing code that interact with hardware devices (e.g. contactless card reader), different test environments (e.g. different devices) and configurations (e.g. number of cards on the device) may be suitable for a set of tests and all developers of the project may not be able to have the same hardware configuration. A convenient way for them to test the area they are working on is to just ignore tests that cannot run with their configuration; however cut_pend() will make cutter return 1, and cut_omit() require the "overhead" of setting a flag in the setup() function that is read in tests to return silently. Branching directly from setup() to teardown() and exiting with an error code of 0 would be really handy in such a situation. Is calling cut_omit() / cut_pend() from a setup() function a "supported" feature ? Can we imagine a new API providing the previously described behaviour (e.g. cut_stop()) ? Or have I missed one in the documentation ? If cut_omit was not designed to be run from setup(), maybe it could be changed to not run the test and match that behaviour ? Thanks! Romain ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2976775&group_id=208375 |
From: SourceForge.net <no...@so...> - 2009-09-23 01:07:55
|
Bugs item #2847203, was opened at 2009-08-30 18:00 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2847203&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Markus Elfring (elfring) Assigned to: Nobody/Anonymous (nobody) Summary: reserved identifier violation Initial Comment: I suggest to try the search pattern "_+[A-Z]+" on the source files. You will find a couple of places where names begin with an underscore and an uppercase letter. Examples: - __CUT_ANALYZER_H__ http://cutter.svn.sourceforge.net/viewvc/cutter/cutter/trunk/cutter/cut-analyzer.h?revision=2267&view=markup - _CutTestContext http://cutter.svn.sourceforge.net/viewvc/cutter/cutter/trunk/cutter/cut-test-context.h?revision=2956&view=markup This does not fit to the expected naming conventions of the C language standard. http://en.wikipedia.org/wiki/Reserved_identifier See also section "7.1.3 Reserved identifiers". http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1124.pdf ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2009-09-23 10:07 Message: Thanks for your suggestion. We are following GLib's coding style. When GLib changes its coding style like suggested by you, we will follow the style. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2847203&group_id=208375 |
From: SourceForge.net <no...@so...> - 2009-08-30 09:00:12
|
Bugs item #2847203, was opened at 2009-08-30 11:00 Message generated for change (Tracker Item Submitted) made by elfring You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2847203&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Markus Elfring (elfring) Assigned to: Nobody/Anonymous (nobody) Summary: reserved identifier violation Initial Comment: I suggest to try the search pattern "_+[A-Z]+" on the source files. You will find a couple of places where names begin with an underscore and an uppercase letter. Examples: - __CUT_ANALYZER_H__ http://cutter.svn.sourceforge.net/viewvc/cutter/cutter/trunk/cutter/cut-analyzer.h?revision=2267&view=markup - _CutTestContext http://cutter.svn.sourceforge.net/viewvc/cutter/cutter/trunk/cutter/cut-test-context.h?revision=2956&view=markup This does not fit to the expected naming conventions of the C language standard. http://en.wikipedia.org/wiki/Reserved_identifier See also section "7.1.3 Reserved identifiers". http://www.open-std.org/JTC1/SC22/WG14/www/docs/n1124.pdf ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2847203&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-06-24 04:07:29
|
Bugs item #2001417, was opened at 2008-06-24 13:05 Message generated for change (Settings changed) made by ikezoe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2001417&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Deleted Resolution: Invalid Priority: 5 Private: No Submitted By: Hiroyuki Ikezoe (ikezoe) Assigned to: Nobody/Anonymous (nobody) Summary: test Initial Comment: test ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2001417&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-06-24 04:06:18
|
Bugs item #2001417, was opened at 2008-06-24 13:05 Message generated for change (Settings changed) made by ikezoe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2001417&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Invalid Priority: 5 Private: No Submitted By: Hiroyuki Ikezoe (ikezoe) Assigned to: Nobody/Anonymous (nobody) Summary: test Initial Comment: test ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2001417&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-06-24 04:05:52
|
Bugs item #2001417, was opened at 2008-06-24 13:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2001417&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Hiroyuki Ikezoe (ikezoe) Assigned to: Nobody/Anonymous (nobody) Summary: test Initial Comment: test ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=2001417&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-04-12 02:20:14
|
Bugs item #1927725, was opened at 2008-03-27 21:48 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1927725&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Accepted Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: cutter doesn't check arguments for formated strings Initial Comment: Please add G_GNUC_PRINTF to cut_test_context_register_result() and other similar functions. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2008-04-11 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Kouhei Sutou (ktou) Date: 2008-03-27 22:56 Message: Logged In: YES user_id=1012232 Originator: NO I've added it to cut_test_context_take_printf() but not to cut_test_context_register_result(). Becaue it's too difficult. If we add G_GNUC_PRINTF, we can't omit a message for cut_assert_equal() without a warning: cut_assert_equal(1, 1); /* NG */ We are happy if we can write like the following: void cut_test_context_register_result (CutTestContext *context, CutTestResultStatus status, const char *function_name, const char *filename, unsigned int line, const char *message, ...) CUT_GNUC_PRINTF(7, 8); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1927725&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-04-03 02:27:39
|
Bugs item #1932062, was opened at 2008-04-02 18:44 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1932062&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: --help-gtk and --help-report-xml aren't recognized Initial Comment: $ cutter --help-all Usage: cutter [OPTION...] TEST_DIRECTORY Help Options: -?, --help Show help options --help-all Show all help options --help-report Show report options --help-ui Show UI options --help-report-xml Show XML report options --help-ui-console Show console UI options --help-gtk Show GTK+ Options ... But $ cutter --help-gtk Unknown option --help-gtk $ LANG=C cutter --help-report-xml Unknown option --help-report-xml ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2008-04-03 11:27 Message: Logged In: YES user_id=1012232 Originator: NO I've fixed in trunk. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1932062&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-04-02 09:44:06
|
Bugs item #1932062, was opened at 2008-04-02 18:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1932062&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: --help-gtk and --help-report-xml aren't recognized Initial Comment: $ cutter --help-all Usage: cutter [OPTION...] TEST_DIRECTORY Help Options: -?, --help Show help options --help-all Show all help options --help-report Show report options --help-ui Show UI options --help-report-xml Show XML report options --help-ui-console Show console UI options --help-gtk Show GTK+ Options ... But $ cutter --help-gtk Unknown option --help-gtk $ LANG=C cutter --help-report-xml Unknown option --help-report-xml ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1932062&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-04-02 09:18:16
|
Bugs item #1931954, was opened at 2008-04-02 16:32 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1931954&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: --help-all requires an additional garbage argument Initial Comment: $ cutter --help-all Missing argument for --help-all $ cutter --help-all unko-oomori Usage: cutter [OPTION...] TEST_DIRECTORY Help Options: -?, --help Show help options --help-all Show all help options --help-report Show report options ... ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2008-04-02 18:18 Message: Logged In: YES user_id=1012232 Originator: NO I've fixed in trunk. Thanks for reporting! ---------------------------------------------------------------------- Comment By: Takuro Ashie (makeinu) Date: 2008-04-02 17:16 Message: Logged In: YES user_id=364243 Originator: YES --version option also requires it. $ cutter --version Missing argument for --version $ cutter --version makiguso 0.7.0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1931954&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-04-02 08:16:09
|
Bugs item #1931954, was opened at 2008-04-02 16:32 Message generated for change (Comment added) made by makeinu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1931954&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: --help-all requires an additional garbage argument Initial Comment: $ cutter --help-all Missing argument for --help-all $ cutter --help-all unko-oomori Usage: cutter [OPTION...] TEST_DIRECTORY Help Options: -?, --help Show help options --help-all Show all help options --help-report Show report options ... ---------------------------------------------------------------------- >Comment By: Takuro Ashie (makeinu) Date: 2008-04-02 17:16 Message: Logged In: YES user_id=364243 Originator: YES --version option also requires it. $ cutter --version Missing argument for --version $ cutter --version makiguso 0.7.0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1931954&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-04-02 07:32:19
|
Bugs item #1931954, was opened at 2008-04-02 16:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1931954&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: --help-all requires an additional garbage argument Initial Comment: $ cutter --help-all Missing argument for --help-all $ cutter --help-all unko-oomori Usage: cutter [OPTION...] TEST_DIRECTORY Help Options: -?, --help Show help options --help-all Show all help options --help-report Show report options ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1931954&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-03-28 05:56:40
|
Bugs item #1927725, was opened at 2008-03-28 13:48 Message generated for change (Comment added) made by ktou You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1927725&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Accepted Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: cutter doesn't check arguments for formated strings Initial Comment: Please add G_GNUC_PRINTF to cut_test_context_register_result() and other similar functions. ---------------------------------------------------------------------- >Comment By: Kouhei Sutou (ktou) Date: 2008-03-28 14:56 Message: Logged In: YES user_id=1012232 Originator: NO I've added it to cut_test_context_take_printf() but not to cut_test_context_register_result(). Becaue it's too difficult. If we add G_GNUC_PRINTF, we can't omit a message for cut_assert_equal() without a warning: cut_assert_equal(1, 1); /* NG */ We are happy if we can write like the following: void cut_test_context_register_result (CutTestContext *context, CutTestResultStatus status, const char *function_name, const char *filename, unsigned int line, const char *message, ...) CUT_GNUC_PRINTF(7, 8); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1927725&group_id=208375 |
From: SourceForge.net <no...@so...> - 2008-03-28 04:48:59
|
Bugs item #1927725, was opened at 2008-03-28 13:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1927725&group_id=208375 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Takuro Ashie (makeinu) Assigned to: Nobody/Anonymous (nobody) Summary: cutter doesn't check arguments for formated strings Initial Comment: Please add G_GNUC_PRINTF to cut_test_context_register_result() and other similar functions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1005444&aid=1927725&group_id=208375 |