Segmentation fault while running a lcc run (...) command

12 views
Skip to first unread message

Akshay Maldhure

unread,
Feb 19, 2020, 10:29:10 PM2/19/20
to lemoncheesecake
I'm running one of my tests using lcc run SuitName.testName command and the execution gets halted with "Segmentation fault" (yes, that's it, that's all it prints) on the console on the Jenkins machine which is based on the Linux OS (Ubuntu). lcc is not installed on the Jenkins machine in any virtual environment, but it installed on the default Python environment.

I do not get this issue on my local machine which is a Mac. I'm running the test locally inside a virtual environment.

Could this be related to lcc in any way? Is there any way to enable more logs so that I could check if something is wrong with my code?

Akshay Maldhure

unread,
Feb 19, 2020, 10:35:47 PM2/19/20
to lemoncheesecake
The command I'm running on Jenkins is: /var/lib/jenkins/.local/bin/lcc run SuiteName.test_name --save-report at_each_event --exit-error-on-failure

Akshay Maldhure

unread,
Feb 20, 2020, 3:46:47 AM2/20/20
to lemoncheesecake
After adding the faulthandler.enable() in my code, I see that the error is originating from the slackclient code.

I've opened an issue with slackclient for this: https://github.com/slackapi/python-slackclient/issues/624

Please disregard this thread.

Nicolas Delon

unread,
Feb 20, 2020, 3:49:13 PM2/20/20
to lemoncheesecake
You mean you are using slackclient directly in your own code ?

Because the lemoncheeseecake slack reporting backend is using slacker (https://github.com/os/slacker) as a Slack client library.

Nicolas.

Akshay Maldhure

unread,
Feb 20, 2020, 7:06:18 PM2/20/20
to lemoncheesecake
Yes, I'm using the slackclient directly in my code and not using slacker, because I need some slack APIs which are provided by slackclient and those are not present in slacker.
Reply all
Reply to author
Forward
0 new messages