-
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
[macOS-arm64] 55 System.DirectoryServices.Protocols.Tests fail on CoreCLR #49105
Comments
fixed by #51205 |
I would assume I disabled these tests, but I don't see the DisableTest tag or a reference to the method where I disabled it... I am going to reopen it, assign it to myself to make sure these tests are enabled. Thanks @sandreenko |
They were disabled as part of #49400. |
Looks like they were reenabled by #51205. |
Some of failed tests:
|
Interesting, so they are failing where they were not disabled previously (arm64 Linux, no MacOS), and they did not fail in the CI for the PR and the BER testing that was done, not sure what is going on. |
It looks like it is passing on x64 Unix/OSX, but does not pass on arm64 Unix/OSX. I can't find the former pipelines that were running arm64 OSX so can't check there. |
@sandreenko The libraries tests are not enabled on PRs right now. They are only on rolling builds. I am not sure if they are inner or outer. If you want to trigger those runs manually, I can probably figure out where the pipeline is... |
Yes, I am searching for a pipeline that runs arm64 MacOS libraries tests, would be nice if you can point me to it. |
The libraries innerloop test are run in the runtime rolling CI builds. Here https://dev.azure.com/dnceng/public/_build/results?buildId=1114297&view=results The libraries outerloop tests are run here https://dev.azure.com/dnceng/public/_build?definitionId=678. Unlike the runtime tests, for libraries the inner and outer loop sets are non overlapping. Outer is not a superset of inner (like it is for runtime tests) |
Does it include the test run? I see only Libraries Build jobs there. |
The libraries tests can be run as part of the build job. https://dev.azure.com/dnceng/public/_build/results?buildId=1113767&view=results The osx one did too. It didn't have failures so I had to show passed tests in the tests tab to verify. |
I see, thanks Steve, looks like in some pipelines we have "Libraries Test Run" where we run libraries tests, like: https://dev.azure.com/dnceng/public/_build/results?buildId=1114559&view=logs&j=ba66422d-a35c-5bc8-b6c6-3a55f049cbee |
notes for me:
|
See https://dev.azure.com/dnceng/public/_build/results?buildId=1021947
First few failures.
/cc @sandreenko These look a bit like ABI issues.
The text was updated successfully, but these errors were encountered: