2015-09-30 3:16 GMT+02:00 Ben Coman <btc@openinworld.com>:
Of the eight issues currently "Resolved (Fix Reviewed By monkey)"
which passed validation successfully, three seem to actually be failures.
That is, Fogbugz shows SUCCESS when the validation report shows FAILURE.

* 16577 Random should be in its own package
* 16634 Rename layout to classLayout (step 2 use new accessors in the tests)
* 16645 RBParser should not accept # <whitespace> and # <number>

So...

Am I misinterpreting the validation reports?

Until this is resolved, should we require validation reports be
manually checked (with a comment on the Issue) before integration?

Could futher occurances be reported in a similar way to those already on...
https://pharo.fogbugz.com/default.asp?16666

* Scrape the Fogbugz comment to the top of a text file.
* Scrape the Validation Report into the text file.
* Extract significant text into a Fogbugz comment in 16666.
* Attach text file to comment.

cheers -ben



Oh, that is bad.
Yes, we should check the validation report manually and comment.
We can reactivate the issue, resolve again and comment if the validation succeed for real.

And redo this after every automatic validation until the cause is found (or don't integrate anything?)