Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[github-actions] upload core dump file and binaries when test program crashes #5805

Closed
Irving-cl opened this issue Nov 12, 2020 · 2 comments · Fixed by #5861
Closed

[github-actions] upload core dump file and binaries when test program crashes #5805

Irving-cl opened this issue Nov 12, 2020 · 2 comments · Fixed by #5861

Comments

@Irving-cl
Copy link
Contributor

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is.

We got some cases that fail intermittently, like #5802, #5774. From the logs, it looks like some node crashes:

ERROR: test (__main__.LowPower_5_3_01_SSEDAttachment)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./tests/scripts/thread-cert/v1_2_LowPower_5_3_01_SSEDAttachment.py", line 98, in test
    timeout=timeout * 2))
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/node.py", line 1342, in ping
    self.simulator.go(1)
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/simulator.py", line 509, in go
    self.receive_events()
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/simulator.py", line 262, in receive_events
    msg, addr = self.sock.recvfrom(self.MAX_MESSAGE)
socket.timeout: timed out

======================================================================
ERROR: test (__main__.LowPower_5_3_01_SSEDAttachment)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/thread_cert.py", line 250, in tearDown
    node.stop()
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/node.py", line 598, in stop
    self.thread_stop()
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/node.py", line 614, in thread_stop
    self.send_command('thread stop')
  File "/home/runner/work/openthread/openthread/tests/scripts/thread-cert/node.py", line 574, in send_command
    self.pexpect.send(cmd + '\n')
  File "/home/runner/.local/lib/python3.6/site-packages/pexpect/popen_spawn.py", line 142, in send
    return self.proc.stdin.write(b)
BrokenPipeError: [Errno 32] Broken pipe

And I'm not sure if it's the program's problem or for some reason the process crashes in github-action's environment. And it's pretty hard to reproduce these failures locally.

Describe the solution you'd like A clear and concise description of what you want to happen.

I'm thinking if we can upload core dump file for crashed programs and the binaries so that we can debug the programs locally. I'll check if we can do this. Thoughts? @bukepo @simonlingoogle @moandor-y @jwhui

@jwhui
Copy link
Member

jwhui commented Nov 12, 2020

Uploading core dump files as artifacts on failure seems like a good idea.

@Irving-cl
Copy link
Contributor Author

#5861 merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants