[TEST PR] CallFunc -> JitCall migration
Moving the default constructor execution (TClingCallFunc::ExecDefaultConstructor) to JitCall seems relatively stable on my system (down to 2 failing tests). This PR is not intended to be merged, but to evaluate the test results on all platforms and will be closed
Test Results
20 files 20 suites 3d 5h 10m 27s ⏱️ 3 066 tests 3 066 ✅ 0 💤 0 ❌ 59 724 runs 59 724 ✅ 0 💤 0 ❌
Results for commit 195a654b.
:recycle: This comment has been updated with latest results.
@smuzaffar we believe these changes would benefit from a CMSSW CI run, could you help us with that?
@vepadulano , cmssw ci tests are running via https://github.com/cms-sw/root/pull/225
Hi @smuzaffar @vepadulano, Aaron and me can't see the build logs behind the CMS login. Can one of you CMS guys please check the logs and see if the failures are related, copy-pasting relevant error messages if there are any? Thanks!
cmssw CI tests look good. The unit tests failure are not due to this change. https://github.com/cms-sw/cmssw/pull/48393 should fix those tests (#19096 : Root's removal of deprecated _TDirectory_getattr pythonization)
@smuzaffar can we give another try of this pr in cmssw?
@smuzaffar can we give another try of this pr in cmssw?
restarted cmssw ci tests