Issue 841 in robotframework: using "--noncritical" and "[Tags]" in testcase to set tag, causes testcase to be critical

[robotframework]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 841 by lnor...@internap.com: using "--noncritical" and "[Tags]"  
in testcase to set tag, causes testcase to be critical
http://code.google.com/p/robotframework/issues/detail?id=841

pybot --version
Robot Framework 2.5.7 (Python 2.6.5 on linux2)

uname -a
Linux qa-test-node3 2.6.32-24-generic-pae #39-Ubuntu SMP Wed Jul 28  
07:39:26 UTC 2010 i686 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.04.1 LTS
Release:        10.04
Codename:       lucid


Expected:
test cases labeled "notReady" and run with "--noncritical notReady" would  
not impact test suite pass/fail and critical tests pass/fail counts

Actual:
(from report HTML)

Name    Documentation   Metadata / Tags         Crit.   Status  Message
...
UAM Hudson Regression.Aria Callback 	(test suite doc)		N/A 	FAIL 	6  
critical tests, 5 passed, 1 failed
6 tests total, 5 passed, 1 failed
...
Aria Callback Bad Command 	Aria Callback bad command test 	notReady 	yes 	 
FAIL 	('Aria call back error:', {'body': '', 'headers': ...})

NOTE: this test is labeled as critical in the report



Here is pybot call and RF test case text:



pybot --name UAM_Hudson_Regression --exclude unfinished --exclude disabled  
--noncritical notReady --log NONE --report NONE --NoStatusRC  
Aria_Callback.txt Create_Users.txt GenerateKey.txt GetBillingId.txt  
GetCustomers.txt GetUserData.txt Logon.txt LogonForCloud.txt  
ModifyStatus.txt PostUsage.txt SetPassword.txt UpdateBilling.txt  
Update_Users.txt

| Aria Callback Bad Command | [Documentation] | Aria Callback bad command  
test
|                     | Create Test Config         |
|                     | [Tags]                     | notReady
|                     | BillingInfoCallbackInvalid | ${testAriaCFG} |  
${testCFG}