Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8771
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Help for Python mock test suite needed |
| Date | 2016-08-15 12:00 +0200 |
| Message-ID | <s6mQx-3Wz-5@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <s5Kid-3N8-7@gated-at.bofh.it> <s5PBf-7sM-3@gated-at.bofh.it> <s5RMJ-mo-3@gated-at.bofh.it> <s5WW6-45C-1@gated-at.bofh.it> <s68Xg-3DL-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Aug 15, 2016 at 05:00:52AM +1000, Ben Finney wrote:
> > https://paste.debian.net/789238/
>
> That appears to be a simple failure when the test suite is run. The
> assertions, as reported, are in the ‘test_srst2’ module:
>
> =====
> […]
> File "test_srst2.py", line 213, in test_run_bowtie_with_defaults
> run_mock.assert_called_once_with(expected_bowtie2_command)
> File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 947, in assert_called_once_with
> raise AssertionError(msg)
> AssertionError: Expected 'run_command' to be called once. Called 0 times.
>
> […]
>
> File "test_srst2.py", line 180, in test_run_bowtie_with_overide
> run_mock.assert_called_once_with(expected_bowtie2_command)
> File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 947, in assert_called_once_with
> raise AssertionError(msg)
> AssertionError: Expected 'run_command' to be called once. Called 0 times.
> =====
>
> The tracebacks tell you what test case functions are emitting failures:
>
> File "test_srst2.py", line 213, in test_run_bowtie_with_defaults
> File "test_srst2.py", line 180, in test_run_bowtie_with_overide
>
> Within those test case functions you can see the exact command that was
> expected to be run. The assertion is that ‘srst2.run_command’ is
> expected to be called (with specific arguments), but is not called,
> hence the assertion fails.
Yes, this is what I guessed from the log. However, how can I find out
why exactly the command is not called?
Kind regards
Andreas.
--
http://fam-tille.de
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Help for Python mock test suite needed (Was: Any help with problem of srst2 new versions tests suite failing to call bowtie2) Andreas Tille <andreas@an3as.eu> - 2016-08-13 08:50 +0200
Re: Help for Python mock test suite needed (Was: Any help with problem of srst2 new versions tests suite failing to call bowtie2) Scott Kitterman <debian@kitterman.com> - 2016-08-13 18:50 +0200
Re: Help for Python mock test suite needed (Was: Any help with problem of srst2 new versions tests suite failing to call bowtie2) Andreas Tille <andreas@an3as.eu> - 2016-08-14 00:30 +0200
Re: Help for Python mock test suite needed Ben Finney <ben+debian@benfinney.id.au> - 2016-08-14 02:50 +0200
Re: Help for Python mock test suite needed Andreas Tille <andreas@an3as.eu> - 2016-08-14 08:20 +0200
Re: Help for Python mock test suite needed Ben Finney <ben+debian@benfinney.id.au> - 2016-08-14 21:10 +0200
Re: Help for Python mock test suite needed Andreas Tille <andreas@an3as.eu> - 2016-08-15 12:00 +0200
Re: Help for Python mock test suite needed Ben Finney <ben+debian@benfinney.id.au> - 2016-08-15 22:30 +0200
Re: Help for Python mock test suite needed Andreas Tille <andreas@an3as.eu> - 2016-08-17 14:00 +0200
Re: Help for Python mock test suite needed Barry Warsaw <barry@debian.org> - 2016-08-17 15:30 +0200
csiph-web