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

Support compilation and running unit tests on 64 bit Windows #24

Closed
xepaul opened this issue Jan 16, 2015 · 5 comments
Closed

Support compilation and running unit tests on 64 bit Windows #24

xepaul opened this issue Jan 16, 2015 · 5 comments

Comments

@xepaul
Copy link
Contributor

xepaul commented Jan 16, 2015

I'm not sure if its just me but I had issues running tests on 64 windows.
It would be good to fix this or at least put notes in the Dev and Test guides.

@KevinRansom
Copy link
Member

Which branch?
What were the issues?

Thanks

Kevin

@forki
Copy link
Contributor

forki commented Jan 16, 2015

I have 64bit Windows and tests run fine on current fsharp4 branch. But during the development of my nameof I broke the proto-compiler and saw really strange results. I recommend you clean every from your repo (git clean - xdf) and try from the beginning.

@xepaul
Copy link
Contributor Author

xepaul commented Jan 16, 2015

Ahh ok thanks. I had issues running the BuildTestTools.cmd with complains from ILComparerfsproj on the fsharp4 branch

@latkin
Copy link
Contributor

latkin commented Jan 16, 2015

@KevinRansom and I and many others are using x64 and aren't having trouble. Any other info you can provide? Can you try full clean + rebuild?

@dsyme
Copy link
Contributor

dsyme commented Jan 17, 2015

64-bit works for me

@latkin latkin closed this as completed Jan 19, 2015
liboz pushed a commit to liboz/visualfsharp that referenced this issue Nov 5, 2016
Reduce the diff on seq.fs so that it is easier to review on GitHub
KevinRansom pushed a commit that referenced this issue Jun 1, 2017
Try to clean up error text a little.
nojaf added a commit to nojaf/fsharp that referenced this issue Nov 30, 2022
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

No branches or pull requests

5 participants