[TIP] Travis.ci => tox => py.test => exited with code -11
olemis at gmail.com
Sun Jul 8 14:57:57 PDT 2018
On Sun, Jul 8, 2018 at 12:05 PM, Floris Bruynooghe <flub at devork.be> wrote:
> On Sun 08 Jul 2018 at 11:08 -0400, Olemis Lang wrote:
> > On Sun, Jul 8, 2018 at 11:03 AM, Olemis Lang <olemis at gmail.com> wrote:
> >> On Sun, Jul 8, 2018 at 5:17 AM, Floris Bruynooghe <flub at devork.be>
>>> > Does anybody know what could be happening with py.test during this
> >>> build ?
> >>> > What's py.test error code -11 about ?
> >>> Negative return codes do not come from the process (where the python
> >>> interpreter running pytest is the process here), but they indicate the
> >>> unhandled signal with which the OS has terminated the process.
> >> I did not know of this . Shouldn't this be included in the py.test docs
> >> _ . If people knew then issues would be fixed faster . Or maybe this
> >> a temporary situation that should remain undocumented ?
> >> ..  https://docs.pytest.org/en/3.6.3/usage.html#possible-exit-codes
> > Oh ! Nevermind . Now I get it . This is built into the Python
> interpreter .
> > No need to document it since this is not specific to py.test .
> It's the UNIX-like operating system's behaviour really, not specific to
> the Python interpreter even.
Got it . It's completely green in Linux and in MacOS for Python 2.7 _
... which leads to the next question ...
..  https://travis-ci.org/simelo/pyskycoin/builds/401528298
Olemis - @olemislc
Software Eng Skycoin : https://www.skycoin.net
Apache™ Bloodhound contributor : http://issues.apache.org/bloodhound
Brython committer : http://brython.info
SciPy Latin America - Ambassador : http://conf.scipyla.org
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python