-
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
ServiceFabricProcessor: HardGetRuntimeInfoFailure failing on .NET Framework #5995
Comments
Filed a couple tracking issues: Azure#5995 Azure#5997
* Enable full signing for test libraries We were silently failing to run the tests on .NET Framework because the test assembly was delay-signed and the xunit test run just outputs a skipping message in this case which made the CI pass but we didn't actually run any tests on .NET Framework. * Disable some failing tests on .NET Framework Filed a couple tracking issues: #5995 #5997
Looks like we also have the following test failing at least sometimes:
|
Reported as fixed with #7446. As a result, closing this out. |
Reopening; this test has been failing intermittently in CI builds and also had nightly run failures. Marking to be ignored pending further investigation. |
For the record, this is a test issue in ServiceFabricProcessor which is still in preview. The entire CIT mechanism needs some work to make it more deterministic, and that will happen when we have time to start moving SFP toward GA. |
We are investigating this issue, and will report back with a status update by 11/4/2020. |
The Microsoft.Azure.EventHubs.ServiceFabricProcessor package is in preview and there are no plans for a stable release. This package will soon be deprecated and therefore we won't be taking any changes. |
Please remove the package from the test pipeline. |
Closing this out, as the package is no longer under active development and the tests are currently skipped (so no impact) unlikely to be fixed. |
When running the EventHubs tests on .NET Framework the HardGetRuntimeInfoFailure test fails.
The text was updated successfully, but these errors were encountered: