Attention packetcable-devs, Autorelease oxygen failed to build packetcable-policy-server from packetcable in build 553. Attached is a snippet of the error message related to the failure that we were a

Attention packetcable-devs, Autorelease oxygen failed to build packetcable-policy-server from packetcable in build 327. Attached is a snippet of the error message related to the failure that we were a

Okay I think this confirms the culprit. I used ncdu on a running build system after only 3 hrs of a carbon build and can confirm it's the pax stuff that's taking all the disk. Here's a small snippet o

Attention packetcable-devs, Autorelease carbon failed to build packetcable-policy-karaf from packetcable in build 559. Attached is a snippet of the error message related to the failure that we were ab

I see we may only be copying the karaf logs and not runtime generated files, while these logs are preserved into `$WORKSPACE/archives` and published into log server. It would be good to remove Pax run

Anil Belur <abelur@...> wrote: I don’t think that would be sufficient. We’d really need to move the Karaf logs out of the way and delete Pax runtime trees during the build. Regards, Stephen

Thanh Ha <thanh.ha@...> wrote: This might be related to https://git.opendaylight.org/gerrit/69529 — we keep Pax Exam runtime trees so we can extract the Karaf logs... Regards, Stephen

Attention packetcable-devs, Autorelease carbon failed to build packetcable-policy-karaf from packetcable in build 552. Attached is a snippet of the error message related to the failure that we were ab

Attention packetcable-devs, Autorelease nitrogen failed to build packetcable-policy-server from packetcable in build 372. Attached is a snippet of the error message related to the failure that we were

Hi – A couple of weeks ago I noticed that the Packetcable CSIT jobs have been failing in Jenkins since October 17 – when all of our CSIT tests began failing. The failure occurs across Carbon, Nitrogen

Hello Kit & ODL teams. My apologies for sending this late but here is the M1 Status readout for the Packetcable Project: Best regards, Kevin Kershaw CableLabs 1. Project PTL: - Steve Pisarski - email:

Hello Oxygen Projects, This is a repeat of last week's reminder. This is a friendly reminder for the 17 projects below to complete their M1 milestone status readout as soon as possible as it is past d

This is a friendly reminder for the projects below to complete their M1 milestone status readout as soon as possible (within a week) as it is past due: aaa, coe, dlux, dluxapps, eman, faas, infrautils

Hello Katie – Here is the Packetcable project M5 status for the Carbon release Best regards, Kevin Kershaw CableLabs --------------------------------------------------------------------------- Packetc

I think there is work under way to get larger VMs and more java mem assigned to these builds which will hopefully help. I've CC'd integration-dev in case those folks can chime in with more details. Th

1. The Packetcable project formally joins the OpenDaylight Carbon Simultaneous Release and agrees to the activities and timeline documented on the Nitrogen Release Plan Page [1]. 2. Project Offset: Of

Mufaddal, I hit the same issue when I build the patch locally. The issue is Karaf exhausts memory trying to resolve dependencies for all features in distribution (including packetcable). Unfortunately

Hello Andrej, I am following this gerrit patch - https://git.opendaylight.org/gerrit/#/c/59800/ and it seems that there is a Jenkins failure. However, this patch builds fine in my machine. Do you have

Hi PACKETCABLE Team, Our analysis indicates that your project has not yet completed the mandatory Nitrogen Karaf 4 Migration Requirements [1] as part of the Nitrogen Simultaneous Release. The TSC rese

Attention packetcable-devs, Autorelease nitrogen failed to build packetcable-driver from packetcable in build 95. Attached is a snippet of the error message related to the failure that we were able to