Menu ▾ ▴

#604 UNSTABLE?

Future
fixed
nobody
None
5
2016-03-22
2014-10-20
Ray Andrews
No

'make check' gives me this:

Processing c.test
UNSTABLE: 00012
UNSTABLE: 00617
UNSTABLE: 02100
UNSTABLE: 02102
UNSTABLE: 02501
Processing cpp.test
Processing d.test
Processing java.test
Processing pawn.test
Processing objective-c.test
UNSTABLE: 50007
Processing vala.test
Processing ecma.test
Passed 425 / 425 tests
All tests passed, but some files were unstable
PASS: run_tests.sh
=============

It doesn't sound good. What should I do?

Thanks for uncrustify!

Discussion

  • Ben Gardner

    Ben Gardner - 2014-11-13

    That's normal due to the way uncrustify handles comments.

    Unstable means that the second run through uncrustify with the same config produced additional changes. That's not optimal, but isn't really a hard failure. I labeled it as UNSTABLE instead of PASS so as to not forget about the issue.

    There should be an addition check to see if a third pass made even more changes. That should be a failure. Never got around to adding that.

     

  • Guy Maurel

    Guy Maurel - 2016-03-22
    • status: open --> fixed