1
Vote

LogParser _artifacts folder missing

description

Hi!

Recently I tried to get started with Wolfpack and the LogParser. As there is no documentation yet, but hopefully will be there soon (?), I looked over the unit tests to find out how to use this thing.

However, the tests fail, as the test data is not checked in and therefore missing.

So could someone please check in the _artifacts folder?

See error:
Test Name:  ArtifactFileCreation(False,0)
Test FullName:  Wolfpack.Contrib.LogParser.Tests.EVTLogParserCheckSpecs.ArtifactFileCreation(False,0)
Test Source:    d:\Code\wolfpackcontrib_1ff73d439b4a\Solutions\HealthChecks\Wolfpack.Contrib.LogParser.Tests\EVTLogParserCheck.Specs.cs : line 26
Test Outcome:   Failed
Test Duration:  0:00:00,003

Result Message: System.IO.DirectoryNotFoundException : Could not find a part of the path 'D:\Code\wolfpackcontrib_1ff73d439b4a\Solutions\HealthChecks\Wolfpack.Contrib.LogParser.Tests\bin\Debug\_artifacts\TestCheck'.
Result StackTrace:  
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileSystemEnumerableIterator`1.CommonInit()
at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetFiles(String path)
at Wolfpack.Core.Testing.Domains.SystemDomainBase.ThereShouldBe_ArtifactFilesForCheck_(Int32 expected, String checkName) in c:\Projects\Wolfpack\Releases\v3.0.19\Source\Wolfpack.Core.Testing\Domains\SystemDomainBase.cs:line 111
at StoryQ.Operation.<>c__DisplayClass10`2.<Then>b__f()
at StoryQ.Infrastructure.Step.Execute()

-- End of original stack trace, test framework stack trace follows: --

at StoryQ.Infrastructure.FragmentBase.StoryQ.Infrastructure.IStepContainer.Execute(IRenderer[] renderers)
at StoryQ.Infrastructure.FragmentBase.ExecuteWithReport(MethodBase currentMethod)
at StoryQ.Infrastructure.FragmentBase.ExecuteWithReport()
at Wolfpack.Contrib.LogParser.Tests.EVTLogParserCheckSpecs.ArtifactFileCreation(Boolean generateArtifacts, Int32 expectedFiles) in d:\Code\wolfpackcontrib_1ff73d439b4a\Solutions\HealthChecks\Wolfpack.Contrib.LogParser.Tests\EVTLogParserCheck.Specs.cs:line 37

comments

jimbobdog wrote Oct 9, 2014 at 12:32 PM

Hmm, I'll take a look - this particular error looks like the Event Log parser ran ok but failed to write out an artefact (eg: its output) to the correct place (or didn't run and that is why the artefact file is missing).

"ThereShouldBe_ArtifactFilesForCheck_" assertion has failed.

Will investigate and report back. As for lack of docs yes, there will be some - I've been kinda tackling them as need arises so I will try to get the LogParser plugin page in the Contrib project completed now.

Cheers,
James

jimbobdog wrote Oct 9, 2014 at 1:03 PM

Interesting - I just ran the LogParser EVT tests and they all passed...I'll keep digging.

To use the LogParser plugin you need to install it into your Wolfpack installation (best way is to stop Wolfpack and open a cmd prompt at the install folder and type "wolfpack.agent.exe /update:Wolfpack.Contrib.LogParser".

That should install it and then restart Wolfpack. In a browser go to the UI configuration page, http://localhost:804/ui and it should appear as a new plugin - click create and configure it, Save and Accept changes - Wolfpack will restart and your check should be running.

Cheers,
James