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

[RUST][RUNTIME] nnvm test fails #2480

Closed
ehsanmok opened this issue Jan 22, 2019 · 3 comments · Fixed by #2482
Closed

[RUST][RUNTIME] nnvm test fails #2480

ehsanmok opened this issue Jan 22, 2019 · 3 comments · Fixed by #2482
Assignees

Comments

@ehsanmok
Copy link
Contributor

ehsanmok commented Jan 22, 2019

During my local dev for Rust frontend, the current runtime tests/test_nnvm fails with that is also a problem with other current PRs such as this in here.

error: failed to run custom build command for `test-nnvm v0.0.0 (/workspace/rust/tests/test_nnvm)`

process didn't exit successfully: `/workspace/rust/tests/test_nnvm/target/debug/build/test-nnvm-7757aa29dfd2f3a3/build-script-build` (exit code: 101)

--- stderr

thread 'main' panicked at 'Cannot find config for target=llvm --system-lib, workload=('dense', (4, 8, 'float32'), (16, 8, 'float32'), (16, 'float32')). A fallback configuration is used, which may bring great performance regression.

', build.rs:18:5

note: Run with `RUST_BACKTRACE=1` for a backtrace.

Previously, my local test was failing at this check_sum. This is rather strange. I'm on Rust-nightly 1.32.

@tqchen @nhynes

@nhynes nhynes self-assigned this Jan 22, 2019
@nhynes
Copy link
Member

nhynes commented Jan 22, 2019

I ran the tests in a local docker container according to the CI flow on 0806b69 but could not reproduce the bug. I'd suggest rebasing the failing PRs onto master, at the very least.

@eqy
Copy link
Contributor

eqy commented Jan 22, 2019

Interesting, the three most recently opened PRs all fail CI with this error.

@nhynes
Copy link
Member

nhynes commented Jan 22, 2019

Well, I found the bug. Why I couldn't reproduce is a separate issue, but I'll post a fix now :)

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

Successfully merging a pull request may close this issue.

3 participants