Skip to content

Do not use Taskbar on Containers. #2546

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

Conversation

weidingerhp
Copy link

Experienced the following when running Benchmarks on Windows Containers with BenchmarkDotNet 0.13.8.

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {56FDF344-FD6D-11D0-958A-006097C9A090} failed due to the following error: 80040154 Class not registered (0x80040154 (REGDB_E_CLASSNOTREG)).
at BenchmarkDotNet.Helpers.TaskbarProgressCom..cctor()
--- End of inner exception stack trace ---
at BenchmarkDotNet.Helpers.TaskbarProgressCom.SetState(IntPtr consoleWindowHandle, IntPtr consoleHandle, TaskbarProgressState taskbarState)
at BenchmarkDotNet.Helpers.TaskbarProgress.Dispose()
at BenchmarkDotNet.Running.BenchmarkRunnerClean.Run(BenchmarkRunInfo[] benchmarkRunInfos)
at BenchmarkDotNet.Running.BenchmarkRunner.RunWithDirtyAssemblyResolveHelper(BenchmarkRunInfo[] benchmarkRunInfos)
at BenchmarkDotNet.Running.BenchmarkRunner.<>c__DisplayClass5_0.<Run>b__0()
at BenchmarkDotNet.Running.BenchmarkRunner.RunWithExceptionHandling(Func`1 run)
at BenchmarkDotNet.Running.BenchmarkRunner.Run(BenchmarkRunInfo benchmarkRunInfo)

Setting the ENV-Variable should fix that issue.

@timcassell
Copy link
Collaborator

I think this should be fixed by #2255 (still waiting on review).

@weidingerhp
Copy link
Author

I think this should be fixed by #2255 (still waiting on review).

Cool, thanks.

Sorry, but did not see your PR before.

@weidingerhp
Copy link
Author

Closing because this should be fixed with #2255.

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.

2 participants