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 75FB9438E3; Tue, 16 Jan 2024 18:07:25 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 566F740278; Tue, 16 Jan 2024 18:07:25 +0100 (CET) Received: from mail-pg1-f169.google.com (mail-pg1-f169.google.com [209.85.215.169]) by mails.dpdk.org (Postfix) with ESMTP id 89081400D6 for ; Tue, 16 Jan 2024 18:07:23 +0100 (CET) Received: by mail-pg1-f169.google.com with SMTP id 41be03b00d2f7-53fbf2c42bfso7113947a12.3 for ; Tue, 16 Jan 2024 09:07:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1705424842; x=1706029642; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=0zJWBW2iSKKXY7oLeSV9FFOxdh/Ao/HDtn1+2Xewbkc=; b=bTVXO0ZDQ3QCWa361dyBPKel/N6q1KdyoYV4v7jFDQ6Qiz6TiK165bYuew3XTtmCnO Qt5hRPCdUlrgwP79JSm2jazelmFBZikZuw8H3jHQK44FeJtPHyM3zLPldUrmSjXHLI6Y cj1slAgk5wCGg+QtpAQKtJGQ5Cbh6dxmTY5Gk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705424842; x=1706029642; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=0zJWBW2iSKKXY7oLeSV9FFOxdh/Ao/HDtn1+2Xewbkc=; b=ZUm7MWwxvEQTBTc38DVWT7tGhoR4JGlQ6xe5bDVmGKPjqMKHYXXlRjF8hfwhau8dO8 pDiXgIaP9xoK8zmHBgoJ9b3QuTlP/EmsO1eiQM2MxPcNEMf65s6UDq92bIqKK21ujijW yM7Ndh8qExg7ReV21eprelhogMHt4R6W37d9zZdbJRYbk/v9fEo0l3cA6Z4qK56sUL/X 89FzoVvz7/b2YEqrP8SGmloGqJUIOLhhTPxt3kgDuwVHavAJBxjAPJKgaUzbGDB/8Squ 7i7NqVypqOGCEpt486ONjw4cWusJKOCj5sdOulDJfrVtQ4RjgzItOwlycI6Ap3NYOM1Y tD4w== X-Gm-Message-State: AOJu0YyYTYjYrTj73ahKq99KWh/8FfjLBPktBQut8RHOXl/tokXMB7m6 RNzioP90uf/V2aB6vglqiOTbMp4Glvb6uNJDj1WhxQKFYbWG0A== X-Google-Smtp-Source: AGHT+IF8+iyj+tStWM0xyClSD+G7G8tlMHdjbEC4SsOun74jsvHkLRR/aStyBIO3ccIfxEooGn66nyaiHR1476biqhk= X-Received: by 2002:a17:902:e5ca:b0:1d4:ef61:2407 with SMTP id u10-20020a170902e5ca00b001d4ef612407mr8854669plf.74.1705424842652; Tue, 16 Jan 2024 09:07:22 -0800 (PST) MIME-Version: 1.0 From: Jeremy Spewock Date: Tue, 16 Jan 2024 12:07:11 -0500 Message-ID: Subject: DTS timeouts when compiling DPDK To: dts@dpdk.org, ci@dpdk.org Cc: Patrick Robb , Lincoln Lavoie Content-Type: multipart/alternative; boundary="000000000000f014be060f1329a1" 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 --000000000000f014be060f1329a1 Content-Type: text/plain; charset="UTF-8" Hi all, On the Community Lab test beds I have noticed something interesting about the (old) DTS framework (NOTE: NOT the current dts framework rewrite effort). We have begun seeing intermittent timeouts during the DTS execution (specifically the DPDK compile command) on the DUT, almost exclusively when doing 22.11 LTS testing, but also intermittently on main. I'm not sure what the cause is, but most likely the timeout was set some time ago and additions to DPDK and backporting to LTS releases has gradually increased the compile time over time making the old timeout value insufficient on some slower systems. For context, the current timeout for compiling DPDK is set to be 30 minutes, but we have started to see builds on some systems consistently require a few minutes more than that for the compilation to complete. Does this sound reasonable to you all? The compile timeout is not provided via config file, but is rather hard-coded in /framework/dpdk_project.py. So, for now we have patched the DTS we are running. I am willing to submit a patch to the DTS project making this change, but I know the DTS project is without a maintainer right now. Does anyone know whether (as discussed at the previous DPDK-CI meeting) there will be a final round(s) of patches merged for the old DTS project? Thank you, Jeremy Spewock --000000000000f014be060f1329a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

On the Community Lab test beds I have noticed some= thing=20 interesting about the (old) DTS framework (NOTE: NOT the current dts=20 framework rewrite effort). We have begun seeing intermittent timeouts=20 during the DTS execution (specifically the DPDK compile command) on the DUT= , almost exclusively when doing=20 22.11 LTS testing, but also intermittently on main.

I'm not sur= e what the cause is, but most likely the timeout was set some time ago and a= dditions to DPDK and=20 backporting to LTS releases has gradually increased the compile time=20 over time making the old timeout value insufficient on some slower=20 systems. For context, the current timeout for compiling DPDK is set to be 3= 0 minutes, but we have started to see builds on some systems consistently r= equire a few minutes more than that for the compilation to complete. Does t= his sound reasonable to you all?

The compile timeout is not provided via config file, but is rather hard-coded in=20 /framework/dpdk_project.py. So, for now we have patched the DTS we are=20 running. I am willing to submit a patch to the DTS project making this=20 change, but I know the DTS project is without a maintainer right now.=20 Does anyone know whether (as discussed at the previous DPDK-CI meeting)=20 there will be a final round(s) of patches merged for the old DTS=20 project?

Thank you,
Jeremy Spewock
--000000000000f014be060f1329a1--