After having disabled the testing code which cause bug #1163400 the next failure is the following: Running org.ovirt.engine.core.notifier.filter.FirstMatchSimpleFilterTest Tests run: 11, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.041 sec <<< FAILURE! Running org.ovirt.engine.core.config.EngineConfigValidatorTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.168 sec Running org.ovirt.engine.core.config.EngineConfigCLIParserTest Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running org.ovirt.engine.core.config.entity.helper.FenceConfigValueHelperTest Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running org.ovirt.engine.core.config.entity.helper.MacAddressPoolRangesValueHelperTest Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec Running org.ovirt.engine.core.config.entity.helper.MtuValueHelperTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Results : Failed tests: testFilter(org.ovirt.engine.core.notifier.filter.FirstMatchSimpleFilterTest): expected:<alon[.barlev@gmail].com> but was:<alon[bl@redhat].com> 100% reproducible on F21.
Gil Klein 2014-12-07 03:59:05 EST Severity: unspecified → high I am curios, how come an issue in jdk8 and effecting only unit test is set to severity high?
Right, will keep this one as low
this ovirt bug was fixed during 3.5.1 cycle and is included in the build, and therefore should be verified.
I am not sure that QA can verify this because we work with RPMs and we don't run R&D unit tests in any way. Sandro, can you please assign QA Contact to a development person who can run the unit tests and thus verify this bug?
I'll verify it as reporter of the bug.
Verified with sources from ovirt-engine-3.5.2_rc1 tag.
This is an automated message. oVirt 3.5.4 has been released on September 3rd 2015 and should include the fix for this BZ. Moving to closed current release.