>> Failed tests: externalAddOffline(org.apache.
jackrabbit.oak.plugins.blob.datastore.BlobIdTrackerTest): expected:<1006>
but was:<1001>
Was added yesterday....taking a look. Will Ignore it meantime.

Thanks
Amit

On Thu, Dec 8, 2016 at 3:16 PM, Julian Reschke <[email protected]>
wrote:

> On 2016-12-07 12:21, Michael Dürig wrote:
>
>>
>> In a F2F discussion we agreed to pay more attention to test failures on
>> the Apache Jenkins instance and make an effort to turn it green:
>>
>> - tests that are constantly failing and also fail on a local checkout
>> should be marked @Ignored along with an issue reference and an bug
>> report in Jira.
>>
>> - tests that only fail on Jenkins should be marked as such through the
>> CIHelpers facility
>>
>> In the meanwhile I tried to configure the Jenkins Jira plugin so it
>> would automatically file Jira issues for failures. This didn't seem to
>> successful as the last failing build didn't show up in the Oak Jira.
>> There is no indications of anything going wrong in the build logs
>> neither though. Anyone who wants to take this up, be my guest.
>>
>> Michael
>>
>
> +1
>
> FWIW; we have way too many tests that happen to fail "sometimes". The
> following just happened twice to me when running integration tests:
>
> Failed tests: 
> externalAddOffline(org.apache.jackrabbit.oak.plugins.blob.datastore.BlobIdTrackerTest):
> expected:<1006> but was:<1001>
>
> Best regards, Julian
>
>

Reply via email to