-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
System.Security.Cryptography.OpenSsl.Tests failing on CI runs #2176
Comments
This was supposed to be fixed by @ilyas1974 already. OpenSSL was not installed correctly. He installed it now in all the OSX machines. @ilyas1974 could you please follow up in this? |
Yes, I will follow up on what is going on with these systems. |
@ilyas1974 I haven't seen this failure anymore, did you follow up? I just want to confirm we can close this issue. |
Apologize for not updating this thread early. DDFUN is currently working on going though all the systems to verify this functionality. Their work item for this task can be for at http://ddweb/TechEase/TicketEdit.aspx?id=1636188. I believe a majority of the systems have OpenSSL configured properly - there are a few that do not (what will be resolved with the associated work item. |
No problem. Would you mind getting back whenever this is finished so that we can close this issue? |
Hit by #31641 |
This is being hit in rolling CI builds as well: @ilyas1974 what's the status on this? |
Reaching out to DDFUN as they are performing the work to get the current status on this. |
We have reached out to the tech and are currently waiting for a reply. I should have an update for you on the current status by tomorrow morning. /cc @JpratherMS |
@JpratherMS, is there an update on the status of the OpenSSL work? Last I heard there were only about 6 systems that were not configured correctly. If we can get that list, I can remove them from rotation until DDFUN is able to fix the OpenSSL issues. |
The affected machines have been fixed, please let me know if this issue persists. |
Thanks @JpratherMS and @ilyas1974 -- I'm going to close this issue and if someone hits it again we can re-open. |
@JpratherMS just happened again on: |
Thanks for reaching out, we found an issue with our process in discovering the ones that are not configured correctly. We are working on resolving that now, I will update again when that is completed. |
I am seeing other
From #31772 |
Yes it is the same error, mono just crashes in a different way and prints the whole call stack, but it is caused by the same: Thanks @ahsonkhan |
Looks like right now this is failing 14% of all runtime jobs: CI and PRs. Particularly though it's for OSX10.13 and OSX10.14. Think at this point we need to pull those configurations until we can get the underlying issue fixed. |
I was already working on that, talked with @JpratherMS offline and he hopes the work to update the machines will be done by EOD. He will update if so, if it is not ready I'll put up my PR to disable the affected tests on OSX. |
Apologies for the delay in getting this resolved, we had some miscommunication on our side and we are going through the rest of the machines to fix them. ETA is tomorrow morning. |
If this isn't fixed by EOD, I'd really appreciate disabling the tests. I'm hitting this constantly, even sometimes on multiple re-runs. I hit it just a little while ago, so at least as of this afternoon it is still not fixed. |
Thanks @CoffeeFlux... Do you have the build when you hit it? @JpratherMS I guess this got delayed a little bit ? |
I've been seeing it frequently on #31814 - I think this time it took 3 runs to get it green? Looks like Koplinger hit it a few hours ago as well. |
I updated the failed build list for all the failures since last night. Looks like it's hit a number of new PRs. |
@JpratherMS where is the core-eng issue we're using to track the OSX configuration update? |
I've put: #31879 to disable them on OSX. |
We have people actively working on fixing these. We are close but there are quite a few machines to manually check and resolve. |
@JpratherMS do we have an ETA? To see if it is worth merging my PR to disable. |
I believe we are very close, just rerunning the automation to verify now. |
@JpratherMS is this done? I would like to re-enable the tests. |
Apologies, yes this has been completed. Please enable and test and let me know if you see further issues |
Thanks @JpratherMS will put up a PR to do so. |
Tests are crashing on several OSX runs
Builds
Test Runs
The text was updated successfully, but these errors were encountered: