Skip to content

Conversation

@jmecosta
Copy link
Member

@jmecosta jmecosta commented Oct 22, 2016

finish #758

@guwirth
Copy link
Collaborator

guwirth commented Oct 24, 2016

@jmecosta checks failing

@jmecosta
Copy link
Member Author

One of the import reports it test is failing g. I will check tonight

@jmecosta jmecosta force-pushed the bugfix/handle-invalid-issues branch from cc32c0c to b90c121 Compare October 25, 2016 14:48
@jmecosta
Copy link
Member Author

@guwirth test should be fixed now, however the builds are not running? do you know anything about it

@jmecosta
Copy link
Member Author

took a bit of time, but its building

@guwirth
Copy link
Collaborator

guwirth commented Oct 31, 2016

Hi @jmecosta, except this

 .*WARN.*The report '.*' seems to be empty, ignoring.
.*ERROR.*The report '.*' seems to be empty.

it looks good to me. Thx for providing this.

Regards,

Copy link
Collaborator

@guwirth guwirth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmecosta other possibility could be to create always only a warning because ValidateRecovery is creating an error ERROR_RECOVERY_KEY == "False".

violationsCount - prevViolationsCount);
} catch (EmptyReportException e) {
LOG.warn("The report '{}' seems to be empty, ignoring.", report);
LOG.error("The report '{}' seems to be empty.", report);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmecosta not sure if this error message is right? For my understanding:

  • in case of CxxPlugin.ERROR_RECOVERY_KEY == "True" this is a warning only?
  • in case of CxxPlugin.ERROR_RECOVERY_KEY == "False" this is an error?

@jmecosta
Copy link
Member Author

jmecosta commented Nov 1, 2016

Yep I will revert that, just seem logic at that time.

On Tue, 1 Nov 2016 20:32 Günter Wirth, notifications@github.com wrote:

@guwirth requested changes on this pull request.

@jmecosta https://github.com/jmecosta other possibility could be to
create always only a warning because ValidateRecovery is creating an error

ERROR_RECOVERY_KEY == "False".

In
sonar-cxx-plugin/src/main/java/org/sonar/plugins/cxx/utils/CxxReportSensor.java
#985 (review)
:

@@ -84,7 +84,8 @@ public void execute(SensorContext context) {
LOG.debug("{} processed = {}", metric == null ? "Issues" : metric.getName(),
violationsCount - prevViolationsCount);
} catch (EmptyReportException e) {

  •      LOG.warn("The report '{}' seems to be empty, ignoring.", report);
    
  •      LOG.error("The report '{}' seems to be empty.", report);
    

@jmecosta https://github.com/jmecosta not sure if this error message is
right? For my understanding:

  • in case of CxxPlugin.ERROR_RECOVERY_KEY == "True" this is a warning
    only?
  • in case of CxxPlugin.ERROR_RECOVERY_KEY == "False" this is an error?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#985 (review),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_jyLBH2CZu118qWu2qOW2EXpGvJ1lIks5q54W-gaJpZM4Kd0NI
.

@jmecosta
Copy link
Member Author

jmecosta commented Nov 5, 2016

@guwirth should be ok now

@guwirth guwirth merged commit b1e0841 into SonarOpenCommunity:master Nov 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants