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 58A0FA0544; Mon, 10 Oct 2022 09:48:25 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0CEB741141; Mon, 10 Oct 2022 09:48:25 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 9AD1040146 for ; Mon, 10 Oct 2022 09:48:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665388103; 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: in-reply-to:in-reply-to:references:references; bh=oVBg3VXhgCFX4syRiyOXI0dhG7YJfjBmWOPm3G3yJuM=; b=NsmH8LDgaoiuyMssVrRdM6fMjEUY3aJkfoptPfVrleQWuXCApXq5zkrC/B0F3K/bCNnDIN Gnk5Ziob2NRHQpBRV7GNqo6R6OqYM3SrIJ9fvc9odHGs2nJSv/qDAscdRLX1deHb2IwrkK WmJbkMicvcgBWa5PAJEV+SZCdLDnLGQ= Received: from mail-pj1-f72.google.com (mail-pj1-f72.google.com [209.85.216.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-259-ez8_lbYpPbmijx92PznINA-1; Mon, 10 Oct 2022 03:48:21 -0400 X-MC-Unique: ez8_lbYpPbmijx92PznINA-1 Received: by mail-pj1-f72.google.com with SMTP id nl8-20020a17090b384800b00205f930565cso4721271pjb.2 for ; Mon, 10 Oct 2022 00:48:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=oVBg3VXhgCFX4syRiyOXI0dhG7YJfjBmWOPm3G3yJuM=; b=5zxbLWIzUYKXvDbehPPeeArRF+uRbZDbP+aJjFlxK33LgZNHWS3/ND49x1IBeU7w5j MkyJQRFcyQA/+yNDwU4CysNdz4QFzBlX+xFf9Z5hhonmdYPuDig6ofz/anz/WY5DzLBs 9VPU2jHx+972atTF/Jy+hrwtWP+H5975Ygc9F9myzdcsIeXDCxijjaRsAecTNnei0p1m WghhMiTG6m0taqOvAxZGifTwkZ/Iflhx4YOwnqA5rusjcBhKu4VXjG6AZRREQDbHp6tD MIzcI8WtD5RENJZAB7DKfU1IpkayMzliQpHW0UPZXZoo+gud9HLcy/wZlGWA+6a2nZtK F+YQ== X-Gm-Message-State: ACrzQf1FS79cyvhatzyqnB/4Kye31k8FwiJteo2R5L29voO2wpBPeUqU 2zRBfFFKS1pPfcZo9o+CKNVhXFQBZvYbVdM/6C1gI+jwEC+MCHO/loLi9W6U0gUd79mSG+gvKuf h4eoLIDlh+xUpXR+B4Es= X-Received: by 2002:a63:5b58:0:b0:452:2ba4:f86b with SMTP id l24-20020a635b58000000b004522ba4f86bmr15228736pgm.223.1665388100849; Mon, 10 Oct 2022 00:48:20 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5KpTp43JedQto+tH/Mfohd703I7vxw1egExQLczsLAIt429CKF/NGk+nzOEN/3cqmgJT8xStNmwS1VDkZ8x6A= X-Received: by 2002:a63:5b58:0:b0:452:2ba4:f86b with SMTP id l24-20020a635b58000000b004522ba4f86bmr15228722pgm.223.1665388100565; Mon, 10 Oct 2022 00:48:20 -0700 (PDT) MIME-Version: 1.0 References: <20220912170747.3128065-1-bruce.richardson@intel.com> <20221007162404.1117056-1-bruce.richardson@intel.com> In-Reply-To: From: David Marchand Date: Mon, 10 Oct 2022 09:48:09 +0200 Message-ID: Subject: Re: [PATCH v2] build: increase minimum meson version to 0.53.2 To: "Tu, Lijuan" Cc: "Richardson, Bruce" , Thomas Monjalon , "dev@dpdk.org" , "ci@dpdk.org" , Lincoln Lavoie , "Chen, Zhaoyan" , "Mcnamara, John" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Mon, Oct 10, 2022 at 7:23 AM Tu, Lijuan wrote: > > It seems the "intel-Testing" test is in ... berserk mode and spewing errors for all > > patches since 10/03. > > No clue if we have an issue in the main branch, and this test logs are useless. > > > > I'll wait for Intel PRC to be back and ignore for now. > > Yes, the main branch had an issue and has been fixed now. Intel-Testing is back to normal. It works fine. The only info we had was that "something" was broken. Example: http://mails.dpdk.org/archives/test-report/2022-October/313054.html When other CI report a failure, executed commands and logs are available in GHA and UNH dashboard, downloadable as zip files. So it is relatively easy to figure out if the issue was due to an infrastructure problem or if it was a test failure. I don't think Intel CI provide such info. If this is the case, please document it. Otherwise, please Intel CI team, work on providing the same kind of info. Thanks. -- David Marchand