Skip to content

correct path to BuildResultAnalysisTests.csproj #2328

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

Merged
merged 12 commits into from
Jul 2, 2025

Conversation

wfurt
Copy link
Contributor

@wfurt wfurt commented Jul 1, 2025

This change has four parts.

  • fix tests failing like
C:\h\w\A6DA08F1\w\B6DB0A24\e>dotnet exec --roll-forward Major --runtimeconfig TestAggregatorHelixTests.runtimeconfig.json --depsfile TestAggregatorHelixTests.deps.json C:\h\w\A6DA08F1\p/xunit-runner/tools/netcoreapp2.0/xunit.console.dll TestAggregatorHelixTests.dll -nocolor -xml testResults.xml  
The specified runtimeconfig.json [TestAggregatorHelixTests.runtimeconfig.json] does not exist

this seems to be caused by .NET upgrade and its behavior SDK change

  • actually fixes the paths locations. It seems like we use singular instead of plural in sever places and that was causing pipeline warnings and "dotnet build" does not work from top directory.

  • it also updates some package and dotnet versions. 3.1 is no longer needed and I sync everything up with runtime 8.0 branch. (to avoid begging on 10.x bleeding edge)

  • it can take a while to get Helix run our jobs. The old one would run every in sequence so when wait Tims is 20-30 minutes it can take long time. Since the tests are independent I split them to 3 Jons so they can execute in parallel.

@missymessa
Copy link
Contributor

Build Analysis isn't showing the failures like expected, so this will not allow the Helix Scenario test to pass: https://github.com/maestro-auth-test/build-result-analysis-test/pull/2283/checks?check_run_id=44503189742

@missymessa missymessa merged commit 901d11b into maestro-auth-test:main Jul 2, 2025
5 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants