-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Exercise TVM under minimal configuration in CI #11932
Comments
driazati
pushed a commit
that referenced
this issue
Aug 11, 2022
This PR builds and tests TVM (running the CPP and unittests) under minimal configuration with some debug flags enabled: - `USE_RELAY_DEBUG=ON` in TVM - `-Wp,-D_GLIBCXX_ASSERTIONS` in TVM - `-DLLVM_ENABLE_ASSERTIONS=ON` in LLVM It also adds this configuration to the CI. `tests/python/unittest/test_meta_schedule_task_scheduler.py::test_meta_schedule_task_scheduler_multiple_gradient_based` results in an array OOB access and a segfault due to `D_GLIBCXX_ASSERTIONS`. I disable this test for now and will open an issue to solve it ASAP. It should fix #11932 and address [this discussion](https://discuss.tvm.apache.org/t/pre-rfc-new-ci-container-ci-cpu-asserts/12536/9).
xinetzone
pushed a commit
to daobook/tvm
that referenced
this issue
Nov 25, 2022
This PR builds and tests TVM (running the CPP and unittests) under minimal configuration with some debug flags enabled: - `USE_RELAY_DEBUG=ON` in TVM - `-Wp,-D_GLIBCXX_ASSERTIONS` in TVM - `-DLLVM_ENABLE_ASSERTIONS=ON` in LLVM It also adds this configuration to the CI. `tests/python/unittest/test_meta_schedule_task_scheduler.py::test_meta_schedule_task_scheduler_multiple_gradient_based` results in an array OOB access and a segfault due to `D_GLIBCXX_ASSERTIONS`. I disable this test for now and will open an issue to solve it ASAP. It should fix apache#11932 and address [this discussion](https://discuss.tvm.apache.org/t/pre-rfc-new-ci-container-ci-cpu-asserts/12536/9).
mikeseven
pushed a commit
to mikeseven/tvm
that referenced
this issue
Sep 27, 2023
This PR builds and tests TVM (running the CPP and unittests) under minimal configuration with some debug flags enabled: - `USE_RELAY_DEBUG=ON` in TVM - `-Wp,-D_GLIBCXX_ASSERTIONS` in TVM - `-DLLVM_ENABLE_ASSERTIONS=ON` in LLVM It also adds this configuration to the CI. `tests/python/unittest/test_meta_schedule_task_scheduler.py::test_meta_schedule_task_scheduler_multiple_gradient_based` results in an array OOB access and a segfault due to `D_GLIBCXX_ASSERTIONS`. I disable this test for now and will open an issue to solve it ASAP. It should fix apache#11932 and address [this discussion](https://discuss.tvm.apache.org/t/pre-rfc-new-ci-container-ci-cpu-asserts/12536/9).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have seen a couple bugs due to microTVM being presumed-ON in config.cmake. Namely, you get python errors importing TVM right now when USE_MICRO is OFF. We should have a regression test that verifies basic functionality with everything (or nearly everything) OFF.
Context: #9617
And another micro-related issue of the same kind, which i don't have handy right now.
cc @gigiblender
The text was updated successfully, but these errors were encountered: