Title: Implement timeout mechanism · Issue #353 · python/pyperformance · GitHub
Open Graph Title: Implement timeout mechanism · Issue #353 · python/pyperformance
X Title: Implement timeout mechanism · Issue #353 · python/pyperformance
Description: Hello, as discussed on Discourse it would be nice to implement a timeout within pyperfomance. If a benchmark run hangs, pyperformance doesn’t have a mechanism to time out and terminate the underlying process. We’ve had a few cases where ...
Open Graph Description: Hello, as discussed on Discourse it would be nice to implement a timeout within pyperfomance. If a benchmark run hangs, pyperformance doesn’t have a mechanism to time out and terminate the underlyi...
X Description: Hello, as discussed on Discourse it would be nice to implement a timeout within pyperfomance. If a benchmark run hangs, pyperformance doesn’t have a mechanism to time out and terminate the underlyi...
Opengraph URL: https://github.com/python/pyperformance/issues/353
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Implement timeout mechanism","articleBody":"Hello,\r\n\r\nas discussed on [Discourse](https://discuss.python.org/t/add-timeout-management-in-pyperformance/63728) it would be nice to implement a timeout within pyperfomance.\r\n\r\nIf a benchmark run hangs, pyperformance doesn’t have a mechanism to time out and terminate the underlying process. We’ve had a few cases where a benchmark was hanging literally forever (deadlock) and the job was terminated by the CI system eventually (after many hours!). This is not ideal because:\r\n\r\n* it’s hard to set an appropriate timeout for the whole process as it might vary from machine to machine\r\n* sometimes folks might not have full control of the CI system hence impossible to set a sensible timeout\r\n* having an early failure by pyperformance is preferred than having a timeout at process (pyperformance) level. This allow better usage of CI resources.\r\n\r\nRequirements:\r\n* Ideally the timeout would be applied at benchmark run level and not for the whole pyperformance process allowing a more fine grained control in case of timeout.\r\n* If a benchmark times out, it should not fail the whole pyperformance suite but we should mark it as failed (there is already a mechanism to do that).\r\n* There should be able to provide an option at cli level to override the default timeout value.","author":{"url":"https://github.com/diegorusso","@type":"Person","name":"diegorusso"},"datePublished":"2024-09-13T13:24:37.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/353/pyperformance/issues/353"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:c2d745d5-e9b6-0a67-9fdd-56872453e414 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | DFBA:2780A3:24B4D15:3225DFC:696AC4FE |
| html-safe-nonce | b18d4235cdfe6e7efafccaede63a85c67814b2bad79daa5011a87f402d0e5531 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJERkJBOjI3ODBBMzoyNEI0RDE1OjMyMjVERkM6Njk2QUM0RkUiLCJ2aXNpdG9yX2lkIjoiMTAyNDk2NDM1NDYzNDMzNTQ4NiIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 951df3c4e7358260cd7fae2b69ab0632fcac6e231647d1afd7c662730324837c |
| hovercard-subject-tag | issue:2524849790 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/python/pyperformance/353/issue_layout |
| twitter:image | https://opengraph.githubassets.com/bb4ccaf42eb66fef83c4719d8873174eff6b809e490f409ff69652095f12cd28/python/pyperformance/issues/353 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/bb4ccaf42eb66fef83c4719d8873174eff6b809e490f409ff69652095f12cd28/python/pyperformance/issues/353 |
| og:image:alt | Hello, as discussed on Discourse it would be nice to implement a timeout within pyperfomance. If a benchmark run hangs, pyperformance doesn’t have a mechanism to time out and terminate the underlyi... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | diegorusso |
| hostname | github.com |
| expected-hostname | github.com |
| None | 986b6a1d774985095564e64d6963d11f094da3d0e2bfda2ab1a27d63662eb033 |
| turbo-cache-control | no-preview |
| go-import | github.com/python/pyperformance git https://github.com/python/pyperformance.git |
| octolytics-dimension-user_id | 1525981 |
| octolytics-dimension-user_login | python |
| octolytics-dimension-repository_id | 65949828 |
| octolytics-dimension-repository_nwo | python/pyperformance |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 65949828 |
| octolytics-dimension-repository_network_root_nwo | python/pyperformance |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 89ad2112b9c4e11df6a0c13c8c1f8eedd36b0977 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width