Pablo Galindo Salgado

I have amended the last commit with your requests, please take another look

Has this been fixed by either #117120 or #117213?

All the pages you mention are supposed to be in the included buildbot package so there is nothing we need to rewrite in our side. Can you confirm this with...

I think it's time to rollback the upgrade, the buildbot page it's certainly less usable and the release dashboard it's broken and everything feels either slower or slightly broken.

@encukou could you please revert https://github.com/python/buildmaster-config/commit/e5d6b0672b9c189a64c2c09eb91d77e20c4c7cdd and the buildbot 4.0 upgrade PRs? If you don't have free cycles I can give it a go if you preefer

Also, I think we should bring this up with the buildbot project. We are probably among their heavier users and I am not sure if they are informed of all...

Ohhhh, I know what's happening. Seems that importing `llvmlite.binding` dlopens the process itself and there is a second mapping and that returns a garbage value for `_PyRuntime`. Before importing: ```...

``` cpython main ? ❯ diff lel1.txt lel2.txt 9,10c9,29 < 3f472000-3f71c000 rw-p 00000000 00:00 0 [heap] < 7f6b85f00000-7f6b86200000 rw-p 00000000 00:00 0 --- > 3f472000-3f837000 rw-p 00000000 00:00 0 [heap]...

After forcing https://github.com/bloomberg/pystack/blob/134db1dbf1a59c04d9681f9d55ef8d2d4209a6da/src/pystack/_pystack/unwinder.cpp#L378 to not overwrite the previous value I can unwind correctly. The problem is that the module is called twice!

Thanks for the contribution @devdanzin and thanks @ZeroIntensity for the review!