Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: "Rebecca N. Palmer" Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python Subject: Bug#1030096: Any ideas Re: #1030096 dask.distributed intermittent autopkgtest fail ? Date: Mon, 06 Feb 2023 22:50:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Mon Feb 6 21:42:10 2023 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -3.499 Reply-To: "Rebecca N. Palmer" , 1030096@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Python Team X-Debian-Pr-Message: followup 1030096 X-Debian-Pr-Package: dask.distributed X-Debian-Pr-Source: dask.distributed Arc-Seal: i=1; a=rsa-sha256; t=1675719575; cv=none; d=zohomail.com; s=zohoarc; b=dUlSPB+ahmVfHkQnD3xVGwRTp5AR1Sp/AC58RSRv2r3pn+1AblkLYSpSw3rSC0C7ovUkqIg74tShAR9yfxGStrpkQ6bIAv88tB+DHf0pUFb21UoaYajIFVTKmBVfjDv3PB05awoRoJQXrTrG7u5awr6LkZZDAEHa+1rhf5ig5R4= Arc-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1675719575; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=IxvQXGb6EUvsx3gcz0FSIoVQpBlnsBfBU+roECu7TBk=; b=U8dCpjfaxee/4gOEXEPULN8y1mMmlc2ezNQDBFomvlM0b6JWI6d6nxXLT0XguvM967QBleJG3Y/LIxs055tQlSvYzk9JhuM5fItFncG5wMvxBfTI1sc1GHpocNP1KwMyZFbP7+koY8UAr5IMSjKu8R9cJxA2c2rZlvXFqA70i+s= Arc-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=zoho.com; spf=pass smtp.mailfrom=rebecca_palmer@zoho.com; dmarc=pass header.from= MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Zohomailclient: External X-Debian-Message: from BTS X-Mailing-List: archive/latest/1758624 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 25 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 1030096@bugs.debian.org, debian-python@lists.debian.org X-Original-Date: Mon, 6 Feb 2023 21:39:24 +0000 X-Original-Message-ID: <4fe948af-768e-4179-c1f1-87cde1b03792@zoho.com> X-Original-References: <501750bb-274c-6bba-7e04-594458aea097@zoho.com> <46ffe341-69af-90e0-3431-9cab6ecd391b@debian.org> Xref: csiph.com linux.debian.bugs.dist:1136713 linux.debian.maint.python:14905 I agree that xfailing the tests *may* be a reasonable solution. I'm only saying that it should be done by someone with more idea than me of whether these particular tests are important, because blindly xfailing everything that fails is effectively not having tests. If we do choose that approach, at least test_balance_expensive_tasks needs to be an outright xfail/skip not just a flaky, because when it fails it fails repeatedly. On 06/02/2023 19:38, Diane Trout wrote: > The most important thing about dask / dask.distributed is they really > should be at about the same upstream version. I knew that, and was planning on 2022.12.1 of both when I decided to go ahead with pandas. What went wrong was that I only tested a build, not an autopkgtest, and thought the failing tests were dask.distributed's (known) inability to run all its tests in a buildd environment. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027254#21 > I'm not 100% sure how to > mark that in the d/control file. Possibly Depends: python3-dask (>= 2022.12.1~), python3-dask (<< 2022.12.2~) but I haven't tested that.