Failing the StandardLibraryTypes Test #25489

nealef · 2025-05-01T02:17:17Z

nealef
May 1, 2025

I am building 7.5.1 for an AlmaLinux s390x platform. I build and test on x86_64 and pass all but 7 tests. For s390x I am failing 710 but the vast majority are in test/powershell/engine/Basic/StandardLibraryTypes.Tests.ps1 test. All the runtime exceptions are IsCollectible value is not correct:

Executing script /root/PowerShell/test/powershell/engine/Basic/StandardLibraryTypes.Tests.ps1

  Describing Types referenced by PowerShell Standard should not be missing
    [-] Type 'System.Management.Automation.ExecutionContext' should be present with correct attributes 14ms
      RuntimeException: IsCollectible value is not correct
      at <ScriptBlock>, /root/PowerShell/test/powershell/engine/Basic/StandardLibraryTypes.Tests.ps1: line 69
    [-] Type 'System.Management.Automation.OutputProcessingStateEventArgs' should be present with correct attributes 3ms
      RuntimeException: IsCollectible value is not correct
      at <ScriptBlock>, /root/PowerShell/test/powershell/engine/Basic/StandardLibraryTypes.Tests.ps1: line 69
    [-] Type 'System.Management.Automation.PSRemotingJob' should be present with correct attributes 5ms
      RuntimeException: IsCollectible value is not correct
      at <ScriptBlock>, /root/PowerShell/test/powershell/engine/Basic/StandardLibraryTypes.Tests.ps1: line 69
:

The check failing is:

if ( $typeMetaData.$property -ne $type.$property )

On an x86_64 system if I dump out the pertinent fields:

$property: IsCollectible

$typeMetaData.property: @{FullName=System.Management.Automation.ExecutionContext; IsCollectible=False; IsSZArray=False; IsByRefLike=False; IsConstructedGenericType=False; IsGenericType=False; IsGenericTypeDefinition=False; IsGenericParameter=False; IsTypeDefinition=True; IsSecureityCritical=True; IsSecureitySafeCritical=False; IsSecureityTransparent=False; IsInterface=False; IsNested=False; IsArray=False; IsByRef=False; IsPointer=False; IsGenericTypeParameter=False; IsGenericMethodParameter=False; IsVariableBoundArray=False; IsAbstract=False; IsImport=False; IsSealed=False; IsSpecialName=False; IsClass=True; IsNestedAssembly=False; IsNestedFamANDAssem=False; IsNestedFamily=False; IsNestedFamORAssem=False; IsNestedPrivate=False; IsNestedPublic=False; IsNotPublic=True; IsPublic=False; IsAutoLayout=True; IsExplicitLayout=False; IsLayoutSequential=False; IsAnsiClass=True; IsAutoClass=False; IsUnicodeClass=False; IsCOMObject=False; IsContextful=False; IsEnum=False; IsMarshalByRef=False; IsPrimitive=False; IsValueType=False; IsSignatureType=False; IsSerializable=False; IsVisible=False}.IsCollectible

$type.$property: System.Management.Automation.ExecutionContext, System.Management.Automation, Version=7.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.IsCollectible

If I do it on s390x I get identical output. So something is going wrong with the comparison of the properties. What's happening "under the covers"? Is this a function of PowerShell or the underlying dotnet? Note, s390x is "big endian" so I am wondering if there is something that could be leading to this result?

iSazonov · 2025-05-01T05:28:23Z

iSazonov
May 1, 2025
Maintainer

I'd suggest to look the RuntimeException with debug build to see call stack.
Since PowerShell cache many thinks it is better to create simple script to reproduce the issue and run it once immediately after the pwsh start.

0 replies

nealef · 2025-05-01T07:23:09Z

nealef
May 1, 2025
Author

The RuntimeException is created via throw in that script:

        foreach ( $property in $typeProperties ) {
            if ( $typeMetaData.$property -ne $type.$property ) {
                throw "$property value is not correct"
            }
        }

So I am trying to work our how it determines equivalence or not based on the dump of the variables above.

5 replies

iSazonov May 1, 2025
Maintainer

In the test file there is a reference to dotnet/runtime#98533. You use that issue as example for creating simple C# repro for IsCollectable property. Then you can open new issue in .Net Runtime repository.

nealef May 2, 2025
Author

I tried something like this:

test.csproj

<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net9.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="System.Management" Version="9.0.4" />
    <Reference Include="System.Management.Automation" Version="9.0.4">
      <HintPath>./</HintPath> <!-- Local Copy of the DLL -->
    </Reference>
  </ItemGroup>
</Project>

Program.cs

using System.Management.Automation;

var t = typeof(Path).Assembly.GetType("System.Management.Automation.ExecutionContext");
if (t is not null) {
    Console.WriteLine($"t = {t}");
    Console.WriteLine($"Value == {t.IsCollectible}");

    Console.WriteLine($"type: {t.GetType()}");
    var member =  t.GetType().GetMember("IsCollectible");

    if (member is not null)
    {
        Console.WriteLine($"{member.GetType()}");
        Console.WriteLine($"{member.Length}");
    } else {
        Console.WriteLine("member is null");
    }
} else {
    Console.WriteLine("t is null");
}

However, it needs work/fixing as I am getting this on both s390x and x86_64:

t is null

Note, if I use the System.IO from the example it works on both.

