call pybot --timestampoutputs --log mylog.html --report NONE tests.html
[ ERROR ] Parsing 'tests.html' failed: Data source does not exist.
I want to create report with time stamp but throws error. Any example as how to generate reports with unique name with time-date.
The error you report, "Data source does not exist", is not because of your use of the --timestampoutputs option. It's because robot can't find "tests.html".
--timestampoutputs works fine when you give it a valid test suite. For example, when I ran the code in your question I ended up with a log file named mylog-20150220-053904.html.
Related
My robot framework test contains part, where I run .exe file. I am using Run process keyword from Process library.
${result} Run Process path_to_the_file/file.exe cwd=path_to_the_file/
When I run this locally, the file is executed and response is like this:
14:35:34.553 INFO Waiting for process to complete.
14:35:34.634 INFO Process completed.
14:35:34.634 TRACE Return: <robot.libraries.Process.ExecutionResult object at 0x055963D0>
14:35:34.634 INFO ${result} = <result object with rc 0>
When I run this test on Team City, the file is not executed ( properly )
5:27:27.587 INFO Waiting for process to complete.
15:27:27.786 INFO Process completed.
15:27:27.786 TRACE Return: <robot.libraries.Process.ExecutionResult object at 0x012C1310>
15:27:27.786 INFO ${result} = <result object with rc 3221225781>
Edit: I tried google for that return code from Team city run and I found something like this:
3221225781 = [$id=DLL_NOT_FOUND, $desc={Unable To Locate Component}
This application has failed to start because %hs was not found.
Reinstalling the application may fix this problem.]
Does anyone have this sort of experience and what can I do with it?
EDIT2: after deeper analysis I found out, that there are missing DLLs on the agent. So once I'll add missing DLLs I'll know if that was a source of this isue
So the solution for this issue was to add missing DLLs. Once I added the newest version of Microsoft Visual C++ package, the Run Process executed the .exe file properly.
I have added a new .p procedure (prodict/myProc.p) in prodict.pl file and saved the prodict.pl file under my program's root folder.
Also, I have added the path of the folder to the PROPATH and it is the first item in the PROPATH.
In order to run the procedure, in the Procedure Editor, I try to run using the code below
RUN prodict/myProc.p
The error message I receive is:
How can I make my procedure run?
Note: I'm trying this in order to create a custom prodict/load_df.p, so it can be run without the need of any user interaction. My older question can be found here.
Instead of RUN "prodict/myProc.p", I have used
RUN value(search("prodict/myProc.p")).
The error message is changed to
Cannot run procedure file prodict/myProc.p from library. (1976)
When we look at the error description:
Can't run procedure file from library. (1976)
The named file in the library reference (e.g, progname.p in libname.pl<>) in the RUN statement is a source file, and cannot be run. Only PROGRESS r-code files can be run from a library.
Solution: I have added the compiled .r file to the library through proenv:
prolib prodict.pl -add prodict/myProc.r
and changed the calling code as:
RUN "prodict/myProc.r".
Now the code runs. Thanks to Stefan Drissen for showing me a way to get the real error message.
I'm trying to use vstest.console.exe with the TfsPublisher logger in VSTS (cloud).
There's a URL example shown in the article for TFS onsite, but I'm trying to work out what parameters to use for my VSTS build. The example is:
/logger:TfsPublisher;Collection=http://localhost:8080/tfs/DefaultCollection;TeamProject=MyProject;BuildName=DailyBuild_20121130.1
But I just get an error saying the build cannot be found in the project, e.g.
Error: Build "1234" cannot be found under team project "MyProject".
I believe the problem is the BuildName parameter. My project and build definition have no spaces in the names. I have tried various values, e.g.:
BuildName=%BUILD_BUILDID% (resolves to number, e.g. 1234)
BuildName=%BUILD_DEFINITIONNAME% (resolves to build definition name OK)
BuildName=%BUILD_BUILDURI% (resolves to url, e.g. vstfs:///Build/Build/1234)
The error message confirms that the environment variables seem to be resolving OK, but I can't determine what I should substitute for "DailyBuild_20121130.1" in my case.
Updated: My vstest.console.exe logger parameter currently looks like
/logger:TfsPublisher;Collection=%SYSTEM_TEAMFOUNDATIONCOLLECTIONURI%;TeamProject=%SYSTEM_TEAMPROJECT%;BuildName=%BUILD_BUILDNUMBER%
I effectively got the result I wanted using the Trx logger and one of the "Publish Test Results" build steps:
vstest.console.exe ... /logger:Trx
The build name is generated by "Build number format" under build definition "General" tab. You can get it from "BUILD_BUILDNUMBER" variable.
I'm trying to convert word documents to PDF, via the commandline using unoconv via PHP.
I'm using the Symfony Process Component to run the command via the command line.
public function run()
{
$cmd = 'unoconv --listener & unoconv ' . $this->path;
//Tested this to check for permissions and this worked.
//$cmd = 'touch /vagrant/public/testfile.pdf';
$process = new Process($cmd);
$process->run();
return $process->getOutput();
}
This yields no output, and doesn't convert the file. However if I echo the $cmd and paste it into the CLI it converts the file as expected and logs output as it goes.
Any ideas what could be the problem?
Edit:
I've since tried: calling mustRun() & start() methods on the symfony class.
mustRun() gives the following error:
"The command '//command//' failed. Exit Code: 251(Unknown error) Output: ================ Error Output: ================
After adding the log code as suggested by Diego Ferri, I get Error: Unable to connect or start own listener. Aborting. in the log file; but I can't find much online that's helpful for that.
Please read this section but also check the troubleshooting section.
It is possible that the shell is missing some important environment variables for unoconv/LibreOffice to work properly (PATH, HOME, ...). And it is recommended you call the LibreOffice python binary with unoconv instead of leaving it up to unoconv to determine the location of LibreOffice and python.
When I open NetSim's Config.txt file after Simulation I get the following error:
Error in config file ---
1) Unknown xml tag "UPDATE_TIMER" in line number 166.
Tag path: TETCOS_NETSIM/NETWORK_CONFIGURATION/DEVICE_CONFIGURATION/DEVICE
[3] /LAYER [2]/ROUTING_PROTOCOL/PROTOCOL_PROPERTY
However, Simulation runs Successfully. What does this mean?
You need to specify the missing parameters in the Configuration file which are mentioned in the "ConfigLog.txt". Since, NetSim will crash if all the required parameters are not configured, NetSim addresses this issue by enabling default values where ever required. Error produced in the "ConfigLog.txt" because the value for the "UPDATE_TIMER" for "ROUTING_PROTOCOL" is not specified in the Configuration file. In order to obtain accurate metrics for the desired scenario you need to update your Configuration.xml file.