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 3B4C9A0350 for ; Fri, 21 Jan 2022 14:46:52 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 338C74275D; Fri, 21 Jan 2022 14:46:52 +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 97FD640042 for ; Fri, 21 Jan 2022 14:46:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1642772810; 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=c+RV0DTHp8THRMcAWtEOUxGOojKpjWUV2OC3+LHyGrY=; b=Gr0kF/X68r6JdJlix6QdkmS/x9P8XJ5l7aLR9xKX+ve0R27dFmEsBpps+A5oJm/YJspWO7 lfSn/mZ9PLwpa6XOkdYO1jmWsjhFpzi7the7fxAqcpij0Kh0GX7SXvQvUKIGT+KZU1uNwR E36HAYvziPElOML+W7HdaLPj3LPsIUA= 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.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-526-_q2hlPmWPhWQSuxEgmPnHw-1; Fri, 21 Jan 2022 08:46:28 -0500 X-MC-Unique: _q2hlPmWPhWQSuxEgmPnHw-1 Received: by mail-wm1-f72.google.com with SMTP id f7-20020a1cc907000000b0034b63f314ccso6317621wmb.6 for ; Fri, 21 Jan 2022 05:46:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:from:to:cc:references:subject:in-reply-to :content-transfer-encoding; bh=c+RV0DTHp8THRMcAWtEOUxGOojKpjWUV2OC3+LHyGrY=; b=dUvqX6Eaahmo2wEtfuYEf8VameiaHJQTaU5QiG6p7ubovNQrIVnq6kfg+VaNZ5DIA2 8B+fTBzx2MM7a6TfVGxKj4uvZqoh9E96DxZtngNn3A/rAB2cTs2SwUXTgdy3fzD86XfM bJwmbdwcvpX4ZGB04bBKHlVIBTx0TicRAisoYL4qg7udb3vEfqd3g1ZBU0ZXT9D0JEnO q941+MPIvabN6vacu09W/mKyuT2GRHC7PlenzRrDhaKm6erj5iBfrhDW/DMrO9vOusWo IW22MiirBIn0tjP06/djxpP9cXiX6C+6IVr1IWZNID8MgtD4ASZdvKaWt5kJkZ5b5tJ2 0pZA== X-Gm-Message-State: AOAM531e+PpUPNOSU5kdnHVDBUMq4CWVqejIJmyTls6ijZldz8/urBkY gfrrp5XIs/TCbimW6YLhbaxtVDovagrd4xXN55L5YpviqjqS7i8w7UNPGsJbiySaNWfZ5IvUJUS sQw== X-Received: by 2002:a5d:64e8:: with SMTP id g8mr3905272wri.286.1642772787770; Fri, 21 Jan 2022 05:46:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJyo/hbDgCfDI6/YShNPajxAfgo52Sv61nd9blGiH8HioDXpvGgAd+iLni41BiUq+2raub5xGw== X-Received: by 2002:a5d:64e8:: with SMTP id g8mr3905257wri.286.1642772787574; Fri, 21 Jan 2022 05:46:27 -0800 (PST) Received: from [192.168.0.36] ([78.19.108.41]) by smtp.gmail.com with ESMTPSA id k35sm11280028wms.23.2022.01.21.05.46.26 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 21 Jan 2022 05:46:26 -0800 (PST) Message-ID: Date: Fri, 21 Jan 2022 13:46:25 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 From: Kevin Traynor To: Owen Hilyard Cc: ci@dpdk.org, Luca Boccassi , "Xueming(Steven) Li" , Christian Ehrhardt , Lincoln Lavoie , Aaron Conole , Ferruh Yigit , David Marchand , Thomas Monjalon References: <849d066d-7308-994d-4d04-52aeed222c12@redhat.com> Subject: Re: Periodic stable branch testing In-Reply-To: Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ktraynor@redhat.com 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 14/01/2022 10:43, Kevin Traynor wrote: > Hi Owen, > > On 12/01/2022 18:36, Owen Hilyard wrote: >> Hello Kevin, >> >> 19.11 was not being tested due to issues with DTS. 20.11 appears to have >> stopped running testing due to a failed job not releasing .git/index.lock. >> This seems to have caused a timeout in a place where our automated alerts >> had not been initalized, so they were never sent. You should see 20.11 >> nightly builds going forward. >> > > Thanks for the update and for enabling 21.11. I see there is a nightly > build now for 20.11/21.11. > Is there an option for the LTS maintainers to request a run? Periodic builds are very good but coming to release, it would be great for LTS maintainer to be also able to kick-off a build on a branch for a re-test, or check immediately for some patches just applied. I suspect this would be handy for other branch maintainers too outside of LTS. It would be just one or two maintainers per branch, so could be handled by having us login etc. It wouldn't need need parsing of patches as i've seen suggested for patch re-testing. thanks, Kevin. > fyi - noticed brcm scatter test newly failing [0] last night with no > changes to 21.11. Will keep an eye on it to see if it was just an > isolated failure. > > thanks, > Kevin. > > [0] https://dpdkdashboard.iol.unh.edu/results/dashboard/tarballs/18272/ > >> Owen Hilyard >> >> On Wed, Jan 12, 2022 at 1:16 PM Kevin Traynor wrote: >> >>> Hello LTS maintainers and Lincoln, >>> >>> Lincoln let me know that UNH can do periodic testing on stable branches. >>> >>> When I looked at the public dashboard [0] i'm confused with what is >>> running as there doesn't seem to have been runs for a long time and >>> there are many failures. >>> >>> So I'm wondering if/how they are being used by LTS maintainers and what >>> exactly they are testing? >>> >>> thanks, >>> Kevin. >>> >>> [0] >>> 20.11 : >>> >>> https://dpdkdashboard.iol.unh.edu/results/dashboard/periodic_testing/?branch_id=13&page=0 >>> >>> 19.11 : >>> >>> https://dpdkdashboard.iol.unh.edu/results/dashboard/periodic_testing/?branch_id=14&page=0 >>> >>> >> >