|
| Re: Debugging IllegalArgumentException [message #551903 is a reply to message #551879] |
Tue, 10 August 2010 06:23   |
|
Hi Miles,
Did you try running Buckminster with the --displaystacktrace option? If you did, and that still didn't give you any
information, then I think the only option left is to attach a remote debugger. The method for doing that depends on how
your last Buckminster invocation is spawned. I usually do that by adding the following to my ant eclipse.launch macro:
<jvmarg value=" -agentlib:jdwp=transport=dt_socket,address=8000,server=y,sus pend=y "/>
HTH,
- thomas
On 08/10/2010 01:04 AM, Miles Parker wrote:
> Hi,
>
> I'm getting the following at the end of my build:
>
> Doing full workspace refresh
> Waiting for jobs to end
>
> Caused by: java.lang.IllegalArgumentException
> Archiving artifacts
> Finished: FAILURE
>
> Unfortunatly, there is no more information that that. I don't know why
> the details are getting buried. I can't see anything obviously wrong in
> the Hudson console but it is quite long so possible I've missed
> something. Any ideas about how I might go about tracking the cause down?
>
> Miles
|
|
|
| Re: Debugging IllegalArgumentException [message #551940 is a reply to message #551903] |
Tue, 10 August 2010 08:58 |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
I wonder if --displaystacktrace is documented, please log a doc
bugzilla.
- Henrik
Thomas Hallgren <thomas@tada.se> wrote:
> Hi Miles,
>
> Did you try running Buckminster with the --displaystacktrace option?
> If you did, and that still didn't give you any information, then I
> think the only option left is to attach a remote debugger. The method
> for doing that depends on how your last Buckminster invocation is
> spawned. I usually do that by adding the following to my ant
> eclipse.launch macro:
>
> <jvmarg
> value=" -agentlib:jdwp=transport=dt_socket,address=8000,server=y,sus pend=y "/>
>
> HTH,
> - thomas
>
> On 08/10/2010 01:04 AM, Miles Parker wrote:
>> Hi,
>>
>> I'm getting the following at the end of my build:
>>
>> Doing full workspace refresh
>> Waiting for jobs to end
>>
>> Caused by: java.lang.IllegalArgumentException
>> Archiving artifacts
>> Finished: FAILURE
>>
>> Unfortunatly, there is no more information that that. I don't know
> > why
>> the details are getting buried. I can't see anything obviously wrong
> > in
>> the Hudson console but it is quite long so possible I've missed
>> something. Any ideas about how I might go about tracking the cause
> > down?
>>
>> Miles
--
- henrik
|
|
|
|
|
| Re: Debugging IllegalArgumentException [message #552066 is a reply to message #552063] |
Tue, 10 August 2010 16:51 |
|
On 08/10/2010 06:36 PM, Miles Parker wrote:
> Henrik Lindberg wrote on Tue, 10 August 2010 09:37
>> On 8/10/10 10:58 AM, Henrik Lindberg wrote:
>> checked - it is described in the documentation.
>
>
> I guess it's one of those "if you know it's there you don't have to
> look" kinds of things. :) I think debug log level gives you a bit more
> as well. It would be nice to get this setup as one of the log-level
> options for hudson. To use this in a Hudson instance I guess you'd
> simply set it with setpref as the first command in your job.
The loglevel is not implemented as a setpref preference I'm afraid. You need to provide it as a command line option. I
know that's not ideal (the loglevel is really an eclipse preference). An enhancement request is in order :-)
- thomas
|
|
|
Powered by
FUDForum. Page generated in 0.03640 seconds
] 
Search
Help
Register
Login
Home
I think debug log level gives you a bit more as well. It would be nice to get this setup as one of the log-level options for hudson. To use this in a Hudson instance I guess you'd simply set it with setpref as the first command in your job.