[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte commented on JENKINS-49495 Re: False positive for LLVM/Clang We updated the plugin and it is working correctly now - sorry for the false alarm, I thought our plugin version would be up-to-date 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-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte closed an issue as Fixed Jenkins / JENKINS-49495 False positive for LLVM/Clang Change By: Steffen Kötte 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-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte created an issue Jenkins / JENKINS-49495 False positive for LLVM/Clang Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-02-12 02:01 Environment: Jenkins 2.46.2 Priority: Minor Reporter: Steffen Kötte 01 Copying the source file '2018-02-12 01' from the workspace to the build folder '25bd.tmp' on the Jenkins master failed. 02 Seems that the path is relative, however an absolute path is required when copying the sources. 03 Is the file '2018-02-12 01' contained more than once in your workspace? 04 Is the file '2018-02-12 01' a valid filename? 05 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/2018-02-12 01' 06 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/2018-02-12 01' Follow up for https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin?focusedCommentId=138446333&refresh=1515495766539#app-switcher The part of the log which is producing the issue is this:
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Madhava Kulkarni commented on JENKINS-49495 Re: False positive for LLVM/Clang Warning Plugin version is: 4.52 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-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte updated an issue Jenkins / JENKINS-49495 False positive for LLVM/Clang Change By: Steffen Kötte |{{{color:#808080}01{color} {color:#00}Copying the source file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' f{color}{color:#00}rom the workspace to the build folder {color}{color:#ff6100}'25{color}{color:#99}{color}{color:#00}bd.tmp{color}{color:#ff6100}' o{color}{color:#00}n the Jenkins master failed.{color}}} {{{color:#808080}02{color} {color:#00}Seems that the path is relative, however an absolute path is required when copying the sources.{color}}} {{{color:#808080}03{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' c{color}{color:#00}ontained more than once in your workspace?{color}}} {{{color:#808080}04{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' a {color}{color:#00}valid filename?{color}}} {{{color:#808080}05{color} {color:#00}If you are building on a slave: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}} {{{color:#808080}06{color} {color:#00}If you are building on the master: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/workspace/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}}| Follow up for [https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin?focusedCommentId=138446333&refresh=1515495766539#app-switcher] The part of the log which is producing the issue is this:{noformat}Test Case '-[AuthenticationTests test_mockError]' started.2018-02-12 01:40:47.179785+0100 App[94246:19282931] ERROR: Error Domain=mockError Code=12345 "(null)" (-[ServerConnection getInitialSessionWithToken:success:error:handleResponse:tryCount:]_block_invoke in ServerConnection.m:911)Test Case '-[AuthenticationTests test_mockError]' passed (0.004 seconds).{noformat}This is printed during our test run, where we in debug mode print the function with {code:java}__PRETTY_FUNCTION__{code}As soon as the the function has something named `error:` it generates a
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte updated an issue Jenkins / JENKINS-49495 False positive for LLVM/Clang Change By: Steffen Kötte |{{{color:#808080}01{color} {color:#00}Copying the source file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' f{color}{color:#00}rom the workspace to the build folder {color}{color:#ff6100}'25{color}{color:#99}{color}{color:#00}bd.tmp{color}{color:#ff6100}' o{color}{color:#00}n the Jenkins master failed.{color}}}{{{color:#808080}02{color} {color:#00}Seems that the path is relative, however an absolute path is required when copying the sources.{color}}}{{{color:#808080}03{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' c{color}{color:#00}ontained more than once in your workspace?{color}}}{{{color:#808080}04{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' a {color}{color:#00}valid filename?{color}}}{{{color:#808080}05{color} {color:#00}If you are building on a slave: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}}{{{color:#808080}06{color} {color:#00}If you are building on the master: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/workspace/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}}| Follow up for [https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin?focusedCommentId=138446333&refresh=1515495766539#app-switcher] The part of the log which is producing the issue is this:{noformat}Test Case '-[AuthenticationTests test_mockError]' started.2018-02-12 01:40:47.179785+0100 App[94246:19282931] ERROR: Error Domain=mockError Code=12345 "(null)" (-[ServerConnection getInitialSessionWithToken:success:error:handleResponse:tryCount:]_block_invoke in ServerConnection.m:911)Test Case '-[AuthenticationTests test_mockError]' passed (0.004 seconds).{noformat}This is printed during our test run, where we in debug mode print the function with {code:java}__PRETTY_FUNCTION__{code}As soon as the the function has something named `error:` it generates a false