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 6F252A0C4C for ; Tue, 5 Oct 2021 15:09:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 62A654135E; Tue, 5 Oct 2021 15:09:03 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 734E041357 for ; Tue, 5 Oct 2021 15:09:01 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633439341; 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=/Fj824nacVank+ofFwOhrEygOvZMoMByFxtA9gXTWXg=; b=L8tAZLPHCslgE3XSpNBzhelBGnMEDqmS9a12qbRe+OtYDkrEHrOAcGf+C498bSA8OmOtmO OS+S6wUpnX5Z8annEK+y1pCLLTHNGe/OXWl3qbf6IJ3J/9tl36r2uH4/+EWtO3VeN+U+Lq GmAyI+LIrqlNaovJV3geEehH+9AEbOM= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-463-9D6t0jH8O3G0SvC6NQSe9g-1; Tue, 05 Oct 2021 09:08:59 -0400 X-MC-Unique: 9D6t0jH8O3G0SvC6NQSe9g-1 Received: by mail-lf1-f69.google.com with SMTP id c42-20020a05651223aa00b003fd328cfeccso5605045lfv.4 for ; Tue, 05 Oct 2021 06:08:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=/Fj824nacVank+ofFwOhrEygOvZMoMByFxtA9gXTWXg=; b=LrMb8am0zIQs6mh6Qdm3fQInKsb4U6in37IdiOv9rftGQPRRwz5hPfAZbRN+8jcajp o91wZY0g7f6oUQ6I/S4wWE+1zGxx16ab/dtZ7GQk8EzzUtYRYqD68QOZv+5h0rhjZ2YZ zXeEvZogvEEST+UVwKp0Inl7p3A6FEBsrgnGQr5fpjFzN1Fs0X+bCPr/tT4kJjqohHYQ rtNJdOJSVFvzgAv6oQMkQul89pK0tPDrMNqfGg3KmdsEwXHY3TEiCakztBuIbD3B2xR3 mI0CoRlQhRqD+NKpshkic/PQWs+B5+Arl+smYdG/StOKxThknkKSg6tb+9d6C7VEBKrZ qVug== X-Gm-Message-State: AOAM530MeASvSibs78ndScQHZ5N6Ef/KApI4549EscGukL4g/hM6M53R taqJCqj/rvfGMZl/Sbn1fwsHAJeo/Np5piCyH/gzRH8E/BuvRmSosMmmsQshkxFHmOaWTWhS0TC 66xnFdvlstrUSX4WeBQ== X-Received: by 2002:a2e:91d4:: with SMTP id u20mr21989763ljg.81.1633439337847; Tue, 05 Oct 2021 06:08:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwxHkyZBdtcL9WeXl6BwWKmk5cupQ8Ty6eLrcisn8NxYW41brZaIndyRALdR4CwiXKg3jwDkaiBYtC/feYGIv4= X-Received: by 2002:a2e:91d4:: with SMTP id u20mr21989739ljg.81.1633439337671; Tue, 05 Oct 2021 06:08:57 -0700 (PDT) MIME-Version: 1.0 From: David Marchand Date: Tue, 5 Oct 2021 15:08:46 +0200 Message-ID: To: "Chen, Zhaoyan" , Lincoln Lavoie , Ali Alnubani , Aaron Conole , ci@dpdk.org Cc: dev , Thomas Monjalon , "Yigit, Ferruh" Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: [dpdk-ci] Should we keep autotest.py ? 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 Sender: "ci" Looking at how to add an autotest, I came upon autotest_data.py used by autotest.py which has been in DPDK for a long time. >From what I see, DTS directly calls the test binary. The public CI relies on meson to invoke unit tests. Is the autotest.py script still used in some CI or can we remove it? -- David Marchand