Closed diegorusso closed 1 month ago
I may have sent you forth with bad information by suggesting that this would be easier in
pyperformance
, and maybe @vstinner is right that this would be better handled inpyperf
.We'd still need a patch to
pyperformance
to pass the--timeout
value down to pyperf -- 80% of this PR is handling commandline arguments as it is, so not wasted effort.
Don't worry, that's the purpose of the review. I leave this PR open for now and implement the timeout in pyperf. Once that one is in, I'll fix this up to make use of the timeout.
I've addressed feedbacks on this PR and also raised a new one in pyperf: https://github.com/psf/pyperf/pull/205
Just to let you know that the pyperf PR has been merged (thanks @vstinner) so we have the timeout functionality there.
Just to let you know that the https://github.com/psf/pyperf/pull/205 has been merged (thanks @vstinner) so we have the timeout functionality there.
You need a pyperf release first.
Just to let you know that the psf/pyperf#205 has been merged (thanks @vstinner) so we have the timeout functionality there.
You need a pyperf release first.
I started one here
Your PR should update pyperf to 2.8.
Your PR should update pyperf to 2.8.
I see that pyperf is unpinned so in theory I should not change anything in there. I have done a fresh install of pyperformance and in fact it installs pyperf 2.8
Your PR should update pyperf to 2.8.
I see that pyperf is unpinned so in theory I should not change anything in there. I have done a fresh install of pyperformance and in fact it installs pyperf 2.8
I think you still need to update it here, which is the version that will actually run in the venvs.
Your PR should update pyperf to 2.8.
I see that pyperf is unpinned so in theory I should not change anything in there. I have done a fresh install of pyperformance and in fact it installs pyperf 2.8
I think you still need to update it here, which is the version that will actually run in the venvs.
Yes, you are right. I've just found it! :)
I'm currently running the tests because there is a small change in the way pyperf reports unit measure: https://github.com/psf/pyperf/commit/432c419cff97804de8c780e82d2a8562e977275a
Add the
--timeout
flag to therun
command. By default there is no timeout and user needs to specify it if they want it. I wanted to avoid to change the current behaviour. This addressed the issue https://github.com/python/pyperformance/issues/353If you run the below command passing the timeout of 1 second, dask will fail and it will be reported at the end.