Is the `TVM_STRICT_MODE` fails the CI if throw warnings? It looks not sustainable to me because this is not in a normal logging system so people can easily forget it.
My understanding about how to determine the log messages is that if we hope to show them to end-users, then we should use INFO and WARNING. If we only want to show to developers, we should use DEBUG (FATAL is not a case in this discussion as it intentionally crashes the process). **Interpreting float as float32** message is a message that we wish end-users to see (correct me if I am wrong), so it should be a WARNING. Here are two proposals to deal with this: P1. We intentionally want to display that many warnings to users to let them know how many cases are processed when converting a model. This behavior is similar to other compilers like gcc. However, it could be annoying. P2. A mechanism to show the same warnings only once. That's why I pointed out the AutoTVM case (the link @t-vi posted). Maybe we could make this mechanism more general. --- [Visit Topic](https://discuss.tvm.ai/t/discuss-the-meaning-of-float-in-relay/6949/14) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.ai/email/unsubscribe/d880cbd25a4953bcbb9d9c79c7e50fc186233b7abd2f70831124b359d1f28add).
