Hi Harshad, I don't think we need the debug build in Travis CI, as I believe both the release builds and the debug build should produce the same results for a PR, although the latter in a test failure case, would provide additional info, like DEBUG_ASSERT as you mentioned. But as the PR reviewers we do not need such info at all. We only care whether the CI results pass.
I do recommend a PR submitter should develop using and test with the debug build. On the other hand, the template code explosion, particularly the expressions and operators part, typically results in OOM using GCC, and thus we set the make job to one. Cheers, Zuyu
