Topic: Log - error report  (Read 912 times)

Log - error report
« on: July 13, 2018, 07:49:02 AM »

NIKZZZZ

  • Code Baker
  • Chef
  • ***
  • Date Registered: Feb 2011
  • Posts: 129
Hi, ied206.
Incorrect output of information about the error in the log file.
Example:
Code: [Select]
<Errors>
- [1] Error in Script [Build Core] (Win10XPE\Core.script)
[Error] RegHiveLoad - Hive file [D:\Win10XPE\Temp\Install.hives\DEFAULT] does not exist (RegHiveLoad,Tmp_Install_Default,%Gtemp%\Install.hives\DEFAULT) (Line 389)
But the error occurs in the script Win10XPE\Macro.script (Line 389), which is called from Win10XPE\Core.script.
Would like the log to be something like this:
Code: [Select]
<Errors>
- [1] Error in Script [Build Core] (Win10XPE\Core.script)\(Win10XPE\Macro.script)
[Error] RegHiveLoad - Hive file [D:\Win10XPE\Temp\Install.hives\DEFAULT] does not exist (RegHiveLoad,Tmp_Install_Default,%Gtemp%\Install.hives\DEFAULT) (Line 389)
Regards, Nikzzzz.

« Last Edit: July 13, 2018, 08:00:48 AM by NIKZZZZ »

Re: Log - error report
« Reply #1 on: July 14, 2018, 05:36:59 PM »

ied206

  • Moderator,
  • Chef
  • *****
  • Location: South Korea
  • Date Registered: Jan 2014
  • Posts: 257
Thanks for reporting, NIKZZZZ.

PEBakery's log database is designed to let a build log (denoting one command) can point to only one script where it resides in.
This kind of limitation was not a problem in entire log, because you can see the context like which script's section is being called by macro call.
But it becomes a problem because error summary omits the context. I will provide a workaround for this issue.

Re: Log - error report
« Reply #2 on: July 23, 2018, 05:43:56 PM »

ied206

  • Moderator,
  • Chef
  • *****
  • Location: South Korea
  • Date Registered: Jan 2014
  • Posts: 257
Please test with lastest nightly binary.

Changed log exports:

- Text export
ila_rendered

- HTML export
ila_rendered

 

Powered by EzPortal