From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from picard.linux.it (picard.linux.it [213.254.12.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 31129C433F5 for ; Tue, 8 Feb 2022 18:50:43 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id D8F823C9B6A for ; Tue, 8 Feb 2022 19:50:40 +0100 (CET) Received: from in-3.smtp.seeweb.it (in-3.smtp.seeweb.it [IPv6:2001:4b78:1:20::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by picard.linux.it (Postfix) with ESMTPS id BD8D73C03AE for ; Tue, 8 Feb 2022 19:50:31 +0100 (CET) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by in-3.smtp.seeweb.it (Postfix) with ESMTPS id C5EA31A00924 for ; Tue, 8 Feb 2022 19:50:30 +0100 (CET) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id C6AE7210F8; Tue, 8 Feb 2022 18:50:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1644346229; h=from:from:reply-to:reply-to: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=2ElMprPW5Cp7bYbLMDurp9MJhtcae8shwWsLRlc5Le4=; b=hqC1muMEEhBOT1mSZpmWzpMmSEaF0KUJAm2yffVoI60P/29B1kCpfjDWyeAppwzj6p2QtG U4h9NdBI90XjviJuf4+r6ZuCCEOC+VVY8knSTNmuJ87NtCtCfewqVHBssGgoOJwHHn+3lj hR+Wrk6bMMl8m/ZyHivNs/Q9BHgK0+M= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1644346229; h=from:from:reply-to:reply-to: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=2ElMprPW5Cp7bYbLMDurp9MJhtcae8shwWsLRlc5Le4=; b=psxEUvw3Qx44/VSyV+Dbt/ToMTniU5PCDlcTdnjEVjr4oZDd65xGylEf6w/KHjPNyjemSn oiGuN1ZkhgvSmVCA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4926113D09; Tue, 8 Feb 2022 18:50:29 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id vu6zD3W7AmIcCQAAMHmgww (envelope-from ); Tue, 08 Feb 2022 18:50:29 +0000 Date: Tue, 8 Feb 2022 19:50:27 +0100 From: Petr Vorel To: Veronika Kabatova Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Virus-Scanned: clamav-milter 0.102.4 at in-3.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [Automated-testing] SCTP testing X-BeenThere: ltp@lists.linux.it X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Test Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Petr Vorel Cc: Marcelo Ricardo Leitner , Xin Long , Joerg Vehlow , Neil Horman , Vlad Yasevich , Baruch Siach , Philip Li , linux-sctp@vger.kernel.org, Thomas Petazzoni , Erico Nunes , ltp@lists.linux.it, automated-testing@lists.yoctoproject.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-bounces+ltp=archiver.kernel.org@lists.linux.it Sender: "ltp" Hi Veronika, all, > On Thu, Feb 3, 2022 at 6:51 PM Petr Vorel wrote: > > Hi all, > > we've been just discussing, which repository should be hosting SCTP tests [1]. > > Do you use these SCTP tests? If yes, do you use it from LTP [2] or the official > > SCTP kernel developers repository [3] ? If you use integrated to some testing > > framework, would it be a problem if repository changes? > > Also, do you use LTP network tests at all? > Hi, > we're currently not running these, but if I may offer a suggestion from my > experience: It's easier for people to pick up testing when it's already a > part of a test suite, rather than a separate test that they have to figure > out a) even exists b) how to run it > There are large test suites like LTP, kselftests and xfstests that most > people are aware of, but then you get a lot of smaller tests or random > scripts that, unless you're already familiar with the subsystem or get > them linked directly, people won't find easily. And if a CI system wants > to start running those tests, they most likely need to create a wrapper > to handle test specifics, while the enablement via a larger test suite > is way easier (as they can already handle it and all that's needed is > to enable that specific test subset). > Consolidating smaller tests into LTP or kselftests, where applicable, > would make the testing process more streamlined and easier to follow > for new folks too, as the expected testing could be unified across > subsystems and there would be no surprises. Thanks a lot for your input. Agree, thus from this point it'd make more sense to keep it in LTP. Given only 2 people responded and none of you actually run these tests. That suggests little interest in SCTP testing. @SCTP kernel maintainers: We LTP maintainers don't care which repo will be chosen it's up to you to decide. Kind regards, Petr > Veronika > > Kind regards, > > Petr > > [1] https://lore.kernel.org/linux-sctp/YfpnVfrto4Elshy5@pevik/ > > [2] https://github.com/linux-test-project/ltp/tree/master/utils/sctp > > [3] https://github.com/sctp/lksctp-tools -- Mailing list info: https://lists.linux.it/listinfo/ltp