cfx run --logfile=filename does not create log file ( for both addon-sdk-1.16 and addon-sdk-1.15)

26 views
Skip to first unread message

Kk

unread,
Apr 3, 2014, 9:51:57 PM4/3/14
to mozilla-la...@googlegroups.com

Environment

Windows 7 Enterprise
Service Pack 1
Python version 2.7.5
addon-sdk-1.16
addon-sdk-1.15

Problem Description

<cfx run --logfile=Filename> does not generate logfile in designated path or current directory. For both versions of addon SDK (1.16 and 1.15)

If a file with intended logfilename is manually created in current directory it is deleted when executing the above command.

Initially with only addon-sdk-1.15 installed and addon created attempted to log messages to logfile using <cfx run --logfile=filename>
(used several variations of this command:
<cfx run --logfile="logfile.txt" > with quotes around filename
<cfx run --logfile=logfile.xt> without qoutes around filename
<cfx run --logfile "logfile.txt" > flag without assignment symbol but filename including quotes
<cfx run --logfile logfile.txt> flag without assignment symbol and filename w/o quotes

Above commands with both fullpath and currentpath (omitting path, only including filename).

All the above was also executed with version addon-sdk-1.16 with same result.

Is logging facility output to file broken?
Has anyone experience the same issue?


Best Regards,

KK



Adrian Aichner

unread,
Apr 4, 2014, 12:20:01 PM4/4/14
to mozilla-la...@googlegroups.com
I can reproduce the problem on Windows XPP.
Log always goes to terminal, not logfile.
Reply all
Reply to author
Forward
0 new messages