Code Monkey home page Code Monkey logo

Comments (8)

ndelon avatar ndelon commented on May 20, 2024 1

If you're talking about a previous version of lemoncheesecake, this behavior has not changed since 0.22.0.

I encourage you to check your calls to lcc.log_*, since the issue appear in a failed test, this limit your search. You can also look for True and False occurrences in logs in the resulting report/report.js file.

from lemoncheesecake.

ndelon avatar ndelon commented on May 20, 2024

Hello @shivamgarg17 ,

I guess that you did not copy/paste the full stacktrace, could you do it ?
I will able to provide you a more accurate diagnostic. From my understanding, there was something that you logged (it could be a step description, a message, a check, etc..) where you passed a bool instead of the excepted string.

Best regards.

from lemoncheesecake.

shivamgarg17 avatar shivamgarg17 commented on May 20, 2024

Hi @ndelon ,
Thanks for quick response, I will try to figure out the said steps. Meanwhile please find the full staktrace:
+ lcc report --non-passed Traceback (most recent call last): File "/var/lib/jenkins/workspace/qa/venv/bin/lcc", line 10, in <module> sys.exit(main()) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/cli/main.py", line 49, in main return command.run_cmd(cli_args) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/cli/commands/report.py", line 47, in run_cmd explicit=cli_args.explicit or not sys.stdout.isatty() File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 230, in print_report _print_chunks(chunks) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 196, in _print_chunks for chunk in chunks: File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 189, in render_results yield self.render_test(result) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 166, in render_test return self.render_chunk(test.description, short_description, test.status, test.steps) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 142, in render_chunk details = self.render_steps(steps) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 110, in render_steps self.render_highlighted(self.wrap_description_col(entry.message)) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/reporting/console.py", line 72, in wrap_description_col return wrap_text(description, int((self.max_width - self._table_overhead) * 0.75)) File "/var/lib/jenkins/workspace/qa/venv/local/lib/python2.7/site-packages/lemoncheesecake/helpers/text.py", line 21, in wrap_text textwrap.wrap(line, width) for line in text.split("\n") AttributeError: 'bool' object has no attribute 'split'

from lemoncheesecake.

ndelon avatar ndelon commented on May 20, 2024

Ok, then it seems to be with a log_{debug,warning,info,error} call where instead of passing a string, you pass a boolean.

Regards.

from lemoncheesecake.

shivamgarg17 avatar shivamgarg17 commented on May 20, 2024

from lemoncheesecake.

shivamgarg17 avatar shivamgarg17 commented on May 20, 2024

from lemoncheesecake.

ndelon avatar ndelon commented on May 20, 2024

In the new lemoncheesecake 1.2.2 release (https://github.com/lemoncheesecake/lemoncheesecake/blob/master/CHANGELOG.md#122-2019-09-15), data going persisted into the report are now strictly type-checked ASAP and will avoid more complicated debugging sessions.
For instance, something such as lcc.log_info(True) will now raise a TypeError exception.

from lemoncheesecake.

shivamgarg17 avatar shivamgarg17 commented on May 20, 2024

If you're talking about a previous version of lemoncheesecake, this behavior has not changed since 0.22.0.

I encourage you to check your calls to lcc.log_*, since the issue appear in a failed test, this limit your search. You can also look for True and False occurrences in logs in the resulting report/report.js file.

Hi @ndelon ,
Its worked after converting them into string
Thanks

from lemoncheesecake.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.