There's most likely a bug in a test library you use. It could also be
that you are passing an invalid argument to a keyword, but even in
that case the keyword could report the error better. Run the test with
`--loglevel debug` command line option and you'll see a traceback that
shows where in the library code the error occurs. If you don't know
much Python, you may need to consult someone who knows it, preferably
the library developer, for more information.
Cheers,
.peke
--
Agile Tester/Developer/Consultant :: http://eliga.fi
Lead Developer of Robot Framework :: http://robotframework.org
Yes, the bug is in Robot Framework itself. I submitted an issue about
it and the bug will be fixed in RF 2.7.2. The issue also lists some
workarounds that you may want to try:
http://code.google.com/p/robotframework/issues/detail?id=1110
Thanks for reporting the issue!