Menu
▾
▴
zookeeper-developer
|
From: SourceForge.net <no...@so...> - 2008-05-14 05:56:06
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
|
From: SourceForge.net <no...@so...> - 2008-05-16 17:44:15
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Comment added) made by phunt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- >Comment By: Patrick Hunt (phunt) Date: 2008-05-16 10:44 Message: Logged In: YES user_id=12853 Originator: YES Ben please merge this asap to address ci issue. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
|
From: SourceForge.net <no...@so...> - 2008-05-20 01:57:14
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Comment added) made by breed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- >Comment By: Benjamin Reed (breed) Date: 2008-05-19 18:57 Message: Logged In: YES user_id=154690 Originator: NO Is this really enough? It will still show up as unstable build if there are error messages printed even though it returns successfully. Right? ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-05-16 10:44 Message: Logged In: YES user_id=12853 Originator: YES Ben please merge this asap to address ci issue. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
|
From: SourceForge.net <no...@so...> - 2008-06-06 18:55:21
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Comment added) made by phunt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- >Comment By: Patrick Hunt (phunt) Date: 2008-06-06 11:55 Message: Logged In: YES user_id=12853 Originator: YES If the tests pass the build will be successful. If a test fails (throws exception or assertX fails) then build will be unsuccessful. This is regardless of println/logging output. Hudson actually parses the output looking for errors (even if build is listed as successful) - if build is successful but there are failure type messages in the stdout/log then it will list the build as unstable, otw will list as success/failure appropriately. I tested the failure case Nigel was seeing and it addressed the issue. ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-05-19 18:57 Message: Logged In: YES user_id=154690 Originator: NO Is this really enough? It will still show up as unstable build if there are error messages printed even though it returns successfully. Right? ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-05-16 10:44 Message: Logged In: YES user_id=12853 Originator: YES Ben please merge this asap to address ci issue. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
|
From: SourceForge.net <no...@so...> - 2008-06-06 19:00:15
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Comment added) made by breed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- >Comment By: Benjamin Reed (breed) Date: 2008-06-06 12:00 Message: Logged In: YES user_id=154690 Originator: NO great. I'll commit then. ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-06-06 11:55 Message: Logged In: YES user_id=12853 Originator: YES If the tests pass the build will be successful. If a test fails (throws exception or assertX fails) then build will be unsuccessful. This is regardless of println/logging output. Hudson actually parses the output looking for errors (even if build is listed as successful) - if build is successful but there are failure type messages in the stdout/log then it will list the build as unstable, otw will list as success/failure appropriately. I tested the failure case Nigel was seeing and it addressed the issue. ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-05-19 18:57 Message: Logged In: YES user_id=154690 Originator: NO Is this really enough? It will still show up as unstable build if there are error messages printed even though it returns successfully. Right? ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-05-16 10:44 Message: Logged In: YES user_id=12853 Originator: YES Ben please merge this asap to address ci issue. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
|
From: SourceForge.net <no...@so...> - 2008-06-06 19:05:29
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Comment added) made by breed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- >Comment By: Benjamin Reed (breed) Date: 2008-06-06 12:05 Message: Logged In: YES user_id=154690 Originator: NO Committed revision 175. ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-06-06 12:00 Message: Logged In: YES user_id=154690 Originator: NO great. I'll commit then. ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-06-06 11:55 Message: Logged In: YES user_id=12853 Originator: YES If the tests pass the build will be successful. If a test fails (throws exception or assertX fails) then build will be unsuccessful. This is regardless of println/logging output. Hudson actually parses the output looking for errors (even if build is listed as successful) - if build is successful but there are failure type messages in the stdout/log then it will list the build as unstable, otw will list as success/failure appropriately. I tested the failure case Nigel was seeing and it addressed the issue. ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-05-19 18:57 Message: Logged In: YES user_id=154690 Originator: NO Is this really enough? It will still show up as unstable build if there are error messages printed even though it returns successfully. Right? ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-05-16 10:44 Message: Logged In: YES user_id=12853 Originator: YES Ben please merge this asap to address ci issue. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
|
From: SourceForge.net <no...@so...> - 2008-06-06 19:05:46
|
Patches item #1963584, was opened at 2008-05-13 22:56 Message generated for change (Settings changed) made by breed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 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: 3.0.0 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Patrick Hunt (phunt) Assigned to: Benjamin Reed (breed) Summary: fix build.xml cobertura test harness Initial Comment: Need to fail if the junit tests fail - missing fail is causing build to be successful even if cobertura fails. (ci is running cobertura and not std test target) ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-06-06 12:05 Message: Logged In: YES user_id=154690 Originator: NO Committed revision 175. ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-06-06 12:00 Message: Logged In: YES user_id=154690 Originator: NO great. I'll commit then. ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-06-06 11:55 Message: Logged In: YES user_id=12853 Originator: YES If the tests pass the build will be successful. If a test fails (throws exception or assertX fails) then build will be unsuccessful. This is regardless of println/logging output. Hudson actually parses the output looking for errors (even if build is listed as successful) - if build is successful but there are failure type messages in the stdout/log then it will list the build as unstable, otw will list as success/failure appropriately. I tested the failure case Nigel was seeing and it addressed the issue. ---------------------------------------------------------------------- Comment By: Benjamin Reed (breed) Date: 2008-05-19 18:57 Message: Logged In: YES user_id=154690 Originator: NO Is this really enough? It will still show up as unstable build if there are error messages printed even though it returns successfully. Right? ---------------------------------------------------------------------- Comment By: Patrick Hunt (phunt) Date: 2008-05-16 10:44 Message: Logged In: YES user_id=12853 Originator: YES Ben please merge this asap to address ci issue. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1008546&aid=1963584&group_id=209147 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X