Re: DAO tests failing

--eWbcAUUbgrfSEG1c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 11/24, Lior Vernia wrote: /hudson8811709354471707251.sh created created t-engine_master_dao-unit-tests_created" > >>>> 08:54:55 ERROR: role "engine" already exists t-engine_master_dao-unit-tests_created" t-engine_master_dao-unit-tests_created" does not exist t-engine_master_dao-unit-tests_created" ao_unit_tests_created_6082 al.dbbroker.BatchProcedureExecutionConnectionCallback doInConnection] Can't= execute batch: Batch entry 0 select * from public.insertnumanode(CAST ('83= 0fd8d0-9332-4d81-bb80-54beee7d5b59' AS uuid),CAST (NULL AS uuid),CAST ('772= 96e00-0cad-4e5a-9299-008a7b6f4355' AS uuid),CAST ('0' AS int2),CAST ('0' AS= int8),CAST ('4' AS int2),CAST (NULL AS int8),CAST (NULL AS int4),CAST (NUL= L AS numeric),CAST (NULL AS numeric),CAST (NULL AS numeric),CAST (NULL AS i= nt4),CAST (NULL AS text)) as result was aborted. Call getNextException to = see the cause. al.dbbroker.BatchProcedureExecutionConnectionCallback doInConnection] Can't= execute batch. Next exception is: ERROR: insert or update on table "numa_n= ode" violates foreign key constraint "fk_numa_node_vm" =46rom the gerrit page I see that the patch depended on other 5 patches, 3 of those are already merged. So no, right now I only see two. There's always a possibility, but I think that it's quite improbable in this case. The DB is being constructed as part of the test. The messages Allon pointed out are not errors but just unfiltered messages (it just drops the db directly instead of checking if it exists first for example). I don't see any issues on the db creation. ERROR: insert or update on table "network" violates foreign key constraint "fk_network_qos_id" Detail: Key (qos_id)=3D(de956031-6be2-43d6-bb90-5191c9253318) is not present in table "qos". This failure is quite a specific one, you can try looking for the point where that key should be added. It looks like you are trying to add an entry to the network table with an id from the qos that does not exist. Most of the other failures also seem related to foreign keys not being consistent. That does not seem like an environmental issue. The db did not exist at the start of the test qnd it works well when run from branch HEAD, so it's an issue that's introduced by your patch or any it depends on. Keep in mind that it does a checkout of the change and not a rebase. I see that the first failure (if I'm not mistaken) seems to be: 00:02:38.691 Running org.ovirt.engine.core.dao.VmAndTemplatesGenerationsDao= Test 00:02:39.007 Tests run: 18, Failures: 13, Errors: 1, Skipped: 0, Time elaps= ed: 0.325 sec <<< FAILURE! What might lead to an entry not being created on the db and the other failures. I don't know the code or the tests code, so I don't think I can help you more than that. this --=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 --eWbcAUUbgrfSEG1c Content-Type: application/pgp-signature --eWbcAUUbgrfSEG1c--