Reading validation reports

At the moment, most of the isues I provide a slice for time out in
validation. What is exactly tested in the validation process? Sometimes
nothing is visible in the report, sometimes there are lots of
deprecation warnings and other problems that look unrelated to the
slice. When should they be ignored?

Stephan

> On 22 Oct 2015, at 19:45, Stephan Eggermont <[hidden email]> wrote:
>
> At the moment, most of the isues I provide a slice for time out in validation. What is exactly tested in the validation process?

It runs twice the tests (first to get false positives) and some Lint rules.

> Sometimes nothing is visible in the report, sometimes there are lots of deprecation warnings and other problems that look unrelated to the slice. When should they be ignored?
>

Yes, this started last week and honestly I have not even a clue what is happening. To me it looks that it might even be caused by the underlying virtual linux machines?

The deprecated we should fix…

        Marcus

On Fri, Oct 23, 2015 at 2:32 PM, Marcus Denker <[hidden email]> wrote:
>
>> On 22 Oct 2015, at 19:45, Stephan Eggermont <[hidden email]> wrote:
>>
>> At the moment, most of the isues I provide a slice for time out in validation. What is exactly tested in the validation process?
>
> It runs twice the tests (first to get false positives) and some Lint rules.

btw, I always wondered, whether the first run of tests to record
existing errors could be done as the last step of creating the
validation image, then it would not need to be run each time.  Maybe
that might cause problems running the validation image on different
platforms?
cheers -ben

On 23/10/15 16:17, Ben Coman wrote:
> On Fri, Oct 23, 2015 at 2:32 PM, Marcus Denker <[hidden email]> wrote:
>> It runs twice the tests (first to get false positives) and some Lint rules.
>
> btw, I always wondered, whether the first run of tests to record
> existing errors could be done as the last step of creating the
> validation image, then it would not need to be run each time.  Maybe
> that might cause problems running the validation image on different
> platforms?

Running it once on all platforms would solve that (and show platform
differences)

Stephan