Skip to content

Avoid using "1" as a test assembly name in VB NoPia tests#80689

Merged
AlekseyTs merged 1 commit intodotnet:mainfrom
AlekseyTs:Issue80686
Oct 14, 2025
Merged

Avoid using "1" as a test assembly name in VB NoPia tests#80689
AlekseyTs merged 1 commit intodotnet:mainfrom
AlekseyTs:Issue80686

Conversation

@AlekseyTs
Copy link
Contributor

Closes #80686.

@AlekseyTs AlekseyTs requested a review from a team as a code owner October 14, 2025 02:39
@AlekseyTs AlekseyTs added Area-Compilers Test Test failures in roslyn-CI labels Oct 14, 2025
Copy link
Member

@333fred 333fred left a comment

Choose a reason for hiding this comment

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

What about the name 1 causes an issue here?

@AlekseyTs
Copy link
Contributor Author

What about the name 1 causes an issue here?

I have no idea. I found this out by comparing similar C# and VB tests and making changes that eliminate differences

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Compilers Test Test failures in roslyn-CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

21 VB NoPia tests fail locally with "[HRESULT 0x8007000B] - An attempt was made to load a program with an incorrect format."

5 participants