-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
WriteEntry_LongFileSize tests failing in CI #79773
Comments
Tagging subscribers to this area: @dotnet/area-system-io Issue Details
This is somewhat related to #77012. I run the test locally on my MacBook:
it seems like it takes more than hour for test to finish ... and that is pretty crazy IMHO.
|
@jozkee PTAL |
I do agree that the test takes too long, it is already marked as |
@jozkee I think a test which takes more than an hour to finish is too long even for OuterLoop. It should be ran manually only, we have that pattern for other cases already, e.g. |
Hmm though judging from your comment in #77012 (comment) the test took just ~8 minutes on your machine apparently, weird. |
That may depend on the filesystem. Some systems may have |
On CI we're also seeing it time out on Linux and I don't think there's any AV/security thing there though. |
I tried running the test locally (after #79899) on my intune'd Mac using Mono and Release config and it took just about 8 minutes too. |
The issue isn't reproing anymore. I'm not seeing the failure again in Kusto. I'll close this. |
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-79652-merge-27087af8ec1f4aff89/System.Formats.Tar.Tests/1/console.cd22a1da.log?helixlogtype=result
This is somewhat related to #77012. I run the test locally on my MacBook:
it seems like it takes more than hour for test to finish ... and that is pretty crazy IMHO.
We should either disable this or at least consider
IgnoreForCI
.The text was updated successfully, but these errors were encountered: