Re: [patch] Automated formatting of Keytest bug reports.

This fixes a bug where get_pid mistakes gdb lyx for the lyx process, preventing it from working at all unless lyx is a symbolic link. Additionally this patch reduces the size of the log, as it no longer generates 3+ lines in the log for every key sent. It also adds more sanity checking and various

Re: [patch] Automated formatting of Keytest bug reports.

John McCabe-Dansted wrote: It does not introduce any filenames with ':' though :). its in. pavel

Re: [patch] Automated formatting of Keytest bug reports.

This fixes a bug where get_pid mistakes "gdb lyx" for the lyx process, preventing it from working at all unless lyx is a symbolic link. Additionally this patch reduces the size of the log, as it no longer generates 3+ lines in the log for every key sent. It also adds more sanity checking and

Re: [patch] Automated formatting of Keytest bug reports.

John McCabe-Dansted wrote: > It does not introduce any filenames with ':' though :). its in. pavel

RE: [patch] Automated formatting of Keytest bug reports.

Specifically I reproduced the bug manually, and put the backtrace in. Hmm. I'm wondering why you can reproduce it manually. Did you customize the converter settings ? If so, can you show us your lyxrc.defaults and preferences file, such that we might reproduce the problem. (Maybe you have

Re: [patch] Automated formatting of Keytest bug reports.

On Mon, Jan 4, 2010 at 6:49 PM, Vincent van Ravesteijn - TNW v.f.vanraveste...@tudelft.nl wrote: Specifically I reproduced the bug manually, and put the backtrace in. Hmm. I'm wondering why you can reproduce it manually. Did you customize the converter settings ? If so, can you show us your

RE: [patch] Automated formatting of Keytest bug reports.

>Specifically I reproduced the bug manually, and put >the backtrace in. Hmm. I'm wondering why you can reproduce it manually. Did you customize the converter settings ? If so, can you show us your "lyxrc.defaults" and "preferences" file, such that we might reproduce the problem. (Maybe you

Re: [patch] Automated formatting of Keytest bug reports.

On Mon, Jan 4, 2010 at 6:49 PM, Vincent van Ravesteijn - TNW wrote: >>Specifically I reproduced the bug manually, and put >>the backtrace in. > > Hmm. I'm wondering why you can reproduce it manually. > > Did you customize the converter settings ? If so, can you show

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

Am 03.01.2010 00:35, schrieb Pavel Sanda: This commit breaks SVN completely: SVN cleanup doesn't help and also no completely new checkout. ouch. can you try whether svn works now? It works now, many thanks. regards Uwe

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

Am 03.01.2010 00:35, schrieb Pavel Sanda: This commit breaks SVN completely: SVN cleanup doesn't help and also no completely new checkout. ouch. can you try whether svn works now? It works now, many thanks. regards Uwe

Re: [patch] Automated formatting of Keytest bug reports.

On Thu, Dec 31, 2009 at 7:36 PM, John McCabe-Dansted gma...@gmail.com wrote: Ah, I manually broke this :( Specifically I reproduced the bug manually, and put the backtrace in. I did this to make sure this was really from the same svn revision. I have changed Keytest now so that it keeps a log of

Re: [patch] Automated formatting of Keytest bug reports.

John McCabe-Dansted wrote: have changed Keytest now so that it keeps a log of the svn revision when it logs a crash so this won't be required.  Patch is attached, i have commited the patch. hopefully without errs, but rather check it ;) pavel

SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

i have commited the patch. hopefully without errs, but rather check it ;) This commit breaks SVN completely: SVN cleanup doesn't help and also no completely new checkout. The reason is that you committed a file named view:1 This is an invlaid filename on Windows and thus screws up SVN. Can

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

Uwe Stöhr wrote: i have commited the patch. hopefully without errs, but rather check it ;) This commit breaks SVN completely: SVN cleanup doesn't help and also no completely new checkout. ouch. can you try whether svn works now? pavel

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

On Sun, Jan 3, 2010 at 7:31 AM, Uwe Stöhr uwesto...@web.de wrote: The reason is that you committed a file named view:1 This is an invlaid filename on Windows and thus screws up SVN. Can anybody on Linux please rename the file so that has no \, /, :, | ?, *, , and '' in its name. Sorry. Hmm,

Re: [patch] Automated formatting of Keytest bug reports.

On Thu, Dec 31, 2009 at 7:36 PM, John McCabe-Dansted wrote: > Ah, I manually broke this :( Specifically I reproduced the bug manually, and put the backtrace in. I did this to make sure this was really from the same svn revision. I have changed Keytest now so that it keeps a log

Re: [patch] Automated formatting of Keytest bug reports.

John McCabe-Dansted wrote: > have changed Keytest now so that it keeps a log of the svn revision > when it logs a crash so this won't be required.  Patch is attached, i have commited the patch. hopefully without errs, but rather check it ;) pavel

SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

> i have commited the patch. hopefully without errs, but rather check it ;) This commit breaks SVN completely: SVN cleanup doesn't help and also no completely new checkout. The reason is that you committed a file named "view:1" This is an invlaid filename on Windows and thus screws up SVN.

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

Uwe Stöhr wrote: > > i have commited the patch. hopefully without errs, but rather check it ;) > > This commit breaks SVN completely: SVN cleanup doesn't help and also no > completely new checkout. ouch. can you try whether svn works now? pavel

Re: SVN broken - was: Re: [patch] Automated formatting of Keytest bug reports.

On Sun, Jan 3, 2010 at 7:31 AM, Uwe Stöhr wrote: > The reason is that you committed a file named "view:1" This is an invlaid > filename on Windows and thus screws up SVN. Can anybody on Linux please > rename the file so that has no "\", "/", ":", "|" "?", "*", "<", ">" and '"' >

RE: [patch] Automated formatting of Keytest bug reports.

An example of a bug entered using this button: http://www.lyx.org/trac/ticket/6424 It appears that the backtrace shown there is not related to the bug. The backtrace is different from the one I see when I follow the Keytest Report link, it is not an assertion as the keyword indicates,

Re: [patch] Automated formatting of Keytest bug reports.

On Thu, Dec 31, 2009 at 7:08 PM, Vincent van Ravesteijn - TNW v.f.vanraveste...@tudelft.nl wrote: An example of a bug entered using this button: http://www.lyx.org/trac/ticket/6424 It appears that the backtrace shown there is not related to the bug. The backtrace is different from

RE: [patch] Automated formatting of Keytest bug reports.

> An example of a bug entered using this button: >http://www.lyx.org/trac/ticket/6424 > It appears that the backtrace shown there is not related to the bug. The backtrace is different from the one I see when I follow the "Keytest Report" link, it is not an assertion as the keyword

Re: [patch] Automated formatting of Keytest bug reports.

On Thu, Dec 31, 2009 at 7:08 PM, Vincent van Ravesteijn - TNW < v.f.vanraveste...@tudelft.nl> wrote: > > An example of a bug entered using this button: > >http://www.lyx.org/trac/ticket/6424 > > > > It appears that the backtrace shown there is not related to the bug. The > backtrace is

[patch] Automated formatting of Keytest bug reports.

The attached patch allows most of the fields in the trac bugreport to filled in with one click from the keytest summary page. The hope is that this would help ensure that the keytest bug-reports are consistent, complete and accurate. An example of a bug entered using this button:

[patch] Automated formatting of Keytest bug reports.

The attached patch allows most of the fields in the trac bugreport to filled in with one click from the keytest summary page. The hope is that this would help ensure that the keytest bug-reports are consistent, complete and accurate. An example of a bug entered using this button: