Skip to content

Conversation

@RikkiGibson
Copy link
Member

RikkiGibson and others added 30 commits November 8, 2024 15:56
* Rename parser method

* Cleanup

* Inline methods

* Share

* fix

* Docs

* rename

* Remove unnecessayr check

* Update src/Compilers/CSharp/Portable/Parser/LanguageParser.cs

Co-authored-by: Rikki Gibson <[email protected]>

* Fix

* Cleaner

* Update src/Compilers/CSharp/Portable/Parser/LanguageParser.cs

Co-authored-by: Rikki Gibson <[email protected]>

* Apply suggestions from code review

---------

Co-authored-by: Rikki Gibson <[email protected]>
@RikkiGibson RikkiGibson requested review from a team as code owners March 27, 2025 16:34
@ghost ghost added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Mar 27, 2025
@RikkiGibson RikkiGibson requested a review from jaredpar March 27, 2025 16:34
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi left a comment

Choose a reason for hiding this comment

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

IDE side lgtm.

@RikkiGibson
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@RikkiGibson
Copy link
Member Author

RikkiGibson commented Mar 27, 2025

Between the PR branch run and feature branch rolling run, the macOS tests are failing on multiple attempts.

image

It's a few VB tests that are failing:

  • Microsoft.CodeAnalysis.VisualBasic.UnitTests.Semantics.BinaryOperators.Test5_DateConst
  • Microsoft.CodeAnalysis.VisualBasic.UnitTests.Semantics.BinaryOperators.Test1_Date

This is unlikely to be an issue with the feature, but, I want to take care we don't introduce a weird failure to main, which is not already there. Possibly an with GitHub grouping CI runs by head SHA is in the mix here making things weird as well.

@jjonescz
Copy link
Member

macOS leg shouldn't be running on PRs and i think it's not a "required" CI check so you can probably ignore it failing; otherwise you might need to merge main back here, because there were some failing tests that needed to be skipped - see 53062f4

@RikkiGibson
Copy link
Member Author

there were some failing tests that needed to be skipped

The tests we skipped in main, are exactly the ones failing here, so it sounds like we will not break main by merging here. Thanks!

@RikkiGibson RikkiGibson merged commit 2437c72 into main Mar 27, 2025
22 of 41 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Mar 27, 2025
@jjonescz jjonescz modified the milestones: Next, 17.14 P3 Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead VSCode

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants