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 C63DAA0524; Tue, 13 Apr 2021 09:16:15 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 835FB160BA9; Tue, 13 Apr 2021 09:16:15 +0200 (CEST) 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 20135160BA2 for ; Tue, 13 Apr 2021 09:16:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1618298173; 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=IXqEBoq2ZJwGb9fwkt1ZICS5eFkLBuIVoZcaI4mYbd8=; b=LdzAYXDFTMk4PHPFOpsviK5taz63prIRPt93pSTjZp8MuiLNV4g1DF7FPPw583KGv+D66s rpNsAfdK0RHD3jMoWTTp+Fv0aP+Fp5+KLYfnVfO+R2loPfTh02LvHbFWcu9mhM2hC4i1z3 HGhKAf+tOjVRjxXONG3T/SP9B7Y1qFw= Received: from mail-vs1-f69.google.com (mail-vs1-f69.google.com [209.85.217.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-186-KFOvHeG7NnO5dSAMIjJGMg-1; Tue, 13 Apr 2021 03:16:09 -0400 X-MC-Unique: KFOvHeG7NnO5dSAMIjJGMg-1 Received: by mail-vs1-f69.google.com with SMTP id y20-20020a67d2140000b029020856370ee5so799159vsi.10 for ; Tue, 13 Apr 2021 00:16:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IXqEBoq2ZJwGb9fwkt1ZICS5eFkLBuIVoZcaI4mYbd8=; b=Yeqk/l+CyRrnMyS5K28pCNmqj/2MTlueC+pTgohAJpxIPl4wdFNBVc4JX5p7LAEeRH 9A3qpPrtpm6PNCmm4hu+UwOmGadUSHiFZr/M7Vg5A/YycwMhLqp/hDDtban5TRjcXi7B ogyK3pTuoSRnsPhJkSmFwPNcwbbkjbqpfO4E2Q+2+KyXqjDqiBat+G+3U7VSydWlOfG1 B5dFyzIukitbuEfMM6jW4I9Udx+PsRSIkLqxSsaobngQqfw2bMPsD3SJ22NurGyq1327 JDGz1l7b2zJ5+PD9HB2niy3Ab8RqJNdbvClYKwvtdUon9GkkQ0hPONY6RS4U5nGCs/eH wTnQ== X-Gm-Message-State: AOAM5339g6fHMFlex/mliimVd0H/m/8wocKNnBNmjZfj0YA4OHeXIgXs GV15/Qo6veMs2G5jeu54RH1zjSh24CD9sB5rOZpgniKmoTPrUQ0WsYr8U+6miFLK3H+5gp4MR13 ExmR6NYepQBGIQcIASKk= X-Received: by 2002:a67:f84a:: with SMTP id b10mr23662624vsp.10.1618298169433; Tue, 13 Apr 2021 00:16:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkd1HYauTAjcl3Ht2Hq29HavQwwODrn4Wmm9M7VVSwZkMVtaDaLjmzXUUWBYEq0BwSKGhW7sqaNDbMKjHRSQk= X-Received: by 2002:a67:f84a:: with SMTP id b10mr23662602vsp.10.1618298169223; Tue, 13 Apr 2021 00:16:09 -0700 (PDT) MIME-Version: 1.0 References: <3565653.Ar8n8QqFrN@thomas> In-Reply-To: <3565653.Ar8n8QqFrN@thomas> From: David Marchand Date: Tue, 13 Apr 2021 09:15:58 +0200 Message-ID: To: Thomas Monjalon , Timothy McDaniel , Jerin Jacob Kollanukkaran , Ray Kinsella , Aaron Conole , dpdklab Cc: "abhinandan.gujjar@intel.com" , "harry.van.haaren@intel.com" , dev , Shijith Thotton , Akhil Goyal , Pavan Nikhilesh Bhagavatula , "mattias.ronnblom@ericsson.com" , ci@dpdk.org 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: Re: [dpdk-dev] [pull-request] dpdk-next-net-eventdev - 21.05 - PRE-RC1 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 Sender: "dev" On Tue, Apr 13, 2021 at 12:12 AM Thomas Monjalon wrote: > > 12/04/2021 15:20, Jerin Jacob Kollanukkaran: > > http://dpdk.org/git/next/dpdk-next-eventdev > > Pulled, thanks. > > Note few changes in titles like uppercases for acronyms, > or "add support" simplified as "support", > and release notes moved in the right place. The ABI check now reports an error on event/dlb. The reason is that the event/dlb driver has been removed, and so the check complains about a missing dump. This will have to be fixed quickly or reverted. This has been missed by multiple people, so trying to understand why. The ABI check should have caught this when run by maintainers (/me looks at Thomas and Jerin). The CI should have caught it too. But, v1 did not apply. For v2, I can see a doc generation issue reported by Intel CI that I can't reproduce, so it could be just noise. I can't find reports for Travis or GHA and I could not find in the robot logs why the series_15708 branch was not created. Looking at UNH reports: http://mails.dpdk.org/archives/test-report/2021-March/182956.html But looking at the log: [2713/2716] Compiling C object 'drivers/a715181@@rte_event_octeontx2@sta/meson-generated_.._rte_event_octeontx2.pmd.c.o'. [2714/2716] Linking static target drivers/librte_event_octeontx2.a. [2715/2716] Generating rte_event_octeontx2.sym_chk with a meson_exe.py custom command. [2716/2716] Linking target drivers/librte_event_octeontx2.so.21.1. Error: cannot find librte_event_dlb.dump in /home-local/jenkins-local/jenkins-agent/workspace/Ubuntu18.04-Compile-DPDK-ABI/dpdk/build-gcc-shared/install Is this something that has been fixed since then? I don't have the main branch/recent series status from UNH, but at least GHA and Travis are now complaining about ABI. -- David Marchand