sounds good to me. I didn't realize it was just an UT change.

I think Luis has one more job to mark OKAY and we can actually
release SR4.

JamO

On 12/10/18 8:48 AM, Daniel Farrell wrote:
I don't think we need a re-spin, since it's just a unit test change.

I'm not super sure it made sense to merge this, since we're about to disable Oxygen jobs, but it also shouldn't be a big problem.

Thanks,
Daniel

On Mon, Dec 10, 2018 at 5:12 PM Jamo Luhrsen <jluhr...@gmail.com 
<mailto:jluhr...@gmail.com>> wrote:

    wait, we merged a new oxygen patch and are doing a re-spin? I thought we
    only did that for release blockers?

    that means we'll have to get everyone to sign off on the csit results again.

    JamO

    On 12/10/18 4:14 AM, Sam Hague wrote:
     > CSIT won't verify this, it is a change to UT code for an intermittent 
failure. If the build passes I think we are
    fine.
     >
     > On Mon, Dec 10, 2018, 4:38 AM Anil Belur <abe...@linuxfoundation.org 
<mailto:abe...@linuxfoundation.org>
    <mailto:abe...@linuxfoundation.org <mailto:abe...@linuxfoundation.org>> 
wrote:
     >
     >
     >     On Mon, Dec 10, 2018 at 5:11 PM Aswin Suryanarayanan <asury...@redhat.com 
<mailto:asury...@redhat.com>
    <mailto:asury...@redhat.com <mailto:asury...@redhat.com>>> wrote:
     >
     >
     >
     >         On Sat, Dec 8, 2018 at 9:00 PM Jamo Luhrsen <jluhr...@gmail.com 
<mailto:jluhr...@gmail.com>
    <mailto:jluhr...@gmail.com <mailto:jluhr...@gmail.com>>> wrote:
     >
     >
     >
     >             On 12/8/18 3:19 AM, Ariel Adam wrote:
     >              > Hi everyone.
     >              > So our current situation is somewhat challenging with 
releasing Oxygen SR4 #509.
     >              >
     >              > On the one hand we have a number of pending and blocking 
jobs:
     >              >
     >              >   * *COE* (pending) - */Prem/*, please take a look
     >              >   * *Controller* (pending) - */Tom/*, please take a look
     >              >   * *Groupbasedpolicy* (pending) - */Michal/*, please 
take a look
     >              >   * *Netvirt* (blocking) - */Jamo/Sam/*, do we know why 
the failures happened?
     >              >   * *sfc* (blocking) - */Jamo/Brady/*, do we know what 
the failure happened?
     >
     >             Makes sure you check the notes column too. I try to keep 
that up to date with
     >             the jobs I'm investigating. At this point, I think I've been 
able to sign off
     >             on all that I was tracking. There was tons of infra and 3rd 
party software
     >             troubles recently that caused a lot of aborts and failures. 
We've been having
     >             to re-run and fix things as we found them.
     >
     >              >
     >              > On the other hand builds #511 and #512 failed each due to 
different reasons:
     >              >
     >              >   * Build #511 due to a possible environment issues 
(*Anil/Thanh* to comment)
     >
     >             yeah, looks like it to me too:
     >
     >             
(https://nexus.opendaylight.org/content/repositories/public/): GET request of:
     >             
org/hibernate/hibernate-core/5.2.6.Final/hibernate-core-5.2.6.Final.jar from 
opendaylight-mirror failed:
     >             Premature end
     >             of Content-Length delimited message body (expected: 6550533; 
received: 192424 -> [Help 1]
     >
     >
     >              >   * Build #512 due to a problem in Netvirt (*Jamo/Sam* to 
comment)
     >
     >             sorry, not sure on this one. Adding Aswin
     >
     >         Adding Kiran,
     >
     >         As Kiran pointed out in different thread there is an issue in 
aclservice tests which should be fixed by
    [0]. But
     >         it is not yet merged.
     >
     >         [0] : https://git.opendaylight.org/gerrit/#/c/78412/
     >
     >
     >
     >     The change is merged, however I don't see this marked as a blocker 
on the tracking sheet.
     >     Do we need to re-trigger AR or can we just run the CSIT job to 
condirm the fix? Please advice.
     >
     >     Thanks,
     >     Anil
     >
     >
    _______________________________________________
    release mailing list
    rele...@lists.opendaylight.org <mailto:rele...@lists.opendaylight.org>
    https://lists.opendaylight.org/mailman/listinfo/release

_______________________________________________
sfc-dev mailing list
sfc-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/sfc-dev

Reply via email to