Andrew Reusch
Andrew Reusch
Summary from my week: things were fairly quiet, mainly some flaky tests. - [[jenkins](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3414/pipeline)](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3414/pipeline) on c1b22ee - flaky test, filed https://github.com/apache/tvm/issues/11527 - [[jenkins](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3415/pipeline)](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3415/pipeline) on ac5d781 - continued flaky paddlepaddle test,...
- [[jenkins](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3753/pipeline/)](https://ci.tlcpack.ai/blue/organizations/[jenkins](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3755/pipeline)/tvm/detail/main/3753/pipeline/) on cfe8318 - failed to docker pull from DockerHub - [[jenkins](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3762/pipeline)](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3755/pipeline) on 9f4bf38 - failed to docker pull from DockerHub - [jenkins](https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/3762/pipeline) on 99d42b2 - test_qlinearadd tolerance, filed...
cc @hpanda-naut for triage
[Runtime] Add runtime.contrib.set_custom_cpu_allocator to use custom memalign() and free() functions
@jsheng-jian thanks for the PR! i think this maybe deserves a broader look by the community as it could potentially impact performance. just curious, did you consider a compile-time workaround...
[Runtime] Add runtime.contrib.set_custom_cpu_allocator to use custom memalign() and free() functions
cc @tqchen @csullivan @junrushao1994 @jwfromm
[Runtime] Add runtime.contrib.set_custom_cpu_allocator to use custom memalign() and free() functions
@jsheng-jian could you address the question above?
@alter-xp we run these nightly, here's the [latest failure](https://ci.tlcpack.ai/blue/organizations/jenkins/docker-images-ci%2Fdocker-image-run-tests/detail/docker-image-run-tests/169/pipeline). resolving the ARM toolchain seems maybe-related to this...what if instead of trying to fix the two together, we just create ci_riscv...
i think we're ok w/o RFC for this one as it's just moving around previously-RFC'd functionality. thanks!
@alter-xp sorry--i've been a bit busy lately. looks like @driazati approved/merged that one, and i created https://github.com/tlc-pack/tlcpack/pull/131 to add that build to our nightly docker image rebuild/test. looks like that...
cc @hpanda-naut can you triage this?