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

Win32Exception when trying to benchmark #6

Closed
sidristij opened this issue May 16, 2015 · 12 comments
Closed

Win32Exception when trying to benchmark #6

sidristij opened this issue May 16, 2015 · 12 comments

Comments

@sidristij
Copy link

After updating to 0.7.* having exception when launching benchmark.

http://i.imgur.com/3srpxqo.png

@AndreyAkinshin
Copy link
Member

I have updated BenchmarkDotNet in dotnetex to v0.7.4. Now it works fine on my computer. Please, check it.

@sidristij
Copy link
Author

Nope, continuing failing with same error. Tried as Admin, result the same.

@AndreyAkinshin
Copy link
Member

Do you have MSBuild in the %PATH% variable? If not, you should add it because BenchmarkDotNet use it for building each benchmark.

@AndreyAkinshin
Copy link
Member

Is it works now?

@danilanv
Copy link

danilanv commented Jun 4, 2015

Had the same issue, but when added MSBuild to %PATH% the problem with Win32Exception disapeared, but now a i have another problem: when i run benchmark i have next error:
Target competition: Crc16Bench
// ***** Competition: Start *****
// Found benchmarks:
// Crc16Bench_Data4_Throughput_X64_CurrentJit_NET-Current -w=5 -t=10
// Crc16Bench_Data4_Throughput_X86_CurrentJit_NET-Current -w=5 -t=10

// **************************
// Benchmark: Crc16Bench_Data4 (Throughput_X64_CurrentJit_NET-Current) [-w=5 -t=10]
// Generated project: c:\Users\danila\Documents\Visual Studio 2013\Projects\Crc16Benchmark\Crc16Bench\bin\Release\Crc16Bench_Data4_Throughput_X64_CurrentJit_NET-Current

// Build:
Build failed
Fail

// Run, Process: 1 / 3
// Platform=X64
// Run, Process: 2 / 3
// Platform=X64
// Run, Process: 3 / 3
// Platform=X64

AverageTime (ns/op): Median = 0; StdDev = Infinity; Min = 0; Max = 0;
OperationsPerSecond: Median = 0; StdDev = Infinity; Min = 0; Max = 0;

// **************************
// Benchmark: Crc16Bench_Data4 (Throughput_X86_CurrentJit_NET-Current) [-w=5 -t=10]
// Generated project: c:\Users\danila\Documents\Visual Studio 2013\Projects\Crc16Benchmark\Crc16Bench\bin\Release\Crc16Bench_Data4_Throughput_X86_CurrentJit_NET-Current

// Build:
Build failed
Fail

// Run, Process: 1 / 3
// Platform=X86
// Run, Process: 2 / 3
// Platform=X86
// Run, Process: 3 / 3
// Platform=X86

AverageTime (ns/op): Median = 0; StdDev = Infinity; Min = 0; Max = 0;
OperationsPerSecond: Median = 0; StdDev = Infinity; Min = 0; Max = 0;

// ***** Competition: Finish *****

// BenchmarkDotNet=v0.7.4.0
// OS=Microsoft Windows NT 6.1.7601 Service Pack 1
// Processor=Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz, ProcessorCount=4
// CLR=MS.NET 4.0.30319.18444, Arch=64-bit
Common: Type=Crc16Bench Method=Data4 Mode=Throughput Jit=CurrentJit .NET=Current

Platform AvrTime StdDev op/s
X64 0.000000 ns Infinity s 0
X86 0.000000 ns Infinity s 0

// ***** Competition: End *****

@damageboy
Copy link
Contributor

Same here...

@olsh
Copy link

olsh commented Jun 5, 2015

@danilanv
You have to remove white spaces, cyrillic symbols etc. in the solution path.
I suppose the second argument should be enclosed in quotes.

@damageboy
Copy link
Contributor

@olsh @danilanv I solve my issue as well, for me it was actually the fact the benchmark class was an inner class, which caused BenchMarkDotNet to generate wierd class names with + in the class name...

@AndreyAkinshin
Copy link
Member

@mumusan, @danilanv, @damageboy , @olsh
I have implemented new build system via API from the Microsoft.Build assembly. Please, check version 0.7.5.

@danilanv
Copy link

version 0.7.5 - it works!

@damageboy
Copy link
Contributor

Same for me, nicer integration with Life(tm)

@AndreyAkinshin
Copy link
Member

@danilanv, @damageboy, great!

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