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 AA80043085; Wed, 16 Aug 2023 21:26:40 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A5662410E3; Wed, 16 Aug 2023 21:26:40 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 62DCB40DDA for ; Wed, 16 Aug 2023 21:26:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1692213998; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ck1ga9GuH6EDHT3HPPbFyD5Li7d1vcqeo7ogPiR8S5A=; b=KWj3shmcjLy6urNSANrk6KZfkWXtodexPBJtCrXhUqse1YZJ2r8Cs4/zfrdXmxe3cvpelE pHjOmPlqSBAl4uogX9zo4F/RJyrhaRUwrrPr10qZAAE/Go+s4ssHc3OiTPOQdEeCVqZvyB 55Ew+61RZw8CWz4HGqf1FSEKPTWG0aU= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-642-mCR89fZAP62ydK4G1wkXEg-1; Wed, 16 Aug 2023 15:26:37 -0400 X-MC-Unique: mCR89fZAP62ydK4G1wkXEg-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2b710c5677eso70796941fa.0 for ; Wed, 16 Aug 2023 12:26:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692213996; x=1692818796; h=content-transfer-encoding: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=ck1ga9GuH6EDHT3HPPbFyD5Li7d1vcqeo7ogPiR8S5A=; b=Ms03qolWScDGnKTqHTCO7CuSkhLjwvRuEX7peRbfGkFhBRXU9Xa9eUZcfEPFRE7Hrq z35CXSAzZ/xmESdefCtOsIhLHc0x598cGOionChP8kIHvEBD4KnfJmVy7yWbGoUQegyb 6P31H+AGXC0a0IMnIY6oFJqN6O3/8zWU8zAI5EvwAG1/FwJl5Pu8BZMyvWvJKRmDoy9z BTBcLb57iQscVMEj7IJ0UGLLvHtSFExMPvin74gKGFi3Bq3zPo/3Eyu87dddSCbS194e /Z/j6g4sN5pVhgLx+khtLn4APRkeLjlFEra9AOxBIMQv187p5pkVzbdVvjX/8GYONVJK daBQ== X-Gm-Message-State: AOJu0Ywvxy4JqOAKEUzcJQBNNA/cIf45ysBYD3khyTK9Ex+mS/ofRuz9 sdDjUhy9k+U1+2xU2+iTDGDNm76Zk+ig2GMebzpbnwNjJjEtduODKCjtiwN8WfWQdRBdmxmo/go W3C8U1zRRggPj5k7JEw== X-Received: by 2002:a05:6512:1590:b0:4fd:d7ac:2654 with SMTP id bp16-20020a056512159000b004fdd7ac2654mr3009618lfb.13.1692213996010; Wed, 16 Aug 2023 12:26:36 -0700 (PDT) X-Google-Smtp-Source: AGHT+IH8QaD+KxUyW9a5lgWGpHFPZzaSfsgAp/0dpV4gOt8mJZb58xIBVBr2JIEuWRv2Je29fq3FeA7e7qzfWWgPxQM= X-Received: by 2002:a05:6512:1590:b0:4fd:d7ac:2654 with SMTP id bp16-20020a056512159000b004fdd7ac2654mr3009602lfb.13.1692213995684; Wed, 16 Aug 2023 12:26:35 -0700 (PDT) MIME-Version: 1.0 References: <20230721115125.55137-1-bruce.richardson@intel.com> <20230815151053.996469-1-bruce.richardson@intel.com> <20230815151053.996469-5-bruce.richardson@intel.com> In-Reply-To: From: David Marchand Date: Wed, 16 Aug 2023 21:26:23 +0200 Message-ID: Subject: Re: [PATCH v5 04/10] app/test: build using per-file dependency matrix To: Patrick Robb Cc: Bruce Richardson , dev@dpdk.org, ci@dpdk.org, =?UTF-8?Q?Morten_Br=C3=B8rup?= , Honnappa Nagarahalli , "Ruifeng Wang (Arm Technology China)" , Thomas Monjalon , Aaron Conole X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Wed, Aug 16, 2023 at 8:30=E2=80=AFPM Patrick Robb wr= ote: > On Wed, Aug 16, 2023 at 10:40=E2=80=AFAM David Marchand wrote: >> >> Patrick, Bruce, >> >> If it was reported, I either missed it or forgot about it, sorry. >> Can you (re)share the context? >> >> >> > >> > Does the test suite pass if the mlx5 driver is disabled in the build? = That >> > could confirm or refute the suspicion of where the issue is, and also >> > provide a temporary workaround while this set is merged (possibly incl= uding >> > support for disabling specific tests, as I suggested in my other email= ). >> >> Or disabling the driver as Bruce proposes. > > Okay, we ran the test with the mlx5 driver disabled, and it still fails.= So, this might be more of an ARM architecture issue. Ruifeng, are you stil= l seeing this on your test bed? > > @David you didn't miss anything, we had a unicast with ARM when setting u= p the new arm container runners for unit testing a few months back. Ruifeng= also noticed the same issue and speculated about mlx5 memory leaks. He rai= sed the possibility of disabling the mlx5 driver too, but that option isn't= great since we want to have a uniform build process (as much as possible) = for our unit testing. Anyways, now we know that that isn't relevant. I'll f= orward the thread to you in any case - let me know if you have any ideas. The mention of "memtest1" in the mails rings a bell. I will need more detailed logs, or ideally an env where it is reproduced. One thing bothers me.. why are we not seeing this failure with ARM for Bruce v6 series? Just looking at patchwork, I would think that I can merge Bruce series as i= s. https://patchwork.dpdk.org/project/dpdk/patch/20230816153439.551501-12-bruc= e.richardson@intel.com/ --=20 David Marchand