After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574053 - Failures log pass=0 and pass = 1 and they do not log the message
Failures log pass=0 and pass = 1 and they do not log the message
Status: RESOLVED WONTFIX
Product: LDTP
Classification: Other
Component: pyldtp
1.5.0
Other All
: Normal normal
: ---
Assigned To: LDTP maintainers
LDTP Development Mailing List
Depends on:
Blocks:
 
 
Reported: 2009-03-04 12:40 UTC by Ara Pulido
Modified: 2011-02-05 00:49 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
this suggests a fix to log_passorfail_usability (766 bytes, patch)
2009-03-19 06:12 UTC, tac 		none Details | Review

Description Ara Pulido 2009-03-04 12:40:01 UTC 
Please describe the problem:
Using ldtprunner

When trying to log a failure a have in my code:

logFailures ("Files differ.", True, "fail")

And in the log this is what I get:

<test>
[...]
<pass>0</pass>
<screenshot>screenshots/screenshot-03-04-2009-12-32-1236166332.png</screenshot>
<pass>1</pass>
</test>

The message with "Files differ" does not get logged and there are two entries for the <pass> tag, one with 0 and the other with 1.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Comment 1 tac 2009-03-19 06:12:46 UTC 
Created attachment 130937 [details] [review]
this suggests a fix to log_passorfail_usability
Comment 2 tac 2009-03-19 06:13:34 UTC 
 I could see in ldtp's log feature design, internalLog('some msg','pass') or
internalLog('some msg','fail') would be set as a format of <pass>1(0)</pass>.
  This directly cast away the message you want to send. I would prefer the
<pass> some_msg </pass>, so adding a patch here : )
Comment 3 Nagappan Alagappan 2011-02-05 00:49:33 UTC 
This functionality is now moved to Mago, closing the bug