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 6D28E48A44; Fri, 31 Oct 2025 09:38:49 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 28EDA402ED; Fri, 31 Oct 2025 09:38:49 +0100 (CET) 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 DBA7D402AE for ; Fri, 31 Oct 2025 09:38:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1761899927; 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; bh=j/pl4U/CAnu1lXCAxJ3SPYgH44+PK/i3w7mxFaHMTFA=; b=VAxR0xu9ZLqCkQLyzI3HY7uNimYl0bo3QgVasGr107m4ZxW9lIG14GBUdWCpZ6EJeN91AF 1oDVQaCxTRwJdMmP0lBiK5pHMqmf5lHPXxFoVPoelFvD0ryr3D7qQeC7a1uqRmLA5DkDAl ypCFaWxiNSQ3q+II4xvRF/4Z7Ai/Xds= Received: from mail-lf1-f70.google.com (mail-lf1-f70.google.com [209.85.167.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-360-alpuDoAuOsyipFV8kTPbxw-1; Fri, 31 Oct 2025 04:38:45 -0400 X-MC-Unique: alpuDoAuOsyipFV8kTPbxw-1 X-Mimecast-MFC-AGG-ID: alpuDoAuOsyipFV8kTPbxw_1761899924 Received: by mail-lf1-f70.google.com with SMTP id 2adb3069b0e04-592f576d68eso1357427e87.3 for ; Fri, 31 Oct 2025 01:38:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761899924; x=1762504724; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=j/pl4U/CAnu1lXCAxJ3SPYgH44+PK/i3w7mxFaHMTFA=; b=AdvlKmk6+z52DGfPAL4W1ZETsC5Zjty6TPooz0bGFU87Z49jfzTkfYaoiYdIzeu0Tu EqLBi4aqW3KsvT3Ia9qoWF1xKYlXn+lhYXybhwd7u/V4rz6iQZGI1Du/3q/Q39QS1vHH zAT0kLib0OXrBmOHtl215tMolUhRA8/whtCEvVjP+k6tHJ4XeLu06pVV06VMPq6rnJZs Z4GQs8YaqG9jbrmynL6kJ8fI3Pyrpn6epa2xowcfITk4Sr8ZCssXh/KDn6FjzBUJULyn ktXowlj3gEPGcDKUu1i4hEJDz3nfuw1/erGqQHJK/XEU6KyyiUa8QpYfX4eU9gSdcl1Q BNMQ== X-Gm-Message-State: AOJu0YyRMllf+pXuU5xVoA5k22fUq5eCfEpUtgMKewsQWK87HoM9Tk2c Q/5rMcGpi98X2XCpT3LCm5r3QIJOl6EvCP+PcT8cITXcc5erwv0vVgIbnZrOHqbJamO03cJWBqC 6pBJ/rMraAyJ1+1cL7i7F426TX1NdDsvxjTcV/KQsxsuzFS9/oX9gh+SM/bLqYEudo94XTiX+5J MPCLZqqE2SFQ/7ijfXvw== X-Gm-Gg: ASbGncviAshIoQ7ekAziCfGbTsgm0MU81kcCE/i+iQ0IUpFV33dFV9KkFzyl5bXJHEU 1j2YPKD1Yex8/Fe1n6ZaBeZNMDLB8+KRztoZt8OwWhF/zQ5geCfhokcxGaODYF240OUNCdN/A3v Iqei/S1qphpp/Got9PO3w1PPenQ4eo93zmIkJPxSHycwQ0lbz6kixEYgEEaw== X-Received: by 2002:a05:6512:3195:b0:592:f9c6:973e with SMTP id 2adb3069b0e04-5941d5315ccmr916051e87.33.1761899924225; Fri, 31 Oct 2025 01:38:44 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEYz2S0u4m1AoGd+p9l5gR73NWYpjd34wxugaWH2DMVJ+mkYqnONmBJqb6MF8tsnV5zMWGvf7iufRUCWUdWzHE= X-Received: by 2002:a05:6512:3195:b0:592:f9c6:973e with SMTP id 2adb3069b0e04-5941d5315ccmr916042e87.33.1761899923735; Fri, 31 Oct 2025 01:38:43 -0700 (PDT) MIME-Version: 1.0 From: David Marchand Date: Fri, 31 Oct 2025 09:38:32 +0100 X-Gm-Features: AWmQ_bmFSgrsxUVrNGeZQI-j01evphSCFZEfRclfwTMXE3HLI03fiUpLMQrJsDM Message-ID: Subject: Disable SPDK testing again? To: Patrick Robb , Aaron Conole , dpdk-techboard Cc: ci@dpdk.org, dev X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: -1DDaZ9uCG05VCQ2qXSUhj5c-2WpEBzed8warmbgbAg_1761899924 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" 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 Hello, The SPDK target in UNH lab has been spewing warnings as SPDK build itself compiles and links against a list of libraries and drivers, regardless of the upstream dependencies. https://github.com/spdk/dpdk/commit/74b1a804eda2ed99d1ecaae5b79de7df6d74e8ff and https://github.com/spdk/spdk/blob/master/dpdkbuild/Makefile#L66 Until SPDK fixes this on their side (either adding argparse in their static list, or using pkg-config for example and stopping patching DPDK), linking SPDK binaries fails as the argparse lib now necessary to EAL is not pulled: /usr/bin/ld.bfd: /usr/local/lib/x86_64-linux-gnu/librte_eal.a(eal_common_eal_common_options.c.o): in function `eal_usage': eal_common_options.c:(.text+0x16): undefined reference to `rte_argparse_print_help' /usr/bin/ld.bfd: /usr/local/lib/x86_64-linux-gnu/librte_eal.a(eal_common_eal_common_options.c.o): in function `eal_collate_args': eal_common_options.c:(.text+0x953): undefined reference to `rte_argparse_parse' /usr/bin/ld.bfd: /usr/local/lib/x86_64-linux-gnu/librte_eal.a(eal_common_eal_common_options.c.o): in function `eal_parse_args': eal_common_options.c:(.text+0x343b): undefined reference to `rte_argparse_parse_type' collect2: error: ld returned 1 exit status make[3]: *** [/root/workspace/Generic-DPDK-Compile-Meson/spdk/mk/spdk.app.mk:39: spdk_lock] Error 1 make[2]: *** [/root/workspace/Generic-DPDK-Compile-Meson/spdk/mk/spdk.subdirs.mk:16: lock] Error 2 make[1]: *** [/root/workspace/Generic-DPDK-Compile-Meson/spdk/mk/spdk.subdirs.mk:16: thread] Error 2 While it is just a warning in the CI dashboard, I don't think we should waste resources on this testing. Opinions? -- David Marchand