Update to Xeus 4.3.4#304
Conversation
|
Unfortunately the "Switch to R kernel and run R code" test shows that it crashes, and I don't know what we can do about it. The video from the CI artifacts doesn't reveal anything substantive. |
3bc0bff to
c4e221f
Compare
|
I don't think I have any insight into what's happening here, @krassowski and @peytondmurray – if you could take a look at this and offer any guidance, or perhaps take over and see if you can budge this, possibly, that would be great. Thanks! |
|
Testing it locally: it works, although it does log an ominous error in the console ( |
|
Okay, makes sense. The "memory access out of bounds" error not showing up locally but showing up in CI most likely just means that the CI runner has too less RAM. Is there something we can do to reduce the memory consumption of the tests in Playwright or free up memory in the runner? |
|
That error - I saw it locally, not on CI. |
|
Ah, sorry, I misread! I ran 4.3.4 locally, and it reported no memory access errors to me on a fresh tab. My machine has 18 GiB RAM, so nearly the same as yours I assume. |
|
Well, since it fails on |
Does not seem to be about resource usage, but about unsafe access which is worse and can trigger crashes. |
This retries the bump to Xeus 4.3.4, as we split it away from #298.