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 89E93428D4 for ; Wed, 5 Apr 2023 16:23:02 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6FAAD41133; Wed, 5 Apr 2023 16:23:02 +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 5C75341133 for ; Wed, 5 Apr 2023 16:23:00 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680704579; 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=mIIgMG50mSvBZRsJ/3rqqvuxuYyOx+58Bx73gEFbjBQ=; b=W5zNkP8aGirQ5PByGnM/l8QVWRt0awep6DZPbWY2vtZj063LPJ0rXpZJgP3gjOIyUjBffG xqvGldxe3jF6P4cG7hueTs719IyG1UvMjeDxbWHBDf+yudIUpU0dmktShG5XSB4YK5Y3OX bnXXO6HcdmSEbfUohaXcuZcRNcLtRWg= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-503-Cnr7t5GWN8OUEaZeGNWIFQ-1; Wed, 05 Apr 2023 10:22:58 -0400 X-MC-Unique: Cnr7t5GWN8OUEaZeGNWIFQ-1 Received: by mail-wm1-f69.google.com with SMTP id l16-20020a05600c4f1000b003ef6ed5f645so14203681wmq.9 for ; Wed, 05 Apr 2023 07:22:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680704577; h=content-transfer-encoding:in-reply-to:subject:references:cc:to:from :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mIIgMG50mSvBZRsJ/3rqqvuxuYyOx+58Bx73gEFbjBQ=; b=qJ2EoVLgunmFHokaQmrA8za616+neUVEjlC8UJb8/Ww/Bd3c7/YyovjJIDGd8p5b3C XE97kzXpr7MzE860aFZNHFvJmr9QsMytZpy7G3muDxNo91z+mdD3VjimBW2D3ksYvImj s649iLgPESBg/wsg0QxP0kvZMgygsoxwA5tHVrlnaqVUkSB/ZvP88vmRKsEfMuuKqoJQ LH6cJHHEs78689HL6qc1NHuK7V8bNy7ez46H6YijVGFVIwgh5UGavtdVx/wT8by21iyc mrHM+BjLSmEBZ9oSSOMPmxXU+kPyQVrQbPUEEwgQWHv97X+tY1S6EP/hGC5OewIJpsDK yBVw== X-Gm-Message-State: AAQBX9dGMMb3ao7wZLDY596flOWDUo2S7csImB20+EU8nQJdFn8rthsr wSqmTRCEWv4+c851VaUP+UXdOwzXhlHcz2fm9fXYwFNAoug1rbIE4BkOAqGyyEvkCfYKnu9cZ00 KDvH/rZv+dQM9WMWxLmpgsSsmuq+5dw2XL3RGieJyNxeAQHiQviEEN0/9DUfkaw== X-Received: by 2002:a7b:c41a:0:b0:3f0:4428:94fa with SMTP id k26-20020a7bc41a000000b003f0442894famr4850723wmi.26.1680704577660; Wed, 05 Apr 2023 07:22:57 -0700 (PDT) X-Google-Smtp-Source: AKy350YzLBqhg1Sj6O0wm9jGrfhVEbyXSqwtJV9w53iFZbEudU7IJ+uuWm61lnst3pepNHyf/SD6rw== X-Received: by 2002:a7b:c41a:0:b0:3f0:4428:94fa with SMTP id k26-20020a7bc41a000000b003f0442894famr4850703wmi.26.1680704577334; Wed, 05 Apr 2023 07:22:57 -0700 (PDT) Received: from [192.168.0.36] ([78.19.103.115]) by smtp.gmail.com with ESMTPSA id l21-20020a1ced15000000b003ee58e8c971sm2368105wmh.14.2023.04.05.07.22.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 05 Apr 2023 07:22:56 -0700 (PDT) Message-ID: <141268f7-fd3e-ea22-051f-d1ef52dd58b2@redhat.com> Date: Wed, 5 Apr 2023 15:22:56 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 From: Kevin Traynor To: ci@dpdk.org Cc: Patrick Robb , Lincoln Lavoie , Jeremy Spewock , Aaron Conole , David Marchand References: 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: 7bit 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 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.