Gyeongjae Choi

Okay, I'm trying to reload Pyodide for each test run. Thanks, @hoodmane for making this available. Let's see what happens.

Well, at least it died after running ~50 tests, which is positive than I thought :) We probably can optimize some of other tests with this "reload" idea (e.g. pyodide/micropip#8)

I'll let this PR draft until I find a better way to manage this. I applied benchmark and timeout updates separately in pyodide/pyodide#2409.

Thanks for the information @leouieda. I'll try that when I have some bandwitdh.

Looks like it builds without error, which is quite promising :) Please add some test so that we can verify it is working correctly. You can create a `test_z3solver.py`in the...

Try adding this line inside meta.yaml. ```yaml build: ldflags: -s SIDE_MODULE=1 ``` > (my working guess, it uses a different suffix, such as "a" instead of "so", if anybody see...

> appreciated, giving it a spin. Also possible that setup.py isn't prepared correctly https://github.com/Z3Prover/z3/blob/2c8df54b70f5456efd0b2c3f4917d2b314098f19/src/api/python/setup.py#L53 I think that line is okay. When I looked inside the built wheel file, it contains...

> I wonder if we should build this out of tree instead. So that you would have the wheel in the z3 CI and get a wheel installable by micropip....

I looked into the build log and the problem seems that we strip `-shared` flag and it makes `emcc` create an invalid object file. (created a PR that fixes it...

> 3\. The docker with pyodide/pyodide doesn't have the pyodide-test-runner. OTOH, it builds z3solver according to the instructions. > When cloning the fork locally to get test-runner, the build stops...