<div dir="ltr"><div><div><br></div>Hello Floris<br></div>Thanks for continuing the thread.<br><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jul 8, 2018 at 5:17 AM, Floris Bruynooghe <span dir="ltr"><<a href="mailto:flub@devork.be" target="_blank">flub@devork.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span class=""><br>
On Sat 07 Jul 2018 at 17:27 -0400, Olemis Lang wrote:<br>
> The py.test build step fails [1]_ with exit error code -11 . Nonetheless<br>
> this code is not listed in py.test exit codes list [2]_ .<br>
><br>
> Does anybody know what could be happening with py.test during this build ?<br>
> What's py.test error code -11 about ?<br>
<br>
</span>Negative return codes do not come from the process (where the python<br>
interpreter running pytest is the process here), but they indicate the<br>
unhandled signal with which the OS has terminated the process. In this<br>
case `man 7 signal` tells me signal no 11 is SIGSEGV aka segmentation<br>
fault aka "Invalid memory reference".<br></blockquote><div><br></div><div>I did not know of this . Shouldn't this be included in the py.test docs [1]_ . If people knew then issues would be fixed faster . Or maybe this is a temporary situation that should remain undocumented ?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So the most likely explanation is that one of your go or swig layers is<br>
allowing your python code to execute something that it shouldn't and the<br>
bug is in those layers somewhere rather then in python or pytest. </blockquote><div><br><br></div><div>Well, for the record , the actual problem was that Travis build was installing SWIG 2.x instead of 3.0.12 .<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The<br>
traditional first step to figure this out is to enable coredumps and<br>
then run the debugger on the coredump which will show you the stack<br>
frames leading up to the crash and hopefully point you in the right<br>
direction.<br>
<br><br></blockquote><div>[...] <br></div></div><br></div><div class="gmail_extra">... but still I'll explore how to do it since I'm not familiar with this .<br></div><div class="gmail_extra"><br>.. [1] <a href="https://docs.pytest.org/en/3.6.3/usage.html#possible-exit-codes" target="_blank">https://docs.pytest.org/en/3.<wbr>6.3/usage.html#possible-exit-<wbr>codes</a><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Regards,<br><br>Olemis - @olemislc<br><br><div>Software Eng Skycoin : <a href="https://www.skycoin.net" target="_blank">https://www.skycoin.net</a><br></div>Apache™ Bloodhound contributor : <a href="http://issues.apache.org/bloodhound" target="_blank">http://issues.apache.org/bloodhound</a><br>Brython committer : <a href="http://brython.info" target="_blank">http://brython.info</a><br></div>SciPy Latin America - Ambassador : <a href="http://conf.scipyla.org" target="_blank">http://conf.scipyla.org</a><br><br>Blog ES: <a href="http://simelo-es.blogspot.com/" target="_blank">http://simelo-es.blogspot.com/</a><br>Blog EN: <a href="http://simelo-en.blogspot.com/" target="_blank">http://simelo-en.blogspot.com/</a><br><br>Featured article:<br></div></div></div></div>
</div></div></div></div>