Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split Variant marshalling tests #53035

Merged
merged 9 commits into from
May 30, 2021

Conversation

kant2002
Copy link
Contributor

These tests split to be able test ComWrappers,
built-in COM enabled/disable mode.
See #50500, #51265

@kant2002
Copy link
Contributor Author

Initially discovered as part of dotnet/runtimelab#1142
I do not know how to pass IsComSupported to test and how to read. Would like that somebody help me with that.
This PR to gather feedback on the implementation details, code split approach.

@AaronRobinsonMSFT
Copy link
Member

I do not know how to pass IsComSupported to test and how to read. Would like that somebody help me with that.

Adding a feature flag to a test project is the same as passing it in the product. See https://github.com/dotnet/runtime/pull/52940/files#diff-c25cd81bf60eaf73ca87747baafae7fbfd0ac8a787da03b22382eff45316c9e5 and look for RuntimeHostConfigurationOption.

@AaronRobinsonMSFT
Copy link
Member

/cc @LakshanF @elinor-fung

@kant2002
Copy link
Contributor Author

I think I overcomplicate PR. I will revert changes, and will create couple projects in same folder. Seems to be that would be easier to maintain.

@LakshanF
Copy link
Member

@kant2002, thanks for taking a look! Please also take a look at some test changes that are already present for library, and the pending PR, #52940, that has some tests for the runtime.

@kant2002
Copy link
Contributor Author

@LakshanF this changes just for Variant marshalling. Hopefully current version is in spirit of what was for #52940

@kant2002
Copy link
Contributor Author

Build was failed, since results was not sent to Helix

@LakshanF
Copy link
Member

I see these 2 tests failing when built-in COM is disabled,

Interop\PInvoke\Variant\VariantTestBuiltInComDisabled\VariantTestBuiltInComDisabled.cmd
Interop\PInvoke\Variant\VariantTestComWrappers\VariantTestComWrappers.cmd

The first test has the following output,

BEGIN EXECUTION
"C:\h\w\AC52093C\p\corerun.exe" -p "System.Runtime.InteropServices.BuiltInComInterop.IsSupported=false" VariantTestBuiltInComDisabled.dll
Built-in COM Disabled?: True
Test failed: System.NotSupportedException: Built-in COM has been disabled via a feature switch. See https://aka.ms/dotnet-illink/com for more information.
at System.StubHelpers.ObjectMarshaler.ConvertToNative(Object objSrc, IntPtr pDstVariant)
at VariantNative.Marshal_ByValue_Object(Object obj)
at Test.TestByValue(Boolean hasComSupport) in VariantTestBuiltInComDisabled.dll:token 0x6000059+0x223
at Test.Main() in VariantTestBuiltInComDisabled.dll:token 0x600005e+0x34
Expected: 100
Actual: 101
END EXECUTION - FAILED

@kant2002
Copy link
Contributor Author

Thanks for pointing me in the error log. I was able to find it afterwards. I see now only one error

    Interop\PInvoke\Variant\VariantTestComWrappers\VariantTestComWrappers.cmd [FAIL]
      
      Return code:      1
      Raw output file:      C:\h\w\AF5C0958\w\B3E30948\e\Interop\PInvoke\Reports\Interop.PInvoke\Variant\VariantTestComWrappers\VariantTestComWrappers.output.txt
      Raw output:
      BEGIN EXECUTION
       "C:\h\w\AF5C0958\p\corerun.exe" -p "System.Runtime.InteropServices.BuiltInComInterop.IsSupported=false" VariantTestComWrappers.dll 
      Test failed: TestLibrary.AssertTestException: Assert.IsTrue: 
         at TestLibrary.Assert.HandleFail(String assertionName, String message) in TestLibrary.dll:token 0x6000021+0x11
         at TestLibrary.Assert.IsTrue(Boolean condition, String message) in TestLibrary.dll:token 0x600000a+0x3
         at Test.TestByValue(Boolean hasComSupport) in VariantTestComWrappers.dll:token 0x6000059+0x223
         at Test.Main() in VariantTestComWrappers.dll:token 0x600005e+0xc
      Invalid format. Expected VT_DISPATCH.

Does that means that ComWrappers has slightly different marshalling, or this is a bug? Should I fix that bug as part of PR?

@AaronRobinsonMSFT
Copy link
Member

Does that means that ComWrappers has slightly different marshalling, or this is a bug? Should I fix that bug as part of PR?

@kant2002 It isn't clear to me which statement in the test is failing. Can you narrow it down to which one is the issue?

@kant2002
Copy link
Contributor Author

@kant2002
Copy link
Contributor Author

Honestly I did not run that. It's just reading logs. I'm yet to build single test project locally. Otherwise it's hard to me to allocate time (~1 hour). If you strictly need me to build, and validate my last statement, let me know. I will compile and troubleshoot in more details. But I think I point location to you properly.

@AaronRobinsonMSFT
Copy link
Member

AaronRobinsonMSFT commented May 25, 2021

@kant2002 The issue here is a bug in the ComWrappers conversion logic for IDispatch. It is a part of the absolute mess that is the OLE support and how enum values are used as both request and result – yuck.

