Skip to content
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

Delete .NET Framework ildasm headers from test sources #68614

Merged
merged 1 commit into from
Apr 28, 2022

Conversation

jkotas
Copy link
Member

@jkotas jkotas commented Apr 27, 2022

No description provided.

@jkotas jkotas requested a review from marek-safar as a code owner April 27, 2022 19:21
@ghost ghost assigned jkotas Apr 27, 2022
@jkotas jkotas requested a review from ViktorHofer April 27, 2022 19:21
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.


// Microsoft (R) .NET Framework IL Disassembler. Version 4.7.3071.0
// Copyright (c) Microsoft Corporation. All rights reserved.
// Licensed to the .NET Foundation under one or more agreements.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it intentional that you aren't adding the license header to the src/mono/mono/tests/* files?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not know where these files came from originally. Adding the simple license headers may be actually wrong for them.

Also, nearly all files under src/mono/mono/tests/* are missing the license headers so it is also for consistency.

@am11
Copy link
Member

am11 commented Apr 27, 2022

Failure look like caused by some recent infra change. Many PRs are red because of that. Tests pass, then helix script fails to access log file. e.g. https://helix.dot.net/api/2019-06-17/jobs/a55267d4-9f85-4033-8c34-48fbafc7c010/workitems/LibraryImportGenerator.Unit.Tests/console

@alexperovich, @MattGal, could it be related to dotnet/arcade#8712? Helix SDK was updated 6 days ago: 2894f54.

@MattGal
Copy link
Member

MattGal commented Apr 27, 2022

Failure look like caused by some recent infra change. Many PRs are red because of that. Tests pass, then helix script fails to access log file. e.g. https://helix.dot.net/api/2019-06-17/jobs/a55267d4-9f85-4033-8c34-48fbafc7c010/workitems/LibraryImportGenerator.Unit.Tests/console

@alexperovich, @MattGal, could it be related to dotnet/arcade#8712? Helix SDK was updated 6 days ago: 2894f54.

I don't think that one's it, but for @stephentoub's recent suggestion I just filed dotnet/arcade#9208. I understand the issue now and have deleted the bad 3 machines, and I will take a quick stab at hardening against this shortly (otherwise we'll get someone to work on it soon)

@jkotas
Copy link
Member Author

jkotas commented Apr 28, 2022

All test failures are unrelated infrastructure issues.

@jkotas jkotas merged commit 43ec806 into dotnet:main Apr 28, 2022
@jkotas jkotas deleted the ildasm-headers branch April 28, 2022 00:51
@MattGal
Copy link
Member

MattGal commented Apr 28, 2022

All test failures are unrelated infrastructure issues.

How about this one? https://helixre8s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-68614-merge-223b1e7ae23b4e0ba4/EMSDK-.NoopNativeRebuildTest/1/console.f555469a.log?helixlogtype=result

I just figured it might have been missed, I noticed it while checking in on this bug. I've merged a change that should make the infra issue not repro in the future.

@jkotas
Copy link
Member Author

jkotas commented Apr 28, 2022

That one is #68393

@ghost ghost locked as resolved and limited conversation to collaborators May 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants