Re: [ovirt-devel] [ OST Failure Report ] [ ovirt-engine-4.1 ] [ 02.03.2017 ] [004_basic_sanity]

On Sun, Mar 19, 2017 at 10:33 AM, Eyal Edri <eedri(a)redhat.com&gt; wrote: Let me explain what happened: 1. check-patch jobs used to run on latest 'tested' repo, but that repo is very big as it contains history of all the builds done for a release [1] 2. recently we found a bug that caused OST to fail due to out of memory because it tried to sync the entire tested repo into memory ( that's how OST works ), so the tested repo was removed from check-patch. 3. This means that now check-patch is only using the repos in the reposync file, which for 4.1 is latest released. 4. vdsm-jsonrpc-java 1.3.9 wasn't released in any official oVirt 4.1 release, this is why the job used 1.3.8 which is the latest released. 5. We also don't want to replace the default repos for OST on 4.1 to something other than released, because the basic suite per release should always check against official release [2] 6. As a side note - manual jobs also support running on latest tested, so this issue is solely restricted to 'check-patch' jobs. We do however believe that running check-patch on latest code is important, so we'll look into providing an alternate solution that won't break any of the above restrictions, Suggestions are welcome of course. [1] It is done so anyone that wants to check oVirt can do it w/o worrying that a pkg will be removed during testing ( something that was happening when used experimental lastest.tested repo ) [2] As opposed to experimental flows which DO check against latest code, which is why 4.1 experimental didn't fail on this issue, as it used 1.3.9 -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)