Open JunielKatarn opened 3 years ago
Many of our core react-native-windows contributors are taking some much needed vacation throughout December 2020. Thank you for being patient while we relax, recharge, and return to a normal responsiveness in January 2021. In the meantime feel free to continue to pose questions, open issues, and make feature requests - you just may not get a response right away.
FYI @vmoroz since you've been looking at bugs in the Chakra JSI runtime along with @tudorms who has been maintaining v8jsi.
@JunielKatarn do you know whether hermes on windows passes these tests?
@JunielKatarn do you know whether hermes on windows passes these tests?
I do not, but if enabling Hermes is as simple as enabling Chakra (MSBuild property), it can be verified using the same remaining steps.
FYI, these are the tests currently disabled in CI:
#6799 -
# HostFunctionTest - Crashes under JSI/V8
# HostObjectProtoTest - Crashes under JSI/V8
# PreparedJavaScriptSourceTest - Asserts/Fails under JSI/ChakraCore
HostObjectProtoTest
appears to be passing (using V8) when I run it locally. PreparedJavaScriptSourceTest
also appears to be passing, but it may be just for V8 and ChakraCore may still be failing (as per the comments in the CI workflow).
For HostFunctionTest
, it appears to be a failure with two unimplemented APIs:
bool V8Runtime::isHostFunction(const jsi::Function &obj) const {
std::abort();
return false;
}
jsi::HostFunctionType &V8Runtime::getHostFunction(const jsi::Function &obj) {
std::abort();
}
@vmoroz I know this bug is old, but is there a reason why these APIs aren't implemented for V8?
A small number of the tests imported from the Facebook JSI code base (i.e.
node_modules\react-native\ReactCommon\jsi\jsi\test\testlib.cpp
) fail deterministically.Environment
Run the following in your terminal and copy the results here.
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
Expected Results
All tests pass successfully
Actual Results
The following tests fail:
/p:UseV8=false
):Workaround
These specific tests are explicitly disabled in CI/PR validations.