test_name failures on OS X

[giampaolo]

From [email protected] on October 23, 2010 20:49:03

======================================================================
FAIL: test_name (__main__.TestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_psutil.py", line 409, in test_name
    self.assertEqual(psutil.Process(sproc.pid).name, os.path.basename(PYTHON))
AssertionError: 'Python' != 'python'

======================================================================
FAIL: test_process_name (_posix.PosixSpecificTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/jloden/src/psutil/test/_posix.py", line 88, in test_process_name
    self.assertEqual(name_ps, name_psutil)
AssertionError: 'python' != 'Python'



This is occurring because the kernel/BSD process list on OS X reports the 
process name as "Python" but sys.executable is /usr/bin/python. Using ps on the 
command line  just reports cmdline[0], so usually just "python". We have 3 
different results, none of them "wrong" - just looking at different 
information. Opening this so we can record discussion on what to do with this. 

Since we're reporting the same thing as the kernel I would favor changing the 
test cases but then we need some kind of alternative test case that's reliable as well.

Original issue: http://code.google.com/p/psutil/issues/detail?id=121

[giampaolo]

From [email protected] on October 27, 2010 15:43:10

For now the test just checks explicitly for "Python" as the name on OS X only

[giampaolo]

From [email protected] on October 27, 2010 15:50:57

Status: WaitingForReview

[giampaolo]

From [email protected] on October 27, 2010 15:51:35

Labels: -Progress-0in4 Progress-4in4

[giampaolo]

From g.rodola on November 12, 2010 12:01:23

Status: Fixed