Skip to content

Conversation

@forki
Copy link
Contributor

@forki forki commented Nov 29, 2016

I used this to fix bugs that are not reproducible on my system.

I wonder if we can upload the .err file to jenkins instead of tracing it

@forki forki force-pushed the fsdiff branch 3 times, most recently from 2586e29 to ac40cf8 Compare November 29, 2016 15:05
@dsyme
Copy link
Contributor

dsyme commented Nov 29, 2016

We should really just remove all calls to fsdiff (at least from FSHarpSuite) and use direct calls to the logic. THere's only pain in having this exe.

I'm not sure if it's used by the FSharpQA suite too though

@forki
Copy link
Contributor Author

forki commented Nov 29, 2016

Good point. Will try to do that. That code looks like it's in need of a big clean up anyways

@forki forki force-pushed the fsdiff branch 4 times, most recently from 46dd05f to 53b8637 Compare December 5, 2016 15:19
@forki
Copy link
Contributor Author

forki commented Dec 5, 2016

@enricosada could you please review this? thx

@forki forki changed the title WIP Trace errors in from fsdiff Trace errors in from fsdiff Dec 5, 2016
@enricosada
Copy link
Contributor

@forki seems ok 👍
As a note, for language sensitive tests (with diff usually) we can also pass --preferreduilang:en to fsc, that should fix for everyone (like me in italian)

@forki
Copy link
Contributor Author

forki commented Dec 5, 2016

@dsyme can we get this in? would help to understand errors in ci_part2

@dsyme dsyme merged commit 12213ce into dotnet:master Dec 5, 2016
@dsyme
Copy link
Contributor

dsyme commented Dec 5, 2016

Sure

@forki forki deleted the fsdiff branch December 5, 2016 17:28
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.

4 participants