[JIRA] (JENKINS-35422) Valgrind plugin failed to parse (String index out of range) for complex C++ trace.
Title: Message Title Johannes Ohlemacher closed an issue as Fixed Jenkins / JENKINS-35422 Valgrind plugin failed to parse (String index out of range) for complex C++ trace. Change By: Johannes Ohlemacher Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34643) New release
Title: Message Title Johannes Ohlemacher closed an issue as Fixed Jenkins / JENKINS-34643 New release Change By: Johannes Ohlemacher Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Johannes Ohlemacher resolved as Fixed added pipeline support with version 0,28, thx Wulkop! Jenkins / JENKINS-34981 Make valgrind-plugin compatible with pipeline Change By: Johannes Ohlemacher Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups
[JIRA] (JENKINS-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Johannes Ohlemacher started work on JENKINS-34981 Change By: Johannes Ohlemacher Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-35156) valgrind plugin crashes
Title: Message Title Johannes Ohlemacher commented on JENKINS-35156 Re: valgrind plugin crashes I will look into it. Can you give details about your configuration and environment? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-28670) Cannot set environment variables
Title: Message Title Johannes Ohlemacher commented on JENKINS-28670 Re: Cannot set environment variables Hi Stephen, have you tried the EnvInject plugin? https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin Does that solve your problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-24971) valgrind not run if working directory set.
Johannes Ohlemacher commented on JENKINS-24971 valgrind not run if working directory set. The release of the original version 0.23 failed and i did not notice that immediately. I did a new release (0.24) a couple of hours ago and you can download the plugin manually from here: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/valgrind/0.24/ It will take up to 12 hours until its visible in jenkins update center and on the website. That delay is very unfortunate, but it's the way the jenkins infrastructure works ;( This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-24971) valgrind not run if working directory set.
Johannes Ohlemacher resolved JENKINS-24971 as Fixed valgrind not run if working directory set. I am not sure why it was that way, but the patterns being relative to the working directory made absolutely no sense and i considered that a bug. With version 0.23 patterns are now always relative to workspace. Change By: Johannes Ohlemacher (23/Nov/14 7:05 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-16218) include suppressions from valgrind
Johannes Ohlemacher resolved JENKINS-16218 as Fixed include suppressions from valgrind fixed this long overdue issue with version 0.23 added option to generate and display suppression information added option to use suppression files Change By: Johannes Ohlemacher (23/Nov/14 7:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
Johannes Ohlemacher closed JENKINS-13745 as Fixed Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception The actual problems was fixed some time ago. I created a new issue JENKINS-25750 for the performance concerns (see comments above). Change By: Johannes Ohlemacher (23/Nov/14 11:03 AM) Status: Reopened Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-25750) Investigate performance issues
Johannes Ohlemacher created JENKINS-25750 Investigate performance issues Issue Type: Task Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 23/Nov/14 10:59 AM Description: As mentioned in the comments of issue JENKINS-13745, loading time for reports increases dramatically with larger amount of data (in this example case 250 reports per build, each report is ~1MB). Project: Jenkins Priority: Minor Reporter: Johannes Ohlemacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
Johannes Ohlemacher commented on JENKINS-13745 Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception @Artem: you are welcome I am worried about performance too, its on my todo list since quite some time. I have a lot on my plate right now, so this has to wait a few more weeks. 250Mb of valgrind reports seems like a challenging test case This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
Johannes Ohlemacher commented on JENKINS-13745 Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception @Artem: thanks for uploading your report files. Most of those files are basically empty or contain no process information (required by the plugin). Those files caused the plugin to crash. It shouldn't happend anymore with version 0.22 (just released, wait a few hours until it shows up in your update center) btw: I am not sure, how you managed to create those empty report files... maybe there is a problem with your valgrind calls... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
Johannes Ohlemacher commented on JENKINS-13745 Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception @Artem: other users seem to have no problem with the latest release (see comments of ticket JENKINS-24256), so i suspect there is something special with your data or your setup. Thanks for the stacktrace, it tells me where the plugin crashed but not exactly why. Could you send me the xml report from valgrind? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24562) Publish Valgrind results and ClearCase
Johannes Ohlemacher edited a comment on JENKINS-24562 Publish Valgrind results and ClearCase Hello Knut, i am not familiar with ClearCase, so i am not sure, if i fully understand the problem. The plugin just reads files from the filesystem via an api provided by jenkins (jenkins handles filesystems on remote build slaves, so the plugin doesn't need to care about that). Could you send me a little sample project? (the project/job definition, including a problematic build and the workspace with all files/views checked out) i think that could help email: johannes [dot] ohlemacher [at] googlemail [dot] com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24562) Publish Valgrind results and ClearCase
Johannes Ohlemacher commented on JENKINS-24562 Publish Valgrind results and ClearCase Hello Knut, i am not familiar with ClearCase, so i am not sure, if i fully understand the problem. The plugin just reads files from the filesystem via an api provided by jenkins (jenkins handles filesystems on remote build slaves, so the plugin doesn't need to care about that). Could you send me a little sample project? (the project/job definition, including a problematic build and the workspace with all files/views checked out) email: johannes [dot] ohlemacher [at] googlemail [dot] com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs
Johannes Ohlemacher edited a comment on JENKINS-24256 Fail build for missing / erroneous valgrind publisher XMLs fixed in version 0.21, added two new publisher options: fail build on missing reports fail build on invalid/malformed reports @Christian: Thanks for reporting and testing! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs
Johannes Ohlemacher resolved JENKINS-24256 as Fixed Fail build for missing / erroneous valgrind publisher XMLs fixed in version 0.21, added to new option: fail build on missing reports fail build on invalid/malformed reports @Christian: Thanks for reporting and testing! Change By: Johannes Ohlemacher (01/Sep/14 6:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-16859) Plugin forgets "Ignore Exit Code" setting
Johannes Ohlemacher edited a comment on JENKINS-16859 Plugin forgets "Ignore Exit Code" setting fixed with version 0.21 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-16859) Plugin forgets "Ignore Exit Code" setting
Johannes Ohlemacher resolved JENKINS-16859 as Fixed Plugin forgets "Ignore Exit Code" setting fixe with version 0.21 Change By: Johannes Ohlemacher (01/Sep/14 6:33 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-23529) The plugin publisher reports no error although the generated xml contains memory violations
Johannes Ohlemacher commented on JENKINS-23529 The plugin publisher reports no error although the generated xml contains memory violations FYI: i added a new publisher option to version 0.21: 'fail build on missing reports' Enabling this option should help to track down such problems! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs
Johannes Ohlemacher commented on JENKINS-24256 Fail build for missing / erroneous valgrind publisher XMLs Sounds reasonable and should be easy to integrate. I am pretty busy right now, but i will try to look into it within the next couple of days. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-16999) No delete button to remove valgrind report publisher
Johannes Ohlemacher closed JENKINS-16999 as Not A Defect No delete button to remove valgrind report publisher That button is not part of the valgrind plugin. Its created by Jenkins directly to remove 'post build actions' from the configuration (in this case 'publish valgrind result'). I just checked the latest jenkins release (1.569) and everything seems to be fine Change By: Johannes Ohlemacher (26/Jun/14 7:40 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-23529) The plugin publisher reports no error although the generated xml contains memory violations
Johannes Ohlemacher commented on JENKINS-23529 The plugin publisher reports no error although the generated xml contains memory violations just looked into it, could not reproduce the problem you described. What exactly does your Report Pattern look like? I noticed that something like './my_report.valgrind' does not work (the plugin finds no reports, hence no reported errors)! Try 'my_report.valgrind' instead! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-23529) The plugin publisher reports no error although the generated xml contains memory violations
Johannes Ohlemacher started work on JENKINS-23529 The plugin publisher reports no error although the generated xml contains memory violations Change By: Johannes Ohlemacher (23/Jun/14 11:34 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-23178) Read DynamicAnalysis.xml written by CTest
Johannes Ohlemacher resolved JENKINS-23178 as Postponed Read DynamicAnalysis.xml written by CTest Its not a bug. The file from CTest is not a valgrind xml file, its completely different. The file from CTest does not even contain easily parsable xml data from valgrind, its just the standard output. The memcheck feature of CTest seems still to be experimental, CTest must export valid valgrind xml to make this work! Change By: Johannes Ohlemacher (25/May/14 11:31 AM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-16859) Plugin forgets "Ignore Exit Code" setting
Johannes Ohlemacher commented on JENKINS-16859 Plugin forgets "Ignore Exit Code" setting Ok, i will look into it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [valgrind] (JENKINS-18556) On the Valgrind Process Details page, the "possibly lost" total is missing (null bytes) and the description paragraphs for "possibly" and "definitely" should be swapp
Johannes Ohlemacher started work on JENKINS-18556 On the Valgrind Process Details page, the "possibly lost" total is missing (null bytes) and the description paragraphs for "possibly" and "definitely" should be swapped. Change By: Johannes Ohlemacher (30/Jul/13 3:34 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [valgrind] (JENKINS-18950) valgrind-plugin makes jenkins run out of memory under heavy use
Johannes Ohlemacher assigned JENKINS-18950 to Johannes Ohlemacher valgrind-plugin makes jenkins run out of memory under heavy use Change By: Johannes Ohlemacher (30/Jul/13 3:32 PM) Assignee: Marco Miller Johannes Ohlemacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16218) include suppressions from valgrind
Johannes Ohlemacher commented on JENKINS-16218 include suppressions from valgrind version 0.19 took way more time than expected and didn't want to delay it any further, so this feature is not included. Its scheduled for version 0.20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16391) Allow publication even if build failed
Johannes Ohlemacher resolved JENKINS-16391 as Fixed Allow publication even if build failed fixed with version 0.19 added options to publish results for aborted or failed builds Change By: Johannes Ohlemacher (04/Mar/13 11:19 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16216) Valgrind plugin mixes results from forking program
Johannes Ohlemacher resolved JENKINS-16216 as Fixed Valgrind plugin mixes results from forking program fixed with version 0.19. errors are grouped by process errors are identified by process id and error id added support for valgrind options trace-children and child-silent-after-fork plugin adds '%p' to xml report filename automatically Change By: Johannes Ohlemacher (04/Mar/13 11:17 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16864) Error details misses to include the complete command line from the valgrind .xml files
Johannes Ohlemacher resolved JENKINS-16864 as Fixed Error details misses to include the complete command line from the valgrind .xml files fixed with version 0.19 plugin stores pid, ppid and arguments Change By: Johannes Ohlemacher (04/Mar/13 11:18 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Johannes Ohlemacher resolved JENKINS-16123 as Fixed Valgrind plugin does not work when providing multiple Executable Arguments for run. Change By: Johannes Ohlemacher (04/Mar/13 7:32 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Johannes Ohlemacher commented on JENKINS-16123 Valgrind plugin does not work when providing multiple Executable Arguments for run. Fixes with release 0.19 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16999) No delete button to remove valgrind report publisher
Johannes Ohlemacher commented on JENKINS-16999 No delete button to remove valgrind report publisher I am pretty sure there never was such a button, but i will look into it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Johannes Ohlemacher commented on JENKINS-16123 Valgrind plugin does not work when providing multiple Executable Arguments for run. sorry for the delay. The last few weeks were pretty tough and i had absolutely no time for the plugin. The next release will likely contain some major changes, but those changes still need some polishment. I'm going to do that now, so you can expect the new version to be released at end of next week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15138) Add ability to specify valgrind command line options to plugin configuration
Johannes Ohlemacher commented on JENKINS-15138 Add ability to specify valgrind command line options to plugin configuration @Tomasz Thats just a bug, see JENKINS-16123. Its already fixed and will be part of the next release. Unfortunately you have to wait for the release until end of february, sorry This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15138) Add ability to specify valgrind command line options to plugin configuration
Johannes Ohlemacher commented on JENKINS-15138 Add ability to specify valgrind command line options to plugin configuration @Tomasz what do you mean with "executable options"? the executable arguments are command line options passed to the executable under test. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16391) Allow publication even if build failed
Johannes Ohlemacher commented on JENKINS-16391 Allow publication even if build failed i fully agree, its already on my todo list since a couple of weeks I will add a configuration option for the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Johannes Ohlemacher commented on JENKINS-16123 Valgrind plugin does not work when providing multiple Executable Arguments for run. there is no special reason for quoting the argument string, its just a bug I already fixed it and i will release a new version soon! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16123) Valgrind plugin does not work when providing multiple Executable Arguments for run.
Johannes Ohlemacher started work on JENKINS-16123 Valgrind plugin does not work when providing multiple Executable Arguments for run. Change By: Johannes Ohlemacher (15/Jan/13 9:10 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16216) Valgrind plugin mixes results from forking program
Johannes Ohlemacher started work on JENKINS-16216 Valgrind plugin mixes results from forking program Change By: Johannes Ohlemacher (28/Dec/12 10:43 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15287) Null pointer exception from ValgrindPublisher
Johannes Ohlemacher resolved JENKINS-15287 as Fixed Null pointer exception from ValgrindPublisher fixed with version 0.17, sorry for the trouble Change By: Johannes Ohlemacher (24/Sep/12 9:11 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15201) Add support for the track-origins valgrind option
Johannes Ohlemacher resolved JENKINS-15201 as Fixed Add support for the track-origins valgrind option Thanks. I added support for those auxiliary information (and for --track-origin option) with version 0.15. Each element can be followed by a complete stacktrace (with multiple stack frames) and is displayed individually after the regular stacktrace. A summary of the auxiliary information (just the messages, no stacktraces) is shown at the top of the page. Change By: Johannes Ohlemacher (18/Sep/12 8:39 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15173) Valgrind plugin "Valgrind Results" link on project root page does not always link to the most recent build
Johannes Ohlemacher resolved JENKINS-15173 as Fixed Valgrind plugin "Valgrind Results" link on project root page does not always link to the most recent build fixed with version 0.15 "Valgrind Result" links to the most recent build that has valid valgrind results Change By: Johannes Ohlemacher (18/Sep/12 8:32 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15201) Add support for the track-origins valgrind option
Johannes Ohlemacher commented on JENKINS-15201 Add support for the track-origins valgrind option Hi David, i am a bit confused by the two auxwhat elements in your xml output and by the way they are related to each other. Could you post the full xml code of the error? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15201) Add support for the track-origins valgrind option
Johannes Ohlemacher commented on JENKINS-15201 Add support for the track-origins valgrind option thanks for the example, i am working on something This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15138) Add ability to specify valgrind command line options to plugin configuration
Johannes Ohlemacher resolved JENKINS-15138 as Fixed Add ability to specify valgrind command line options to plugin configuration fixed with release 0.12 Change By: Johannes Ohlemacher (13/Sep/12 9:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15139) Add ability to handle command line arguments in valgrind runner
Johannes Ohlemacher resolved JENKINS-15139 as Fixed Add ability to handle command line arguments in valgrind runner fixed with release 0.12 Change By: Johannes Ohlemacher (13/Sep/12 9:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15139) Add ability to handle command line arguments in valgrind runner
Johannes Ohlemacher commented on JENKINS-15139 Add ability to handle command line arguments in valgrind runner adding command line options for the program under test is on my todo list for quite some time, just give me a few more days. thanks for the feedback! btw: the runner prints the call to valgrind to the log (including all valgrind command line options), so if you want to run valgrind by yourself (from your Makefile or whatever) and you miss some meta data, take a look at it! maybe you just missed some options!? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14200) Allow valgrind plugin to select valgrind executable location
Johannes Ohlemacher resolved JENKINS-14200 as Fixed Allow valgrind plugin to select valgrind executable location fixed with version 0.10 Change By: Johannes Ohlemacher (16/Jul/12 12:20 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14200) Allow valgrind plugin to select valgrind executable location
Johannes Ohlemacher reopened JENKINS-14200 Allow valgrind plugin to select valgrind executable location Configured valgrind executable doesn't show up on configuration page Change By: Johannes Ohlemacher (05/Jul/12 2:49 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14199) Valgrind Plugin doesn't expand variables in the working/output directories for parameterized builds
Johannes Ohlemacher
resolved JENKINS-14199 as Fixed
Valgrind Plugin doesn't expand variables in the working/output directories for parameterized builds
should be fixed with version 0.9
use ${varname}
Change By:
Johannes Ohlemacher
(24/Jun/12 5:53 PM)
Status:
Open
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14200) Allow valgrind plugin to select valgrind executable location
Johannes Ohlemacher resolved JENKINS-14200 as Fixed Allow valgrind plugin to select valgrind executable location should be fixed with version 0.9 Change By: Johannes Ohlemacher (24/Jun/12 5:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Ohlemacher resolved JENKINS-13745. --- Resolution: Fixed oops, that should not have happened...shame on me. I released versions 0.7 and 0.8 to address this issue, i tested it with 1.464 and it should finally work now. > Valgrind Plugin: Any Configuration of the "publish valgrind results" part > triggers exception > > > Key: JENKINS-13745 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 > Project: Jenkins > Issue Type: Bug > Components: valgrind >Affects Versions: current > Environment: Ubuntu 12.04 > Jenkins 1.463 >Reporter: Georg Hofmann >Assignee: Johannes Ohlemacher > Labels: exception, plugin > Fix For: current > > Attachments: hudson_valgrind_plugin_excpetion.txt > > > I have tested the Valgrind plugin, but I cannot configure it. > The build configuration part is working find, but when I try to configure the > "publish valgrind results" part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Ohlemacher updated JENKINS-13745: -- Component/s: valgrind (was: plugin) > Valgrind Plugin: Any Configuration of the "publish valgrind results" part > triggers exception > > > Key: JENKINS-13745 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 > Project: Jenkins > Issue Type: Bug > Components: valgrind >Affects Versions: current > Environment: Ubuntu 12.04 > Jenkins 1.463 >Reporter: Georg Hofmann >Assignee: Johannes Ohlemacher > Labels: exception, plugin > Fix For: current > > Attachments: hudson_valgrind_plugin_excpetion.txt > > > I have tested the Valgrind plugin, but I cannot configure it. > The build configuration part is working find, but when I try to configure the > "publish valgrind results" part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Ohlemacher resolved JENKINS-13745. --- Fix Version/s: current Resolution: Fixed instantiate ValgrindPublisher via databound constructor and not via newInstance method from ValgrindPublisherDescriptor > Valgrind Plugin: Any Configuration of the "publish valgrind results" part > triggers exception > > > Key: JENKINS-13745 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 > Project: Jenkins > Issue Type: Bug > Components: plugin >Affects Versions: current > Environment: Ubuntu 12.04 > Jenkins 1.463 >Reporter: Georg Hofmann >Assignee: Johannes Ohlemacher > Labels: exception, plugin > Fix For: current > > Attachments: hudson_valgrind_plugin_excpetion.txt > > > I have tested the Valgrind plugin, but I cannot configure it. > The build configuration part is working find, but when I try to configure the > "publish valgrind results" part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13745) Valgrind Plugin: Any Configuration of the "publish valgrind results" part triggers exception
[ https://issues.jenkins-ci.org/browse/JENKINS-13745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162681#comment-162681 ] Johannes Ohlemacher commented on JENKINS-13745: --- good news: i can reproduce the bug :) It appears only on jenkins 1.463, all older versions seem to work fine (i tested 1.455, 1.460 and 1.462). I am working on it... > Valgrind Plugin: Any Configuration of the "publish valgrind results" part > triggers exception > > > Key: JENKINS-13745 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13745 > Project: Jenkins > Issue Type: Bug > Components: plugin >Affects Versions: current > Environment: Ubuntu 12.04 > Hudson 1.463 >Reporter: Georg Hofmann >Assignee: Johannes Ohlemacher > Labels: exception, plugin > Attachments: hudson_valgrind_plugin_excpetion.txt > > > I have tested the Valgrind plugin, but I cannot configure it. > The build configuration part is working find, but when I try to configure the > "publish valgrind results" part, I get the exception in the attached file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
