-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
The given key 'size' was not present in the dictionary in coreclr libraries outerloop tests #87359
Comments
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=302240 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "System.Collections.Generic.KeyNotFoundException : The given key 'size' was not present in the dictionary.",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
|
Tagging subscribers to this area: @dotnet/area-system-formats-tar Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=302240 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "System.Collections.Generic.KeyNotFoundException : The given key 'size' was not present in the dictionary.",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
} Report
Summary
|
|
Note there's apparently two issues, the failure due to KeyNotFoundException , and the below. Might need the test to be looped. After fixing those, this test should probably become manual only, as it's running up against the 15 min timeout, even on release builds.
|
I had a look to see whether it's something simple. this should be adding the size to the dictionary, but at this point _size is zero so it doesn't.
that is here runtime/src/libraries/System.Formats.Tar/src/System/Formats/Tar/TarHeader.Write.cs Line 223 in 4720918
the size is not calculated and added to the extended attributes dictionary until here runtime/src/libraries/System.Formats.Tar/src/System/Formats/Tar/TarHeader.Write.cs Line 228 in 4720918
The 2nd failure mode is probably simply because its release mode and so it gets past the debug assert. Probably introduced by #76707 @jozkee and wasn't spotted as it's outerloop? |
thanks for taking a look, @danmoseley! it seems like the libraries outerloop has many errors. I did another PR that just triggers more background GCs with no other changes and it's still hitting many libraries outerloop failures (hard to say if it's hitting the exactly same issues since there isn't a convenient way to compare them when there are so many). |
Yeah, I'm not sure what the process currently is for keeping the outerloop clean (@ericstj ). Hopefully it's not too difficult to identify anything new you introduce. Most of these failures are pretty vanilla. |
it's actually not easy to identify new errors. as I mentioned, there isn't a convenient way to compare results - not that I know of anyway. and when Build Analysis does not categorize test failures it requires laboriously going through the tests marked as new to see if the failure on each test to see if it's actually a new error (not to mention Build Analysis does not necessarily give accurate results so that's already questionable). I've already spent a bunch of time on this so I think I will stop here. |
Unlike PR validation which will have a forcing function to stay clean, outerloop is only clean based on folks responding to and resolving bugs. @Maoni0 - are you needing to look in one particular area or are you trying to look across all areas? |
no one area. I'm thinking of making a change in GC so I'm just looking for some test runs that might uncover problems. |
#76707 I'm working on a fix. |
Passing |
Thanks @am11, I'll make sure to run those locally.
Not for this scenario, at least not easily. The It seems I introduced this bug when I merged the PR that refactored our Tar APIs to allow handling of unseekable data streams. The outerloop tests didn't run so I never caught the bug 😢 . 84a7be7 I'm currently testing the fix, will submit a PR soon. |
Tiny typo BTW: it's |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=302240
Build error leg or test failing:
System.Formats.Tar.Tests.TarWriter_WriteEntry_LongFile_Tests.WriteEntry_LongFileSize
System.Formats.Tar.Tests.TarWriter_WriteEntryAsync_LongFile_Tests.WriteEntry_LongFileSizeAsync
Pull request: #87311
Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=324045
Error message validated:
System.Collections.Generic.KeyNotFoundException : The given key 'size' was not present in the dictionary.
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 6/28/2023 9:23:56 PM UTC
The text was updated successfully, but these errors were encountered: