Skip to content
This repository has been archived by the owner on Apr 12, 2018. It is now read-only.

Scrutinizer marks inspection as failed because of many changes when this is not the truth? #363

Open
senkal opened this issue Jan 11, 2016 · 0 comments

Comments

@senkal
Copy link

senkal commented Jan 11, 2016

For a while Scrutinizer started to mark some inspections as "failed"
The test part passes fine, the analysis as well, but on Github it says "Failed condition met"
When I go to inspection I see:"Unfortunately, the change set was too large and we could not compute changes, but only the current state."
But the change set for the PR was really small(6 files).

I can understand that sometimes, for over 200 files, it says that.
But it sometimes catches really small change and sets inspection as invalid.

Any way to stop this behaviour?
Is there a way I can tell "if you think the changes are too big, do not mark the inspection as failed"?

@senkal senkal changed the title Scrutinizer mars as failed with "Unfortunately, the changeset was too large and we could not compute changes, but only the current state." Scrutinizer marks as failed with because of many changes when this is not the truth? Jan 11, 2016
@senkal senkal changed the title Scrutinizer marks as failed with because of many changes when this is not the truth? Scrutinizer marks inspection as failed because of many changes when this is not the truth? Jan 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant