From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3C69545EC4; Mon, 16 Dec 2024 22:43:37 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 37291402A3; Mon, 16 Dec 2024 22:43:37 +0100 (CET) Received: from mail-pg1-f173.google.com (mail-pg1-f173.google.com [209.85.215.173]) by mails.dpdk.org (Postfix) with ESMTP id 655CB40267 for ; Mon, 16 Dec 2024 22:43:35 +0100 (CET) Received: by mail-pg1-f173.google.com with SMTP id 41be03b00d2f7-7fcfb7db9bfso3157887a12.1 for ; Mon, 16 Dec 2024 13:43:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1734385414; x=1734990214; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=lhlVAGkM7McQRRDFXfx9XUXnzXYARILBUNcco466Pkw=; b=D0s9ij2zkLFyVFEO0Ll3EZ8/dmH2ANlTB8N6uI3eYZUdMQSreu/chFMw5Y8cQB01jU 8ei50KZ6/3mkz3g72RNqtQwmAyh7R43SgAXna24RLMOkvDS3TlvvTXCbR8v4FWZPDgpz gClVgPnJJXGoG/sDJgv93nEMvFlBNFlCMj+vY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734385414; x=1734990214; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=lhlVAGkM7McQRRDFXfx9XUXnzXYARILBUNcco466Pkw=; b=hDp8li62+GbI5uEBt/TFChqE+U3jv98eY+FP35atM+vQaUvKCR93TUaQT8L3Q5QqYZ JN5myM2mQBGh9HjtbPclPpyupefbLuBRqMFOWBpQdYOIr4isFgrtjaQBHzcFp488c9gP wl4lJ5qxO3tdqtYA5v5i1+LlNs8xo+qGPE0QtTp8/49Nv0GC6AG6FmscWkUTBmGX8yVu p28FN+THwlft2KpSVu9m5fW9WKP4RRK5lYGQBoMicVD9QKqKBeXag5uq/ng+abMZAWSh lhv49mhx6y9dTGhNZsU8MGVEu5cTrQyPf6wBgw1LJhTxx4K3c5k+dRjFmFpQjkf6Sstg B22Q== X-Forwarded-Encrypted: i=1; AJvYcCWVVEt6TiHSj2VlWQ5oqWZzJmEEh94YtNZrEh27ye/Pzj9s0qQBEbvCTxCuuko4FtKlkA==@dpdk.org X-Gm-Message-State: AOJu0Yz7TBCUxAT4tnmtaXqCN2BZbB11Ng5leNFao3pLP4ljIoJ56FdD vPLtBxnzIX3pEgiFoPoSr6r2HI+ZW5te9fef1rzVP9Ig5Yka2oxsjmm3UOIUf7Q8mlciUB9ixlY E1aXlnMzGhZBere9v03PJX5GymR24+jvGdgsQMQ== X-Gm-Gg: ASbGncv4uinjN6nIEnVzIg0uUseVlT6SoVoAQwEcM92o/O0RGpdK8iAsuk68wANLsE7 hf+edPJtFUwy5jsxl2OpGmehuLDtivHmqrooE7GF10tdxyPqXQ6pACRY4XP8UpOfoZyKveV0= X-Google-Smtp-Source: AGHT+IEHjPGv+ziEHeBaXnc9GC2Mbhs6OG8bTI6q0T8uqbgGaa6lI04XVcXkSkQFAwtU9u9M8qlZ5z2a0uY0yEPdMcg= X-Received: by 2002:a17:90b:54c7:b0:2ee:d63f:d73 with SMTP id 98e67ed59e1d1-2f28fb666fbmr19745210a91.11.1734385414466; Mon, 16 Dec 2024 13:43:34 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Patrick Robb Date: Mon, 16 Dec 2024 16:41:11 -0500 Message-ID: Subject: Re: Intel CI failing on updated DTS patchset To: "rajesh.t.puttaswamy@intel.com" Cc: Luca Vizzarro , "ci@dpdk.org" , Paul Szczepanek , Thomas Monjalon , Aaron Conole , Bruce Richardson , "Mcnamara, John" , David Marchand Content-Type: multipart/alternative; boundary="000000000000888c3006296a128c" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org --000000000000888c3006296a128c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Rajesh, Do you (or someone at your team) know what the "Document" test from the table in Luca's email is covering? I see from Lijuan's email that in your patch apply process, you are using a command like: git pw series apply 26733 --exclude=3Ddoc/** So I guess we need to decide between disabling the test in your CI, or returning to applying the doc/** files. Perhaps you can join the DPDK CI call on January 7 at 1500 UTC and we can discuss? I'm happy to add this as an agenda item. On Fri, Dec 13, 2024 at 11:15=E2=80=AFAM David Marchand wrote: > On Fri, Dec 13, 2024 at 5:00=E2=80=AFPM Luca Vizzarro > wrote: > > I=E2=80=99ve sent a v2 fixing this patch, but for some reason the CI ha= s failed > again with the same problem, even if it=E2=80=99s been resolved. The line= s > referenced are also no longer there. > > I don't really see the point of reporting doc testing per patch from Inte= l > CI. > > Documentation testing per patch is broken in Intel CI, as doc/ updates > are filtered: > > http://inbox.dpdk.org/dev/CY5PR11MB618735108D3E9D90C67EEF96F5DA9@CY5PR11M= B6187.namprd11.prod.outlook.com/ > > So this report is about testing merged code, but not your changes. > > > -- > David Marchand > > --000000000000888c3006296a128c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Rajesh,

Do you (or someone at your t= eam) know what the "Document" test from the table in Luca's e= mail is covering?

I see from Lijuan's email th= at in your patch apply process, you are using a command like: git pw series apply 26733 --exclude=3Dd= oc/**=C2=A0

So = I guess we need to decide between disabling the test in your CI, or returni= ng to applying the doc/** files.=C2=A0

Perhaps you can join the DPDK CI call on January 7 = at 1500 UTC and we can discuss? I'm happy to add this as an agenda item= .

On Fri, Dec 13, 2024 at 11:15=E2=80=AFA= M David Marchand <david.mar= chand@redhat.com> wrote:
On Fri, Dec 13, 2024 at 5:00=E2=80=AFPM Luca Vizzarro <<= a href=3D"mailto:Luca.Vizzarro@arm.com" target=3D"_blank">Luca.Vizzarro@arm= .com> wrote:
> I=E2=80=99ve sent a v2 fixing this patch, but for some reason the CI h= as failed again with the same problem, even if it=E2=80=99s been resolved. = The lines referenced are also no longer there.

I don't really see the point of reporting doc testing per patch from In= tel CI.

Documentation testing per patch is broken in Intel CI, as doc/ updates
are filtered:
http://inbox.dpdk.org/dev/CY5PR11MB618735108D3E9D90C67EEF96F5DA9@CY5PR= 11MB6187.namprd11.prod.outlook.com/

So this report is about testing merged code, but not your changes.


--
David Marchand

--000000000000888c3006296a128c--