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

Fork Xunit Console Runner to Arcade #1613

Closed
4 of 5 tasks
josalem opened this issue Dec 17, 2018 · 15 comments
Closed
4 of 5 tasks

Fork Xunit Console Runner to Arcade #1613

josalem opened this issue Dec 17, 2018 · 15 comments
Assignees
Labels

Comments

@josalem
Copy link
Contributor

josalem commented Dec 17, 2018

This issue is for tracking work on forking the xunit console runner.

Reason

The current xunit console runner (v2.4.x) is no longer maintained, so we will be forking the code for longer term maintenance and feature updates until a viable alternative presents itself.

TODO

CC - @ViktorHofer

@josalem
Copy link
Contributor Author

josalem commented Dec 17, 2018

@BruceForstall

@josalem josalem self-assigned this Dec 17, 2018
@BruceForstall
Copy link
Member

cc @echesakovMSFT

@BruceForstall
Copy link
Member

cc @RussKeldorph

@echesakov
Copy link

@jashook @sbomer

@jashook
Copy link

jashook commented Jan 9, 2019

Adding more people who may be interested @dotnet/jit-contrib @safern

@safern
Copy link
Member

safern commented Jan 9, 2019

cc: @danmosemsft

@BruceForstall
Copy link
Member

@ViktorHofer @josalem Now that #1627 is merged, what is the plan for addressing the bugs/issues referenced above?

@josalem
Copy link
Contributor Author

josalem commented Jan 18, 2019

There isn't a plan in place yet. We could create a label for xunit runner issues and create issues/PRs with that label. That will give us a nice view of what work needs to be done since I'm sure I'm missing a few in the checklist above. I was planning on tackling the response files work (dotnet/buildtools#2035) that @A-And added to the old custom runner in the near future.

@ViktorHofer
Copy link
Member

We aren't using this runner in corefx for netcoreapp and netfx right now as there is no necessity to do so but if it's blocking when can switch over to it. Right now we use a repackaged version of it for uap (UWP console app) and uapaot (netcoreapp2.0 + WINDOWS_UWP constant).

@echesakov
Copy link

@josalem @ViktorHofer Can you please tell how far we are from getting this fork published to NuGet?

I have a fix xunit/xunit#1846 that I would like port to the fork and consume the fork version of xunit.console.dll in coreclr when publishing jobs to Helix.

@echesakov
Copy link

/cc @RussKeldorph

@josalem
Copy link
Contributor Author

josalem commented Mar 27, 2019

As far as I'm aware, this should already be available as a pacakge on the NuGet feed that Arcade puts its build outputs in (based on this doc). It should be in the dotnet-feed NuGet feed.

Should be under the name Microsoft.DotNet.XUnitConsoleRunner at version 2.5.0. It still outputs xunit.console.dll, so scripts shouldn't need to change, just the package name.

@echesakov
Copy link

@josalem Thanks!

@josalem
Copy link
Contributor Author

josalem commented Nov 6, 2019

Is this issue needed anymore? I think the work above was completed a long while ago.

@ViktorHofer
Copy link
Member

Thanks, closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants