Bug#984894: python-azure: flaky autopkgtest: You need to call 'result' or 'wait' on all LROPoller you have created

2021-04-20 Thread Luca Boccassi
On Mon, 12 Apr 2021 21:18:02 +0200 Paul Gevers  wrote:
> Control: severity -1 serious
> 
> Hi Luca,
> 
> [Please CC submitters if you ask for their input, the BTS doesn't
> forward messages automatically]
> 
> On Wed, 24 Mar 2021 16:53:52 + Luca Boccassi  wrote:
> > I have ran the sdk/resources/azure-mgmt-resource tests locally for ~30
> > times and unfortunately I am not able to reproduce the issue.
> 
> Did you by any chance run them in parallel? The failures on amd64 always
> happen on ci-worker13, which is running 8 parallel debci workers.
> Interestingly enough, armhf is *always* running on a host with 8
> parallel debci workers and there the issue isn't seen. All our arm64
> workers have two debci workers, as does ppc64el. The former is lightly
> flaky, the latter hasn't showed a failure yet since -2.
> 
> > Hence I'm
> > downgrading + adding tags for help - if anyone is able to reproduce or
> > spot the issue, a MR is more than welcome.
> > This particular module was also updated in -4 to solve an unrelated
> > issue, so it might very well be that this is solved too.
> 
> -4 is as flaky as before.
> 
> If there's something specific we can test for you on the ci.d.n infra
> let us know.
> 
> Paul
> (Release Team hat on for the severity call, CI Team hat on for the offer
> to help on the infra.)

Hi,

Thanks for the further information - I have now tried to run the same
test in parallel multiple times, but still no luck.

I'll just go ahead and blocklist it in the next upload.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


Bug#984894: python-azure: flaky autopkgtest: You need to call 'result' or 'wait' on all LROPoller you have created

2021-03-24 Thread Luca Boccassi
Control: severity -1 important
Control: tags -1 unreproducible help

On Tue, 9 Mar 2021 20:51:00 +0100 Paul Gevers 
wrote:
> Source: python-azure
> Version: 20201208+git-3
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org

> Usertags: flaky
> 
> Dear maintainer(s),
> 
> Your package has an autopkgtest, great. However, I looked into
> the history of your autopkgtest [1] (because it is blocking
> sphinx) and I noticed it fails regularly, while a rerun passes. I
> copied some of the output at the bottom of this report.
> 
> Because the unstable-to-testing migration software now blocks on
> regressions in testing, flaky tests, i.e. tests that flip between
> passing and failing without changes to the list of installed packages,
> are causing people unrelated to your package to spend time on these
> tests.
> 
> Paul
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-azure/10719743/log.gz

Hi,

Thanks for the report.

I have ran the sdk/resources/azure-mgmt-resource tests locally for ~30
times and unfortunately I am not able to reproduce the issue. Hence I'm
downgrading + adding tags for help - if anyone is able to reproduce or
spot the issue, a MR is more than welcome.
This particular module was also updated in -4 to solve an unrelated
issue, so it might very well be that this is solved too.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


Bug#984894: python-azure: flaky autopkgtest: You need to call 'result' or 'wait' on all LROPoller you have created

2021-03-09 Thread Paul Gevers
Source: python-azure
Version: 20201208+git-3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] (because it is blocking
sphinx) and I noticed it fails regularly, while a rerun passes. I
copied some of the output at the bottom of this report.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-azure/10719743/log.gz


=== FAILURES
===
 MgmtResourceLinksTest.test_application

pylib/devtools_testutils/mgmt_testcase.py:97: in tearDown
return super(AzureMgmtTestCase, self).tearDown()
pylib/devtools_testutils/azure_testcase.py:193: in tearDown
return super(AzureTestCase, self).tearDown()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _

self = 

def tearDown(self):
os.environ = self.original_env
# Autorest.Python 2.x
assert not [t for t in threading.enumerate() if
t.name.startswith("AzureOperationPoller")], \
"You need to call 'result' or 'wait' on all
AzureOperationPoller you have created"
# Autorest.Python 3.x
>   assert not [t for t in threading.enumerate() if
t.name.startswith("LROPoller")], \
"You need to call 'result' or 'wait' on all LROPoller you
have created"
E   AssertionError: You need to call 'result' or 'wait' on all
LROPoller you have created

pylib/azure_devtools/scenario_tests/base.py:158: AssertionError
-- Captured log call
---



OpenPGP_signature
Description: OpenPGP digital signature