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

CI error with "raise child_exception" #5914

Closed
pengxin99 opened this issue Jan 9, 2019 · 5 comments
Closed

CI error with "raise child_exception" #5914

pengxin99 opened this issue Jan 9, 2019 · 5 comments

Comments

@pengxin99
Copy link

pengxin99 commented Jan 9, 2019

Subject:

Problem

  • The ci work interrupt twice with this pr commit in mxnet-pr12498
    thanks for your time.

Procedure to reproduce the problem

<Paste your command-line here which cause the problem>

Error logs / results

/usr/local/lib/python2.7/dist-packages/recommonmark/parser.py:280: UserWarning: Unsupported inline type Hardbreak

  warn("Unsupported inline type " + inline.t)

reading sources... [ 41%] faq/develop_and_hack

reading sources... [ 41%] faq/distributed_training

reading sources... [ 42%] faq/env_var

reading sources... [ 42%] faq/faq

reading sources... [ 43%] faq/finetune

Converted 1 tables in faq/finetune

reading sources... [ 43%] faq/float16

reading sources... [ 44%] faq/gradient_compression

reading sources... [ 44%] faq/index

reading sources... [ 45%] faq/model_parallel_lstm

reading sources... [ 45%] faq/multi_devices

reading sources... [ 46%] faq/new_op

reading sources... [ 46%] faq/nnpack

Converted 1 tables in faq/nnpack

reading sources... [ 47%] faq/perf


Exception occurred:

  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child

    raise child_exception

OSError: [Errno 14] Bad address

The full traceback has been saved in /tmp/sphinx-err-DtF09X.log, if you want to report the issue to the developers.

Please also report this if it was a user error, so that a better error message can be provided next time.

A bug report can be filed in the tracker at </~https://github.com/sphinx-doc/sphinx/issues>. Thanks!

Makefile:75: recipe for target 'html' failed

make[1]: *** [html] Error 1

make[1]: Leaving directory '/work/mxnet/docs'

Makefile:563: recipe for target 'docs' failed

make: *** [docs] Error 2

build.py: 2019-01-09 04:56:12,848Z INFO Waiting for status of container 9ab3db47b10b for 600 s.

build.py: 2019-01-09 04:56:13,144Z INFO Container exit status: {'Error': None, 'StatusCode': 2}

build.py: 2019-01-09 04:56:13,144Z ERROR Container exited with an error 😞

build.py: 2019-01-09 04:56:13,144Z INFO Stopping container: 9ab3db47b10b

build.py: 2019-01-09 04:56:13,146Z INFO Removing container: 9ab3db47b10b

build.py: 2019-01-09 04:56:13,384Z INFO Other running containers: ['fb57c720b496']

build.py: 2019-01-09 04:56:13,385Z CRITICAL Execution of ['/work/runtime_functions.sh', 'deploy_docs'] failed with status: 2

Expected results

Reproducible project / your project

Environment info

  • OS: <Unix/Linux/Mac/Win/other with version>
  • Python version:
  • Sphinx version:
  • <Extra tools e.g.: Browser, tex or something else>
@tk0miya
Copy link
Member

tk0miya commented Jan 9, 2019

Please paste the full traceback file here. It helps us to investigate error.
Thanks,

@pengxin99
Copy link
Author

The whole file is a bit big, and you can find the log here. @tk0miya

@tk0miya
Copy link
Member

tk0miya commented Jan 10, 2019

No, full stacktrace is generated as external file. Please see this line which you pasted.

The full traceback has been saved in /tmp/sphinx-err-DtF09X.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at </~https://github.com/sphinx-doc/sphinx/issues>. Thanks!

If it is hard to get the error log, You can see it on log with -T option to sphinx-build command.

BTW, it seems you're using very old Sphinx. How about upgrading it to newest one? It might be resolved.

Running Sphinx v1.5.6

@pengxin99
Copy link
Author

@tk0miya Thanks, and i cannot get the full stacktrace file. I will recommend the this repo to use a new version.

@tk0miya
Copy link
Member

tk0miya commented Jan 24, 2019

I'm closing this now.
Please feel free to reopen this if you're still in trouble.
Thanks,

@tk0miya tk0miya closed this as completed Jan 24, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants