Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Travis errors w/o showing an error #2089

Closed
OlegHahm opened this issue Nov 26, 2014 · 7 comments
Closed

Travis errors w/o showing an error #2089

OlegHahm opened this issue Nov 26, 2014 · 7 comments
Assignees
@N8Fear
Labels
Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Milestone
Release 2015.12

Comments

@OlegHahm
Copy link
Member

As can be currently found in https://travis-ci.org/RIOT-OS/RIOT/builds/42150176, the || exit part seems to cause Travis sometimes to exit, before it prints the actual error message.
@OlegHahm OlegHahm added this to the Release 2014.12 milestone Nov 26, 2014
@OlegHahm OlegHahm mentioned this issue Nov 26, 2014
Merged
@LudwigKnuepfer
Copy link
Member

Maybe there just is no output - cppcheck didn't show any errors in https://travis-ci.org/RIOT-OS/RIOT/builds/41835828 either and I think it also did not print errors when running locally (without exit) but still had a non-zero exit code.

@LudwigKnuepfer LudwigKnuepfer assigned N8Fear and unassigned Kijewski Nov 26, 2014
@OlegHahm
Copy link
Member Author

I tried yesterday night by running exactly the same commands from the travis configuration on my local machine and got the two warnings mentioned in #1767.

@LudwigKnuepfer
Copy link
Member

The behavior could also depend on the particular version of cppcheck.

@N8Fear
Copy link

N8Fear commented Nov 26, 2014 

 ./dist/tools/cppcheck/check.sh master --diff-filter=AC || echo $?
2

But why? I must admit that I don't really get it...
Looks like cppcheck suppresses the output of the unusedStructMember stuff right now, but still causes an error like exit status. Investigating further...

@OlegHahm
Copy link
Member Author

If I remove the -j 8 from the cppcheck parameters, it returns with 0.

N8Fear pushed a commit to N8Fear/RIOT that referenced this issue Nov 27, 2014
dist: run cppcheck with only one job (triage RIOT-OS#2089)
c1b61b1
N8Fear pushed a commit to N8Fear/RIOT that referenced this issue Nov 27, 2014
dist: run cppcheck with only one job (triage RIOT-OS#2089)
ed9834c
@N8Fear N8Fear mentioned this issue Nov 27, 2014
Merged
@N8Fear
Copy link

N8Fear commented Nov 27, 2014

This is the upstream bug for it: http://trac.cppcheck.net/ticket/4768
Since it's open about 1 1/2 years I guess I need to dig into the cppcheck code or else the chances of getting this fixed soon is minimal.. .:-/

OlegHahm added a commit that referenced this issue Nov 27, 2014
@OlegHahm
Merge pull request #2101 from N8Fear/cppcheck-triage
bd74f3a 
dist: run cppcheck with only one job (triage #2089)
@OlegHahm OlegHahm added Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) and removed Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation labels Dec 2, 2014
@OlegHahm OlegHahm modified the milestones: Release 2014.12, Release NEXT MAJOR Jan 6, 2015
@OlegHahm
Copy link
Member Author

OlegHahm commented Dec 2, 2015

Haven't seen this for a long time.

@OlegHahm OlegHahm closed this as completed Dec 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@N8Fear N8Fear

Labels
Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors)
Projects
None yet
Milestone
Release 2015.12
Development

No branches or pull requests
4 participants
@Kijewski @N8Fear @OlegHahm @LudwigKnuepfer