Hi Kazu, This seems to be related to recent Let's Encrypt changes. Please see my comments on the issue. https://gitlab.com/cip-project/cip-core/deby/-/issues/15 Best regards, Hiraku Toyooka <kazuhiro3

Hi! I think functional testing for wireless drivers in CI system is hard, so building and probing seem reasonable tests currently. zynqmp-zcu102 which is connected to CIP LAVA doesn't have the wl18xx

Hi! I finally finished physical location change of the lab and zcu102-01 is online now. Thank you very much for getting the testing done before going offline. And I'm sorry for the delay in the restar

Hi. The lab-cip-cybertrust will be temporarily offline on June 25th due to physical location change. I'm sorry for the inconvenience. The schedule is as follows: June 24th (Thu.) 10:00- (UTC) - zcu102

Hi, After staring at the logs, I noticed that duplicate MAC addresses were used on the two zynqmp-zcu102. I believe this is the cause of the intermittent TFTP termination problem. So I made those mach

Hi, I found that the TFTP transfer of the kernel was terminated in all failure cases. So this is at least not a kernel failure. For example, https://lava.ciplatform.org/scheduler/job/191862 TFTP from

Hello Pavel-san, I'm sorry to give you trouble. It looks "Infrastructure error" and happens intermittently even in 5.10. I will investigate the cause. Failure case: https://lava.ciplatform.org/schedul

Hello Chris, I'm creating Cybertrust's own LAVA lab discussed at [1] to integrate zcu102 board to CIP kernel testing pipeline, while referring to [2]. At this time, health check for the zcu102 board i

Hi, Oh, I missed the sentence. Thank you very much for telling it. Is the backporting limited to the supported hardware? Best regards, Hiraku Toyooka 2019年7月11日(木) 8:47 <nobuhiro1.iwamatsu@....

Hello, I have a question about CIP kernel maintenance policy. Can CIP kernel accept backport patches for new hardware support (not only fixes)? I read the following document and it seems to describe o