In the both case we detect if IDispatch is implemented but don't reduce the returned enum value to just ComIpType_Dispatch but return the input - which is the request not the result. The solution here is to return either ComIpType_Dispatch or ComIpType_Unknown but not ComIpType_Both.

if (TryGetComIPFromObjectRefUsingComWrappers(*poref, &pUnk))
{
hr = S_OK;
IUnknown* pvObj;
if (ReqIpType & ComIpType_Dispatch)
{
hr = SafeQueryInterface(pUnk, IID_IDispatch, &pvObj);
pUnk->Release();
}
else
{
pvObj = pUnk;
}
if (FAILED(hr))
COMPlusThrowHR(hr);
if (pFetchedIpType != NULL)
*pFetchedIpType = ReqIpType;
RETURN pvObj;
}

@AaronRobinsonMSFT
Copy link
Member

Should I fix that bug as part of PR?

Yes, that would be much appreciated.

@kant2002
Copy link
Contributor Author

@AaronRobinsonMSFT can you take a look?

@kant2002
Copy link
Contributor Author

Do not understand test failures. Please advice if this something which I'm responsible with?

Copy link
Member

@AaronRobinsonMSFT AaronRobinsonMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kant2002 I would take a step back here and walk through this logic more fully. I think there was some confusion on when this was originally written and support IDispatch has uncovered that in the ComWrappers scenario.

/cc @elinor-fung

@@ -189,17 +189,26 @@ IUnknown *GetComIPFromObjectRef(OBJECTREF *poref, ComIpType ReqIpType, ComIpType
{
hr = SafeQueryInterface(pUnk, IID_IDispatch, &pvObj);
pUnk->Release();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This Release shouldn't be called indiscriminately here. We are checking for IDispatch now and it could fail, but ComIpType_Unknown must still be returned. Move this release into the success path below.

src/coreclr/vm/interopconverter.cpp Show resolved Hide resolved
@kant2002
Copy link
Contributor Author

kant2002 commented May 27, 2021

Do I understand correctly that in discussed part of code, I should follow these rules?

ReqIpType = ComIpType_Both

  1. QI to IDispatch - ok
pUnk->Release();
FetchedIpType = ComIpType_Dispatch;
  1. QI to IDispatch - failed
pvObj = pUnk;
FetchedIpType = ComIpType_Unknown;

ReqIpType = ComIpType_IDispatch

  1. QI to IDispatch - ok
pUnk->Release();
FetchedIpType = ComIpType_Dispatch;
  1. QI to IDispatch - failed
COMPlusThrowHR(hr); // ????

ReqIpType = ComIpType_IUnknown

pvObj = pUnk;
FetchedIpType = ComIpType_Unknown;

@AaronRobinsonMSFT
Copy link
Member

@kant2002 Yes.

@kant2002
Copy link
Contributor Author

@AaronRobinsonMSFT is it possible that ComIpType_OuterUnknown would be passed to that location? Technically that will be handled by IUnknown case, but maybe there special processing needed.

@AaronRobinsonMSFT
Copy link
Member

@kant2002 I don't think that ComIpType_OuterUnknown should be a concern here. The ComWrappers API does support aggregation but at present I am not sure how we would integrate at this point. I am okay not dealing with it at present.

@kant2002
Copy link
Contributor Author

@AaronRobinsonMSFT then can you take a look?

Copy link
Member

@AaronRobinsonMSFT AaronRobinsonMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you.

@AaronRobinsonMSFT AaronRobinsonMSFT merged commit 8538a75 into dotnet:main May 30, 2021
@kant2002 kant2002 deleted the kant/split-variant-test branch May 31, 2021 09:38
thaystg added a commit to thaystg/runtime that referenced this pull request Jun 1, 2021
…asm_debugger_and_use_debugger_agent

* upstream/main: (597 commits)
  Fix42292 (dotnet#52463)
  [mono] Remove some obsolete emscripten flags. (dotnet#53486)
  Fixed path to projects (dotnet#53435)
  support ServerCertificateContext in quic (dotnet#53175)
  Socket: delete unix local endpoint filename on Close (dotnet#52103)
  [mono] Fix sgen_gc_info.memory_load_bytes (dotnet#53364)
  Refactor MsQuic's native IP address types. (dotnet#53461)
  Re-enabled optimizations for gtFoldExprConst (dotnet#53347)
  Add diagnostic support into sample app and AppBuilders on Mono. (dotnet#53361)
  Fix issues with virtuals and mdarrays (dotnet#53400)
  Split Variant marshalling tests (dotnet#53035)
  Update clrjit.natvis to cover GT_SIMD and GT_HWINTRINSIC (dotnet#53470)
  remove WSL checks in tests (dotnet#53475)
  Always spawn message loop thread for SystemEvents (dotnet#53467)
  add AcceptAsync cancellation overloads (dotnet#53340)
  Remove unnecessary reference to iOS workload pack in the Mono workload (dotnet#53425)
  Add CookieContainer.GetAllCookies (dotnet#53441)
  Remove DynamicallyAccessedMembers on JsonSerializer  (dotnet#53235)
  [wasm] Re-enable Wasm.Build.Tests (dotnet#53433)
  [libraries] Move library tests Feature Switches defaults to Functional tests (dotnet#53253)
  ...
@ghost ghost locked as resolved and limited conversation to collaborators Jun 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants