xdp-for-windows icon indicating copy to clipboard operation
xdp-for-windows copied to clipboard

Logs Don't Include Test Events

Open nibanks opened this issue 2 years ago • 0 comments

The logs that are collected from test failures should include at least a minimal number of events from the test code, such as test failures. I think the easiest way to achieve this is to update LogTestFailure and LogTestWarning to write the same console output to ETW/WPP.

Without this, the unfamiliar (me) cannot figure out where to look for failures. For instance, in this test failure:

XskNotifySocket(Xsk.Handle.get(), NotifyFlags, WaitTimeoutMs, &NotifyResult) not equal to HRESULT_FROM_WIN32(ERROR_TIMEOUT)
  Failed GenericXskWaitRxTx [1 s]
  Error Message:
   Assert failed. Stop test execution.
  Stack Trace:
  	at StopTest() in D:\a\1\s\test\functional\taef\tests.cpp:line 24
	at GenericXskWait() in D:\a\1\s\test\functional\lib\tests.cpp:line 3551
	at xdpfunctionaltests::GenericXskWaitRxTx() in D:\a\1\s\test\functional\taef\tests.cpp:line 217
  Standard Output Messages:
 XskNotifySocket(Xsk.Handle.get(), NotifyFlags, WaitTimeoutMs, &NotifyResult) not equal to HRESULT_FROM_WIN32(ERROR_TIMEOUT)

I downloaded the logs (xdpfunc.txt) but cannot figure out where to find what the actual return of XskNotifySocket is, let alone why it was that.

nibanks avatar Jul 18 '22 14:07 nibanks