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 3D686428D4 for ; Wed, 5 Apr 2023 18:13:25 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2A4A241133; Wed, 5 Apr 2023 18:13: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 6FA0441133 for ; Wed, 5 Apr 2023 18:13:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680711202; 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=tNdk/Y2Zh4PnOn/qSo6NqWtQh92t8974kXgmeOatVw8=; b=HJeph+ayb//Z88M3c4dpzcd6AIwdLrtZqF2TGdZQ8C68JzzXvxDq/UzhBcW6GFdXguQzVl 6bsj+/67HYzy8VXPbvyFBYgEeNf64BXg8yyVMv8bo9+xhtzoCCyUt1FKxtiaUEqqp0MkuB sgEYT6UrHe+tA0oVlidNWEHEkl/hECQ= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-173-kkIyvIKuPUOpMO0shUOgCA-1; Wed, 05 Apr 2023 12:13:21 -0400 X-MC-Unique: kkIyvIKuPUOpMO0shUOgCA-1 Received: by mail-wm1-f72.google.com with SMTP id r11-20020a05600c458b00b003eea8d25f06so17742816wmo.1 for ; Wed, 05 Apr 2023 09:13:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680711200; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=tNdk/Y2Zh4PnOn/qSo6NqWtQh92t8974kXgmeOatVw8=; b=7lHH4Bni5PErLGo3f38QV5FiosZpuXqDDYpvLfKt03J4qYmArb+1tXxNE/H2bg88X9 RZqvn/u2ebKQHLplmZjLjq0pAKjia4DTHs4rHD3N2Hnpt/Qlmhl38kmkNSitXXP41YbL yPLzvpNIjS/zYgRi97HmrpHR79xj3tJXsqFZ0XZeXkqQqB/qf1F0TUfiqzm1eJRDh0fG hlsMG870GrGcqD/iGin+jJaJOipJw8/31ctiFxkiWoOlNxkJ8EZIFYG15T3g3uMyQvhk kEXFYm30ewjfGjr62dUMBgymygh61wlbOOX8D2WFDZGIa5OgTreKXu3w+4m6mA+7QV54 QqNQ== X-Gm-Message-State: AAQBX9fswwasjQcNyCiVUDceQo9EEFkeNwODqOvxl50f4zRCo/ohOcoR 9trCy8BkKBlKqmbC6HR30YCOTyoH+COVZqSY6JH0zB5k3d9dHgsAiEgrCcV+HOGLLM6Te7gj5t+ Hpw== X-Received: by 2002:a05:6000:1ca:b0:2e5:820b:9289 with SMTP id t10-20020a05600001ca00b002e5820b9289mr4511032wrx.64.1680711200461; Wed, 05 Apr 2023 09:13:20 -0700 (PDT) X-Google-Smtp-Source: AKy350ZQBfSTGUUU9mOSfbIVpcRmcaVIqxAYWwl+IP50FBFtjZ5vbzKXTunnu51jrtLH7mb8y07ajQ== X-Received: by 2002:a05:6000:1ca:b0:2e5:820b:9289 with SMTP id t10-20020a05600001ca00b002e5820b9289mr4511019wrx.64.1680711200147; Wed, 05 Apr 2023 09:13:20 -0700 (PDT) Received: from [192.168.0.36] ([78.19.103.115]) by smtp.gmail.com with ESMTPSA id n9-20020a5d4009000000b002d431f61b18sm15211617wrp.103.2023.04.05.09.13.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Apr 2023 09:13:19 -0700 (PDT) Message-ID: <3001ba65-d089-4f1b-5f05-56f76e9150db@redhat.com> Date: Wed, 5 Apr 2023 17:13:18 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 To: Patrick Robb Cc: ci@dpdk.org, Lincoln Lavoie , Jeremy Spewock , Aaron Conole , David Marchand References: <141268f7-fd3e-ea22-051f-d1ef52dd58b2@redhat.com> From: Kevin Traynor Subject: Re: 21.11-staging CI run In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 05/04/2023 16:26, Patrick Robb wrote: > Hi Kevin, > Hi Patrick, > We do use the Github mirror for the stable branches. However, the Github > key change is not relevant here because we use https for our git operations > on the stable branches. > > This morning when you pushed to 21.11-staging, our system timed out when > checking out to your commit. Just to check that the issue was reproducible, > I reran the pipeline, and this time the checkout completed fine and a full > series of tests was kicked off for 21.11-staging. I'm not sure if git was > in a bad state or what, but I'm trying to find out more. > ok, cool. It might be just a once off, I haven't seen that in the past. As a workaround, I can force push as it's a staging branch to re-trigger if it occurs again. > Also, the scatter test failure you see on the 21.11-staging results is an > infra issue on our side which is now resolved, and a rerun for that scatter > test is put in so that will be corrected soon. > Thanks for letting me know. I noticed that and saw that I hadn't pushed new Bcm patches, so figured it was an test/infra issue. thanks, Kevin. > On Wed, Apr 5, 2023 at 10:23 AM Kevin Traynor wrote: > >> On 05/04/2023 13:36, Kevin Traynor wrote: >>> Hi, >>> >>> I noticed that 21.11-staging was not kicking off CI the last 2-3 times I >>> pushed to it. >>> >>> It may have been caused by the recent github key change? >>> >>> That is resolved now for dpdk.org -> github replication and I pushed >>> today, but I still didn't see any CI run started. >>> >>> I'm not sure if 21.11-staging is monitoring dpdk.org or github, and also >>> has an issue with keys, or if there is some other issue. >>> >>> Could someone take a look and check? >>> >> >> Update, I see some tests running on 21.11-staging now. Not sure if it >> was just a delay after my push earlier, or someone updated something - >> if so, thanks! >> >>> thanks, >>> Kevin. >> >> >