while i'm running azure pipeline in building images i'm getting this error
##[error]Unhandled: Unable to locate executable file: 'docker'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Related
I ran Robot framework test cases(present in github) through azure pipeline. Test cases executed fine. Next I modified robot framework test case file to import yaml variable file (variable yaml file also present in same github repo folder) which has variables to be used by test cases file.
yaml variable file looks like this
login:
url: xxx.com
email: abc#y.com
password: xyz
And my test cases file look like this
*** Settings ***
Library SeleniumLibrary
Variables variablesfile.yaml
*** Test Cases ***
Dev_TC01_AddProcess
Open Browser ${login.url} chrome
Input Text id=email ${login.email}
Input Password id=password ${login.password}
And my yaml pipeline to trigger test scenarios looks like this
- script: |
pip install pytest pytest-azurepipelines
pytest
robot --pythonpath . -x outputxunit.xml TestScenarios.robot
displayName: 'Run Robot Scripts'
but on running the pipeline I get error, because test scenarios file is unable to reference variablesfile.yaml. got error message - Resolving variable '${login.url}' failed:
Can you please suggest how to reference variable file
Above error seems to be caused by the variables yaml file not being found.
If you defined Variables file in the Settings section like what you defined in above example. You should put the variables yaml files in the same directory of the test robot file TestScenarios.robot.
If the variables files are not under the same directory. You can define the correct relative path in the Settings section like below example: See here.
Variables ../data/variables.yaml
Note:
Using YAML files with Robot Framework requires PyYAML module to be installed. If you have pip_ installed, you can install it simply by running pip install pyyaml.
Variables file is in the same directory of TestScenarios.robot. I also tried entering the full path still it didnt work. Finally i got a solution, I need to run pip install pyyaml script then it worked
I'm using a flutter package "BiblePlus". This package will read a .pdb file but when I specified a path to my .pdb file which is inside the lib folder (lib/pdb) I get this error:
Cannot open file, path = '/pdb/KJVD.pdb' (OS Error: No such file or
directory, errno = 2)
Please refer to this image.
The upload failed and I see there is a warning that MANIFEST.in does not exist and standard file not found: should have one of README, README.txt, README.rst.
Can someone please help? I'm not sure if I need to create the manifest template and standard readme files or if there's something wrong with the code I'm using:
C:\Users\Sean\Desktop\Projects\Head_First_Python\nester>python setup.py sdist upload
running sdist
running check
warning: sdist: manifest template 'MANIFEST.in' does not exist (using default file list)
warning: sdist: standard file not found: should have one of README, README.txt, README.rst
writing manifest file 'MANIFEST'
creating nester-1.0.0
making hard links in nester-1.0.0...
hard linking nester.py -> nester-1.0.0
hard linking setup.py -> nester-1.0.0
Creating tar archive
removing 'nester-1.0.0' (and everything under it)
running upload
Submitting dist\nester-1.0.0.tar.gz to https://upload.pypi.org/legacy/
Upload failed (403): Invalid or non-existent authentication information. See https://pypi.org/help/#invalid-auth for details
error: Upload failed (403): Invalid or non-existent authentication information. See https://pypi.org/help/#invalid-auth for details
C:\Users\Sean\Desktop\Projects\Head_First_Python\nester>
** (Postgrex.Error) ERROR 58P01 (undefined_file): could not open extension control file "/usr/local/Cellar/postgresql#9.6/9.6.5/share/postgresql#9.6/extension/postgis.control": No such file or directory
I'm getting this error when I try to run mix ecto.migrate...
Why is it looking at that path? I've tried moving postgis.control
If I run this command find /usr -name postgis.control it gives me this result:
/usr/local/Cellar/postgis/2.4.0_1/share/postgresql/extension/postgis.control
/usr/local/share/postgresql#9.6/extension/postgis.control
Does anybody know how I can move postgis.control or what I could be doing wrong?
The file postgis.control should be in the extension subdirectory of the PostgreSQL share directory. You can find out the location of the share directory by running pg_config --sharedir.
All the other files that belong to the PostGIS extension must also be in place: the SQL files in the same directory as the control file, and the shared libraries in pg_config --libdir.
I have a simple demo console program to debug but surprisingly windbg can't symbols from Microsoft default store.
I do
.reload /f
I get the summary:
************* Symbol Loading Error Summary **************
Module name Error
ConsoleApp PDB not found : cache*
Unable to locate the .pdb file in this location
The system cannot find the file specified : SRV*https://msdl.microsoft.com/download/symbols
The SYMSRV client failed to find a file in the UNC store, or there
is an invalid UNC store (an invalid path or the pingme.txt file is
not present in the root directory), or the file is present in the
symbol server exclusion list.
Symbols file path is
srv*
I was trying to get to work with pdf files of my own application but it can't even find microsoft symbols.
Update
After sorting out other issues, I can reproduce this back. It seems like I was just reading the message wrong. Since the error message was pointing to Microsoft default store, I read it like it didn't find the specified files at Microsoft store...thinking it was not connecting/finding/downloading Microsoft symbols when in fact the major error says it just didn't find my own's application's symbols.
Still, the message is not super clear. For example when I set and add an additional path, says Ok.
0:000> .sympath srv*c:\test\Symbols*https://msdl.microsoft.com/download/symbols;c:\test\hello
DBGHELP: Symbol Search Path: srv*c:\test\symbols*https://msdl.microsoft.com/download/symbols;c:\test\hello
DBGHELP: Symbol Search Path: srv*c:\test\symbols*https://msdl.microsoft.com/download/symbols;c:\test\hello
Symbol search path is: srv*c:\test\Symbols*https://msdl.microsoft.com/download/symbols;c:\test\hello
Expanded Symbol search path is: srv*c:\test\symbols*https://msdl.microsoft.com/download/symbols;c:\test\hello
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\test\Symbols*https://msdl.microsoft.com/download/symbols
OK c:\test\hello
Now when I .reload /f the symbol loading error summary is this:
************* Symbol Loading Error Summary **************
Module name Error
App The system cannot find the file specified : srv*c:\test\symbols*https://msdl.microsoft.com/download/symbols
The SYMSRV client failed to find a file in the UNC store, or there
is an invalid UNC store (an invalid path or the pingme.txt file is
not present in the root directory), or the file is present in the
symbol server exclusion list.
PDB not found : c:\test\hello\symbols\exe\App.pdb
Unable to locate the .pdb file in this location
I don't know the why unable to load in the path PDB not found : c:\test\hello\symbols\exe\App.pdb?
In the output of your WinDbg session there is
************* Symbol Loading Error Summary **************
Module name Error
ConsoleApp PDB not found : cache*
so there's a module load error for ConsoleApp, which is your application and not a Microsoft application.
Certainly you have not uploaded the symbols of your application to Microsoft, so the symbols cannot be found on https://msdl.microsoft.com/download/symbols.
It seems to me that your application is
either a release build without symbol information at all
a debug build with symbol information but the symbols are not found in the path that is specified within the application
Therefore,
in addition to the Microsoft symbol server (please use .symfix c:\path\to\microsoft-symbols),
make sure you have built PDBs for your application (check your compiler and/or linker settings, depending on the programming language)
add your own symbols to the symbol path (.sympath+ c:\path\to\pdb\).
.reload the symbols
The syntax srv* is documented, but actually I've never seen someone use it in practice, because people want to benefit from symbols stored locally, which increases the performance.
If it still does not work, use !sym noisy and Process Monitor to troubleshoot loading of the symbols. A file name filter for .pdb should help.
The reason for that is
even with !sym noisy, WinDbg does not list all paths where it is actually looking for symbols
the documentation for the symbol load order is incorrect.
The help file says that symbols are loaded in this order
X:\...\symbols\<ext>\<filename>.pdb
X:\...\<ext>\<filename>.pdb
X:\...\<filename>.pdb
But the load order observed by me is
X:\...\<filename>.pdb
X:\...\<ext>\<filename>.pdb
X:\...\symbols\<ext>\<filename>.pdb
what does srv* mean is it all you have got ?
where is the path ?
like say c:\symbols
or f:\mycrap\myuselesssymbols etc etc ?
the path should be something like srv*<your LOCAL DIRECTORY>viz X:\yyyyyy*http://msdl.microsoft.com/download/symbols
you can use .symfix to set a default symbol path prior to .reload /f