Bug 745496 - "condor_release.exe" returns "\r \n" string on its std error
Summary: "condor_release.exe" returns "\r \n" string on its std error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor
Version: 2.0
Hardware: Unspecified
OS: Windows
low
low
Target Milestone: 2.3
: ---
Assignee: Timothy St. Clair
QA Contact: Petra Svobodová
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-12 14:13 UTC by Petra Svobodová
Modified: 2012-10-30 13:25 UTC (History)
4 users (show)

Fixed In Version: condor-7.6.7-0.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-25 14:06:44 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petra Svobodová 2011-10-12 14:13:43 UTC
Description of problem: 
Even if the "condor_release.exe" application ends by standard way without exceptions and with exit code 0, it returns "\r \n" string on its std error.
In Linux is the std err empty in this case.

Version-Release number of selected component (if applicable):
condor-7.6.4-0.6.msi

How reproducible:
100%

Steps to Reproduce:
1. Submit a job from Windows.
2. Hold the job 
3. Release the job and check value of std error
  
Actual results:
The application does not have empty std err.

Expected results:
The application should have empty std error when there is no error.

Comment 1 Timothy St. Clair 2012-02-15 21:16:33 UTC
When testing ~ latest

hexedit of 'condor_release 2925000 >foo.txt <&1' vs. 'condor_release 2925000 >foo.txt 2<&1' 

shows no difference.  

e.g. - there is only one '0D 0A' which is output'd from stdout

Comment 3 Martin Kudlej 2012-02-16 12:16:10 UTC
This is pure Windows bug and only for condor_release.exe.

I've reproduced this on Windows XP with development version 7.6.7-0.2:
c:\> c:\condor\bin\condor_release.exe 1.0 1>x 2>y
c:\> dir
....... 18 x
........ 2 y

So y has 2 bytes and it contains \r\n even if command was successful.

the same with condor_hold.exe:
c:\> c:\condor\bin\condor_hold.exe 1.0 1>x 2>y
c:\> dir
....... 14 x
........ 0 y

Comment 4 Timothy St. Clair 2012-02-16 20:55:17 UTC
Running the exact test from comment #3 on Win 7 w/7.6 development bits yields:  
-------------------------------------------
C:\condor\tests>condor_hold 2925000.19 1>x 2>y

C:\condor\tests>dir
 Volume in drive C is Windows7_OS
 Volume Serial Number is

 Directory of C:\condor\tests

02/16/2012  02:44 PM    <DIR>          .
02/16/2012  02:44 PM    <DIR>          ..
02/15/2012  02:50 PM                38 wait.bat
02/15/2012  02:55 PM               263 win.submit
02/16/2012  02:46 PM                21 x
02/16/2012  02:46 PM                 0 y
               4 File(s)            322 bytes
               2 Dir(s)  213,540,810,752 bytes free

C:\condor\tests>cat x
Job 2925000.19 held

C:\condor\tests>condor_release 2925000.19 1>x 2>y

C:\condor\tests>dir
 Volume in drive C is Windows7_OS
 Volume Serial Number is

 Directory of C:\condor\tests

02/16/2012  02:44 PM    <DIR>          .
02/16/2012  02:44 PM    <DIR>          ..
02/15/2012  02:50 PM                38 wait.bat
02/15/2012  02:55 PM               263 win.submit
02/16/2012  02:47 PM                25 x
02/16/2012  02:47 PM                 0 y
               4 File(s)            326 bytes
               2 Dir(s)  213,531,635,712 bytes free

C:\condor\tests>cat x
Job 2925000.19 released

-------------------------------------------

I'm inclined to close as it may be Windows.XP specific behavior, 
+ it does not repro locally on my Win7 Box ( Most common Platform) 
+ very low priority BZ.

Comment 10 Petra Svobodová 2012-05-30 07:26:54 UTC
Retested on version condor-7.6.8-0.3; this bug occurs still.

See the Windows command line transcription, please:

....

C:\condor\bin>condor_hold.exe -name mrg-qe-06.lab.eng.brq.redhat.com 4108.0 1>st
dout_hold.txt 2>stderr.txt

C:\condor\bin>condor_release.exe -name mrg-qe-06.lab.eng.brq.redhat.com 4108.0 1
>stdout_release.txt 2>stderr_release.txt

C:\condor\bin>echo %ERRORLEVEL%
0

C:\condor\bin>dir *.txt
 Volume in drive C has no label.
 Volume Serial Number is F089-992A

 Directory of C:\condor\bin

05/29/2012  05:31 AM                 0 stderr.txt
05/29/2012  05:31 AM                 2 stderr_release.txt
05/29/2012  05:31 AM                17 stdout_hold.txt
05/29/2012  05:31 AM                21 stdout_release.txt
               4 File(s)             40 bytes
               0 Dir(s)   5,439,361,024 bytes free


C:\condor\bin>condor_version.exe
$CondorVersion: 7.6.8 May 25 2012 $
$CondorPlatform: WINDOWS $

...

The "condor_release.exe" finished with exit code 0 and its std error size is 2B. 

--> ASSIGNED

Comment 11 Timothy St. Clair 2012-05-30 13:54:25 UTC
I need to know exact versions that it does not work on, as I was unable to repro on Win7.  I suspect this is platform dependent.

Comment 12 Petra Svobodová 2012-05-30 15:29:40 UTC
This issue appears on all my machines: WindowsXP-x86, Windows7-x86 and x64, Windows Server2008-x86 and x64, Windows Server2003-x86 and x64.

Central manager configuration:
OS: Red Hat Enterprise Linux Server release 5.8 (Tikanga) - x86_64

root@hostname]# rpm -qa | grep condor 
python-condorutils-1.5-4.el5
ruby-condor-wallaby-tools-5.0.2-1.el5
condor-aviary-7.6.8-0.1.el5
condor-7.6.8-0.1.el5
condor-debuginfo-7.6.8-0.2.el5
condor-wallaby-client-5.0.2-1.el5
condor-wallaby-base-db-1.22-2.el5
condor-wallaby-tools-5.0.2-1.el5
condor-classads-7.6.8-0.1.el5


Note You need to log in before you can comment on or make changes to this bug.