History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-3176
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Dee Frazier
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

[QB 8.0.4] Enabling "links in log setting" on step breaks java error stacktrace format

Created: 01/May/18 04:34 PM   Updated: 15/May/18 04:12 PM
Component/s: None
Affects Version/s: 8.0.4
Fix Version/s: 8.0.5

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment:
Operating System: Windows 10 Enterprise 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
Memory: 65536MB RAM
java.runtime.version 1.8.0_162-b12


 Description  « Hide
impact: error stack traces are difficult to read

Experienced: When I enable "Show Links In Log" it causes the error stack traces to be incorrectly formatted. This only happens when the step has the setting enabled. If the setting is disabled, the log is formatted correctly.

For example:
11:24:41,302 WARN - NOTE - This is a Build Trigger Step. You must click on the "Triggered Build" link in the step graph to jump to the build you want.
11:24:41,302 ERROR - Step 'master>Send some Slack Messages' is failed: java.lang.NullPointerException: Cannot invoke method getId() on null object at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112) at script15251312457031833429650.run(script15251312457031833429650.groovy:6) at com.pmease.quickbuild.plugin.basis.BasisPlugin$32.evaluate(BasisPlugin.java:382) at com.pmease.quickbuild.DefaultScriptEngine.evaluate(DefaultScriptEngine.java:305) at com.pmease.quickbuild.D...
11:24:41,457 INFO - Executing post-execute action...

Vs the correct formatting:
11:24:41,302 WARN - NOTE - This is a Build Trigger Step. You must click on the "Triggered Build" link in the step graph to jump to the build you want.
11:24:41,302 ERROR - Step 'master>Send some Slack Messages' is failed: java.lang.NullPointerException: Cannot invoke method getId() on null object
    at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
    at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
    at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
    at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:54)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
    at script15251312457031833429650.run(script15251312457031833429650.groovy:6)
    at com.pmease.quickbuild.plugin.basis.BasisPlugin$32.evaluate(BasisPlugin.java:382)
    at com.pmease.quickbuild.DefaultScriptEngine.evaluate(DefaultScriptEngine.java:305)
    at com.pmease.quickbuild.D...
11:24:41,457 INFO - Executing post-execute action...

Expected: The log should display the correct formatting no matter what the setting is to show links in the log.

Repro:
1. Create a step
2. Enable the "Show links in log" setting
3. Create an error in the post-execute action
4. Run the build
5. Observe the incorrectly formatted log
6. Edit the step
7. disable the "show links in log" setting
8. Load the log again and observe the log is now correctly formatted.


 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.