Off topic for review, but congrats to the 10000/s differential to @CHAN ! :-)

@devilhorns ping

If there would be a unit test it could have helped to detect this. Such typos can find it way into various places though when the API call is simply copied from only file to another.
Reviewing APIs manually is always a good idea before a release. Machines can only understand some things that we wanted to be taken care of :-)

Gosh, and I was even the guy disabling it. Getting old here...

I agree, it seems like a little thing, but this consistency helps during development and it is easy enough to change now.

@devilhorns as our remaining wayland expert could you please check on this? Reproduce this with latest efl and weston and see if you can find a fix?

@Thanatermesis can you reproduce this on every terminology start on 32 bit?

I have not seen this failed since a long time. Definitely not since we have meson and Travis in use (not saying that this fixed it but rather to give a timeline).

I have been digging around in this for a while and here is what seems to be happen to me.

I am assigning this purely on the fact that it goes through #17 0x41fdbf in _teardown ../src/tests/eldbus/eldbus_test_eldbus_model_proxy.c:52 everytime I am hitting this.
If you could have a look and see if that comes from the model test code or from the actual eldbus lib that might already help.

Prettier outpur after running with -g -O0 compiled:

25/44 eldbus-suite                            FAIL     1.43 s (exit status 1)

Fixed by a6e679f830b85e0f6512bd8b3c102d07875e07f4

Got fixed by patch D9576

I got fooled by the eolian-mono prefix of the patch. Tested that one now and pushed. Thanks

Thanks, the proposed patch fixes the use after free.

The release-ready build job needs to stay as a cron job. It is taking over 36 minutes to finish. This totally blows our nice 11 minute total time for push builds right now. :-)

oh wait, it also pulls release-ready into the push builds from daily. Hope this does not impact our build time. Will know more after the CI does finish

This looks good. A great side effect is that we would be down to 5 jobs for a push, aka the exact number of parallel jobs we can have. No more waiting. :-)

Alos remove config.cahce file references

Good point. There might actually be more of these around. Will have a look and re-spin tomorrow.