From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id A47BC4DC80 for ; Sun, 2 Mar 2025 08:31:53 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id AC13768E14E; Sun, 2 Mar 2025 10:31:49 +0200 (EET) Received: from smtp.waider.ie (smtp.waider.ie [52.31.250.228]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A4B3968DF7E for ; Sun, 2 Mar 2025 10:31:43 +0200 (EET) Received: from smtpclient.apple (unknown [109.255.224.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.waider.ie (Postfix) with ESMTPSA id 073CF4AB38 for ; Sun, 2 Mar 2025 08:31:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=waider.ie; s=waider_ie; t=1740904303; bh=sQJKYnJd7YnY9LLbtbxtV7+CqT4gO7lRU/chddY/j3M=; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject: Message-Id:Date:To; b=q/n/2MUDsDokC5Pjh6bXLkjnaT+hq4x1r9cSHm391xU9zxh+C4QZp5xYGaZuNAQOM ZRYAKzTWFj+uvWAfs3Oc4lWddB53rVvR/6X7rVhRooMfUOxKxth1hmKy0n8x55JWnl i5ZJnOoPOfw4gKjOLkNCL5LcMla5dxBDMuZdYrD8= From: Ronan Waide Organization: Poor, at best Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\)) Message-Id: <44C98277-BCB9-4AEA-AF0F-185BF1EA4BB8@waider.ie> Date: Sun, 2 Mar 2025 08:31:35 +0000 To: FFmpeg development discussions and patches X-Mailer: Apple Mail (2.3826.400.131.1.6) X-Spam-Status: No, score=-102.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED,URIBL_DBL_BLOCKED_OPENDNS,URIBL_ZEN_BLOCKED_OPENDNS, USER_IN_WELCOMELIST,USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.3 X-Spam-Checker-Version: SpamAssassin 3.4.3 (2019-12-06) on ec2.waider.ie Subject: [FFmpeg-devel] retriggering patchwork for failed fate tests? X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: hi folks, I submitted a patch yesterday which seems to have failed automated `make fate` tests in a place unrelated to the patch (https://patchwork.ffmpeg.org/check/114511/, https://patchwork.ffmpeg.org/check/114513/). I saw a few other patches also failing in this same way - it looks like some libavcodec/tests files contain deprecated usages. I've since seen other patches submitted without tripping over this, so I'm not sure if the failures were triggered specifically by touching files in libavcodec, or if this was an unrelated failure that's since been fixed. `make fate` runs fine on my laptop, but I'm on apple silicon and the failing builds are x86/loongarch64. What is the correct etiquette here? It seems like my patch may not be at fault, so I could just submit a v5 and see what happens, but that feels like potentially wasting time if it's just going to hit the same problem. Cheers, Waider. -- Ronan Waide waider@waider.ie _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".