On 24/02/2022 7:18 pm, Chris Withers wrote:
On 23/02/2022 22:04, Jean-Paul Calderone wrote:
Apart from that, a couple other trial issues that bothered me
recently are:
* https://twistedmatrix.com/trac/ticket/10311
<https://twistedmatrix.com/trac/ticket/10311>
* https://twistedmatrix.com/trac/ticket/10312
<https://twistedmatrix.com/trac/ticket/10312>
If these bother you, I feel like I must be missing something obvious:
What's the correct way to end a trial -u run such that you don't get
an ugly traceback and a non-zero return code when it's been running
for a while and no tests have failed?
I have to to confess I've never used -u and I would assume it's for
catching some subtle nondeterministic bugs (hardware, threads or other
strangeness)
if it has a more general use, i'd be keen to know
Anyway, the problem is it's behaviour changes with -jN
Internally -jN causes a separate test runner to be used, see
https://github.com/twisted/twisted/blob/trunk/src/twisted/trial/_dist/disttrial.py
this is where the difference in behaviour lies. The fix seems
straightforward enough (I think the two tickets can be fixed in one PR)
Not sure how to write a test case though
Ian
cheers,
Chris
_______________________________________________
Twisted mailing list -- twisted@python.org
To unsubscribe send an email to twisted-le...@python.org
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/twisted@python.org/message/IK6NBM3LV2TE7RSKVS6RQHG7MBEBZKZB/
Code of Conduct: https://twisted.org/conduct
_______________________________________________
Twisted mailing list -- twisted@python.org
To unsubscribe send an email to twisted-le...@python.org
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/twisted@python.org/message/TUQ25WTXTEMHMX3KV4F3GTVGEW7XTRFE/
Code of Conduct: https://twisted.org/conduct