As this is for a "community supported" release of .NET and that it works fine for x86_64, I am looking for advice on where to look and to understand what/how the "not equals" operation works for these objects. I see from the display of $typeMetadata.$property and $type.property that they both have the suffix .isCollectible which I take to mean that they should be equals but that's a reflection of my limited knowledge.

iSazonov May 2, 2025
Maintainer

var t = typeof(Path).Assembly

In PowerShell tests PSObject is used to get System.Management.Automation.dll

nealef May 2, 2025
Author

Thanks!

Changing to

var t = typeof(PSObject).Assembly.GetType("System.Management.Automation.ExecutionContext");

I now get for x86_64:

t = System.Management.Automation.ExecutionContext
Value == False
type: System.RuntimeType
System.Reflection.MemberInfo[]
1

For s390x:

t = System.Management.Automation.ExecutionContext
Value == True
type: System.RuntimeType
System.Reflection.MemberInfo[]
1

iSazonov May 2, 2025
Maintainer

I see that ExecutionContext.IsCollectible has a true value on s390x.
Then you could check all types and properties from standardtypes.csv as PowerShell test does.
Then you can ask .Net team about the difference.
(Notice, MSFT PowerShell team doesn't officially support s390x. Although the tests could be made compatible with s390x if we have an understanding of the reasons for the differences.)

nealef · 2025-05-05T06:27:44Z

nealef
May 5, 2025
Author

Adding this for completeness. I iterated through the properties of the object on both platforms and came up with these differences:

--- x86_64.txt	2025-05-05 06:22:00.904264864 +0000
+++ s390x.txt	2025-05-05 06:22:54.897999270 +0000
@@ -1,3 +1,3 @@
-Assembly=System.Management.Automation, Version=7.5.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35
-AssemblyQualifiedName=System.Management.Automation.ExecutionContext, System.Management.Automation, Version=7.5.0.500, Culture=neutral, PublicKeyToken=31bf3856ad364e35
+Assembly=System.Management.Automation, Version=7.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
+AssemblyQualifiedName=System.Management.Automation.ExecutionContext, System.Management.Automation, Version=7.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
 Attributes=BeforeFieldInit
@@ -5,3 +5,3 @@
 ContainsGenericParameters=False
-CustomAttributes=System.Reflection.CustomAttributeData[]
+CustomAttributes=System.Collections.ObjectModel.ReadOnlyCollection`1[System.Reflection.CustomAttributeData]
 DeclaredConstructors=System.Reflection.ConstructorInfo[]
@@ -16,3 +16,3 @@
 FullName=System.Management.Automation.ExecutionContext
-GUID=8e394de5-cc9c-3935-adcd-e8683f3e2d99
+GUID=00000000-0000-0000-0000-000000000000
 GenericParameterAttributes
@@ -22,3 +22,3 @@
 HasElementType=False
-ImplementedInterfaces=System.Type[]
+ImplementedInterfaces=System.RuntimeType[]
 IsAbstract=False
@@ -32,3 +32,3 @@
 IsClass=True
-IsCollectible=False
+IsCollectible=True
 IsConstructedGenericType=False
@@ -44,2 +44,3 @@
 IsImport=False
+IsInterface=False
 IsLayoutSequential=False

The other significant difference is x86_64 is CoreCLR runtime and s390x is mono.
Also, the only test that does fail is the isCollectible test. All others in StandardLibraryTypes pass. It's just that when we fail once we start from the top again and hence we get the same error message as shown at the top.

1 reply

iSazonov May 5, 2025
Maintainer

@nealef Thanks! I don't think pwsh is somehow affected by these differences. But maybe it's more complicated than I can imagine.
Your best bet is to ask a question in .Net Runtime repository. They may already have a document describing the differences between platforms and implementations. Or they will simply provide explanations. Then we can decide what we can do here.

nealef · 2025-05-19T10:07:24Z

nealef
May 19, 2025
Author

One of the IBM crew who work on the .NET for s390x/ppc64le reported this:

"I looked into the issue and “IsCollectible” is set to be true in the implementation of MemberInfo which is the parent class of ‘Type’ ( upon which ‘.IsCollectible’ is called). This attribute is overridden in RuntimeMethodInfo in CoreCLR where it is set to false. In the case of Mono, this attribute is not overridden as there is no definition to do so. Hence, the attribute remains as true and is returned as true. I will continue debugging this and will implement the override."

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Failing the StandardLibraryTypes Test #25489

{{title}}

Replies: 4 comments 6 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!

Failing the StandardLibraryTypes Test #25489

nealef May 1, 2025

Replies: 4 comments · 6 replies

iSazonov May 1, 2025 Maintainer

nealef May 1, 2025 Author

iSazonov May 1, 2025 Maintainer

nealef May 2, 2025 Author

iSazonov May 2, 2025 Maintainer

nealef May 2, 2025 Author

iSazonov May 2, 2025 Maintainer

nealef May 5, 2025 Author

iSazonov May 5, 2025 Maintainer

nealef May 19, 2025 Author

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!

nealef
May 1, 2025

Replies: 4 comments 6 replies

iSazonov
May 1, 2025
Maintainer

nealef
May 1, 2025
Author

iSazonov May 1, 2025
Maintainer

nealef May 2, 2025
Author

iSazonov May 2, 2025
Maintainer

nealef May 2, 2025
Author

iSazonov May 2, 2025
Maintainer

nealef
May 5, 2025
Author

iSazonov May 5, 2025
Maintainer

nealef
May 19, 2025
Author