Closed Bug 651661 Opened 13 years ago Closed 11 years ago

unit test failure in testGetJsonOrWarn

Categories

(Socorro :: General, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: rhelmer, Assigned: gabithume)

References

Details

I've only seen this one on Fedora 14 (which is recommended in the INSTALL file). Not sure if it's python 2.7-related or something else in the environment:

==== socorro.unittest.testlib.testutil ====
===========================================
.
======================================================================
FAIL: testGetJsonOrWarn: several invocations
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/socorro/socorro/socorro-virtualenv/lib/python2.7/site-packages/nose-1.0.0-py2.7.egg/nose/case.py", line 187, in runTest
    self.test(*self.arg)
  File "/home/socorro/socorro/socorro/unittest/processor/testProcessor.py", line 921, in testGetJsonOrWarn
    message_list
AssertionError: 
-------------------- >> begin captured logging << --------------------
processor: WARNING: While extracting 'key' from jsonDoc {'key': 23}, exception (<type 'exceptions.TypeError'>): 'int' object is not subscriptable
--------------------- >> end captured logging << ---------------------
Component: Socorro → General
Product: Webtools → Socorro
Considering that socorro/socorro-virtualenv/lib/python2.7 doesnt exist anymore, not even socorro-virtualenv/bin/python2.7, is this problem useful now?
If so, how can I reproduce it?
(In reply to Gabriela Thumé from comment #1)
> Considering that socorro/socorro-virtualenv/lib/python2.7 doesnt exist
> anymore, not even socorro-virtualenv/bin/python2.7, is this problem useful
> now?
> If so, how can I reproduce it?

The virtualenv was created with python2.7 -- you can modify the Makefile to use a different python when creating the virtualenv.
Ok, so I created the virtualenv with 2.7 and I don't see any error like that. Maybe because the nose version is 1.3 instead of 1.0?
(In reply to Gabriela Thumé from comment #3)
> Ok, so I created the virtualenv with 2.7 and I don't see any error like
> that. Maybe because the nose version is 1.3 instead of 1.0?

That sounds plausible. Change the required version of nose in your requirements/*.txt and see if you can duplicate!
I changed it and everything is working fine with testGetJsonOrWarn :)
Assignee: nobody → gabithume
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.