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

xUnit use relative path for output dir #798

Closed

Conversation

neoeinstein
Copy link
Contributor

A rooted *nix path (beginning with /) is interpreted by the xUnit runner as a command line directive. This causes the xUnit runner to fail when report directories are specified when building on Mono.

A rooted *nix path (beginning with /) is interpreted by the
xUnit runner as a command line directive. This causes the xUnit
runner to fail when report directories are specified when
building on Mono.

Fixes fsprojects#568
@neoeinstein neoeinstein force-pushed the xunit-with-reports-on-mono branch from 055b823 to 0fe3c73 Compare May 15, 2015 15:33
@neoeinstein
Copy link
Contributor Author

I used the FAKE build as a guinea pig to test this since it already has an xunit task as part of the build. When copying the built FakeLib.dll into the FAKE tools directory and re-running the build, it appropriately uses the relative paths.

I have a separate commit which I can also add that will cause FAKE to begin generating xUnit HTML reports into the reports directory, but as that breaks the Travis-CI build (at least until FAKE uses a version of FAKE which includes #798), I've withheld that commit.

@neoeinstein neoeinstein mentioned this pull request May 16, 2015
@neoeinstein
Copy link
Contributor Author

Superceded by #800

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.

1 participant