From: Dominik A. <Dominik.Acri@Gmx.net> - 2011-05-19 10:36:14
|
Hi, I use msys for building ffmpeg with in a win7_64 buildbot slave and have an strange behaviour calling bash from buildbot. Triggers an batch file (build.bat) that calls bash --login -i build.sh. build.sh #!bin/bash pwd export ... If i start the batch file via doubleclick or typing into cmd shell the output looks correct. /foo/bar ... declare -x PWD=/bar If I call the same .bat file from buildbot slave, the output is windows style. C:\mingw32\foo\bar declare - x PWD=c:\mingw32\foo\bar I tried : #!/bin/bash THE_CURRENT_PATH=`bash -c pwd -L` echo "Starting Script prebuild.sh in : $THE_CURRENT_PATH" But the result is the same, buildbot output is in win style, but calling from dos shell returns the paths in posix style. Anybody an idea what can cause that ? -- Mit freundlichen Grüssen Dominik Acri mailto:Dominik.Acri@Gmx.net |
From: Earnie <ea...@us...> - 2011-05-20 11:27:01
|
Dominik Acri wrote: > Hi, > > I use msys for building ffmpeg with in a win7_64 buildbot slave and > have an strange behaviour calling bash from buildbot. > > Triggers an batch file (build.bat) that calls bash --login -i build.sh. > This is wrong. You shouldn't be using --login nor -i in this case. > build.sh > #!bin/bash > pwd > export > ... > > If i start the batch file via doubleclick or typing into cmd shell the output > looks correct. > > /foo/bar > ... > declare -x PWD=/bar > > If I call the same .bat file from buildbot slave, the output is > windows style. > > C:\mingw32\foo\bar > declare - x PWD=c:\mingw32\foo\bar > > > > I tried : > #!/bin/bash > THE_CURRENT_PATH=`bash -c pwd -L` > echo "Starting Script prebuild.sh in : $THE_CURRENT_PATH" > > But the result is the same, buildbot output is in win style, but calling > from dos shell returns the paths in posix style. > > Anybody an idea what can cause that ? > No, but this use isn't really supported even though it may work. Why start in a cmd shell instead of bash to begin with? -- Earnie -- http://www.for-my-kids.com |
From: Dominik A. <Dominik.Acri@Gmx.net> - 2011-05-21 08:38:49
|
Guten Tag Earnie, Am Freitag, 20. Mai 2011 um 13:26 schrieben Sie: E> Dominik Acri wrote: >> Hi, >> >> I use msys for building ffmpeg with in a win7_64 buildbot slave and >> have an strange behaviour calling bash from buildbot. >> >> Triggers an batch file (build.bat) that calls bash --login -i build.sh. >> E> This is wrong. You shouldn't be using --login nor -i in this case. Fixed. >> build.sh >> #!bin/bash >> pwd >> export >> ... >> >> If i start the batch file via doubleclick or typing into cmd shell the output >> looks correct. >> >> /foo/bar >> ... >> declare -x PWD=/bar >> >> If I call the same .bat file from buildbot slave, the output is >> windows style. >> >> C:\mingw32\foo\bar >> declare - x PWD=c:\mingw32\foo\bar >> >> >> >> I tried : >> #!/bin/bash >> THE_CURRENT_PATH=`bash -c pwd -L` >> echo "Starting Script prebuild.sh in : $THE_CURRENT_PATH" >> >> But the result is the same, buildbot output is in win style, but calling >> from dos shell returns the paths in posix style. >> >> Anybody an idea what can cause that ? >> E> No, but this use isn't really supported even though it may work. Why E> start in a cmd shell instead of bash to begin with? Only to make sure both tests start with the same starting point. I changed it to trigger the bash directly from the buildbot server but the result is the same :-( http://chii.homedns.org:8010/builders/playground/builds/1/steps/shell/logs/stdio export returns declare -x PWD="c:\\Slave\\playground" but local: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten. C:\Users\buildbot>bash bash-3.1$ export declare -x !::="::\\" declare -x !C:="C:\\Users\\buildbot" declare -x ALLUSERSPROFILE="C:\\ProgramData" declare -x APPDATA="C:\\Users\\buildbot\\AppData\\Roaming" declare -x CLIENTNAME="MAINFRAME" declare -x COMMONPROGRAMFILES="C:\\Program Files (x86)\\Common Files" declare -x COMMONPROGRAMFILES(X86)="C:\\Program Files (x86)\\Common Files" declare -x COMMONPROGRAMW6432="C:\\Program Files\\Common Files" declare -x COMPUTERNAME="VM-WIN7-64" declare -x COMSPEC="C:\\Windows\\system32\\cmd.exe" declare -x FP_NO_HOST_CHECK="NO" declare -x HOMEDRIVE="C:" declare -x HOMEPATH="\\" declare -x LOCALAPPDATA="C:\\Users\\buildbot\\AppData\\Local" declare -x LOGONSERVER="\\\\VM-WIN7-64" declare -x NUMBER_OF_PROCESSORS="2" declare -x OLDPWD declare -x OS="Windows_NT" declare -x PATH="/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Wind ows/System32/WindowsPowerShell/v1.0/:/c/Program Files/TortoiseSVN/bin:/c/Program Files (x86)/CMake 2.8/bin:/c/Program Files/TortoiseGit/bin:/c/Program Files (x8 6)/SlikSvn/bin/:/c/Program Files (x86)/Git/cmd:/c/Program Files (x86)/WinMerge:/ usr/bin" declare -x PATHEXT=".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC" declare -x PROCESSOR_ARCHITECTURE="x86" declare -x PROCESSOR_ARCHITEW6432="AMD64" declare -x PROCESSOR_IDENTIFIER="AMD64 Family 16 Model 6 Stepping 3, AuthenticAM D" declare -x PROCESSOR_LEVEL="16" declare -x PROCESSOR_REVISION="0603" declare -x PROGRAMDATA="C:\\ProgramData" declare -x PROGRAMFILES="C:\\Program Files (x86)" declare -x PROGRAMFILES(X86)="C:\\Program Files (x86)" declare -x PROGRAMW6432="C:\\Program Files" declare -x PROMPT="\$P\$G" declare -x PSMODULEPATH="C:\\Windows\\system32\\WindowsPowerShell\\v1.0\\Modules \\" declare -x PUBLIC="C:\\Users\\Public" declare -x PWD="/c/Users/buildbot" declare -x SESSIONNAME="RDP-Tcp#0" declare -x SHLVL="1" declare -x SYSTEMDRIVE="C:" declare -x SYSTEMROOT="C:\\Windows" declare -x TEMP="/tmp" declare -x TERM="cygwin" declare -x TMP="/tmp" declare -x USERDOMAIN="vm-win7-64" declare -x USERNAME="buildbot" declare -x USERPROFILE="C:\\Users\\buildbot" declare -x VS90COMNTOOLS="c:\\Program Files (x86)\\Microsoft Visual Studio 9.0\\ Common7\\Tools\\" declare -x WINDIR="C:\\Windows" declare -x WINDOWS_TRACING_FLAGS="3" declare -x WINDOWS_TRACING_LOGFILE="C:\\BVTBin\\Tests\\installpackage\\csilogfil e.log" bash-3.1$ -- Mit freundlichen Grüssen Dominik Acri mailto:Dominik.Acri@Gmx.net |
From: Earnie <ea...@us...> - 2011-05-21 20:14:29
|
Dominik Acri wrote: > Guten Tag Earnie, > > Am Freitag, 20. Mai 2011 um 13:26 schrieben Sie: > > E> Dominik Acri wrote: >>> Hi, >>> >>> I use msys for building ffmpeg with in a win7_64 buildbot slave and >>> have an strange behaviour calling bash from buildbot. >>> >>> Triggers an batch file (build.bat) that calls bash --login -i build.sh. >>> > > E> This is wrong. You shouldn't be using --login nor -i in this case. > > Fixed. > >>> build.sh >>> #!bin/bash >>> pwd >>> export >>> ... >>> >>> If i start the batch file via doubleclick or typing into cmd shell the output >>> looks correct. >>> >>> /foo/bar >>> ... >>> declare -x PWD=/bar >>> >>> If I call the same .bat file from buildbot slave, the output is >>> windows style. >>> >>> C:\mingw32\foo\bar >>> declare - x PWD=c:\mingw32\foo\bar >>> >>> >>> >>> I tried : >>> #!/bin/bash >>> THE_CURRENT_PATH=`bash -c pwd -L` >>> echo "Starting Script prebuild.sh in : $THE_CURRENT_PATH" >>> >>> But the result is the same, buildbot output is in win style, but calling >>> from dos shell returns the paths in posix style. >>> >>> Anybody an idea what can cause that ? >>> > > E> No, but this use isn't really supported even though it may work. Why > E> start in a cmd shell instead of bash to begin with? > > Only to make sure both tests start with the same starting point. I don't understand how starting the command from windows is any different than starting from bash. > I changed it to trigger the bash directly from the buildbot server but > the result is the same :-( > As I said earlier, your use case is unsupported. Although I do not know why the PWD value should be set in Windows style paths. If you start bash, then from bash do the ``bash build.sh'' does it make a difference? If not then there is a bug and you can open a bug report. -- Earnie -- http://www.for-my-kids.com |