From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0A553A0546; Wed, 26 May 2021 15:06:27 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 84F5440150; Wed, 26 May 2021 15:06:27 +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 B4AA140041 for <dev@dpdk.org>; Wed, 26 May 2021 15:06:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1622034385; 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=wVGlVBQQmwS6082OunEjHhthoNuxoWDLFJ+VyBZTrMs=; b=DNyBzRvI+KDnQpf7S8D8DVHUWZsyRoIrEbWSq9Tbh9bWuzQ3lCP0TnuGAd8LforPpmI2kr O9gmZ47uXM9mlkOoXK2Dnk+9ZOUiGKOyd7FlLgUiPCPlTIVgxdqNhc4hP+t/6AQOgbgvnn JVNMWaL+nwXeJMdA2zcF0n4VuqqZWNE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-226-XL4qOib1NQWuJjt0jXhOlg-1; Wed, 26 May 2021 09:06:23 -0400 X-MC-Unique: XL4qOib1NQWuJjt0jXhOlg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D84F2107ACCD; Wed, 26 May 2021 13:06:18 +0000 (UTC) Received: from RHTPC1VM0NT (ovpn-116-248.rdu2.redhat.com [10.10.116.248]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D4BA6100E113; Wed, 26 May 2021 13:06:11 +0000 (UTC) From: Aaron Conole <aconole@redhat.com> To: dev@dpdk.org Cc: David Marchand <david.marchand@redhat.com>, ci@dpdk.org, Michael Santana <msantana@redhat.com>, Ilya Maximets <i.maximets@ovn.org>, Thomas Monjalon <thomas@monjalon.net> References: <f7teedv8y6p.fsf@redhat.com> <f7tk0nlaeq7.fsf@redhat.com> Date: Wed, 26 May 2021 09:06:10 -0400 In-Reply-To: <f7tk0nlaeq7.fsf@redhat.com> (Aaron Conole's message of "Wed, 26 May 2021 07:58:40 -0400") Message-ID: <f7t5yz5ablp.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [dpdk-dev] [PATCH v2] test: remove strict timing requirements from alarm and cycles tests X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> Aaron Conole <aconole@redhat.com> writes: > The tests 'alarm_autotest' and 'cycles_autotest' rely on the underlying > system having very accurate and precise timing. On systems where the > timing isn't as rigid, or the load is particularly high, these tests are > unreliable since the wake latency from the scheduler can be high enough > to miss the timing window. > > Remove the timing related tests from the test suites. These tests now > ensure the add/remove callback infrastructure unit tests, but drop the > waits and reliance on system timing and load. > > This avoids FAIL on various testing infrastructures. > > Signed-off-by: Aaron Conole <aconole@redhat.com> > --- > v2: Drop the timing requirements, but keep the API calls NAK - I have a v3 for this with some stuff that was missed.