If we build release mode on the builders, perhaps we could re-enable
"warnings as errors", but for release builds only.
This would mean you can develop in debug mode locally with warnings, but
bors won't merge any PRs that introduce warnings?
On 25/02/15 00:12, Lars Bergstrom wrote:
Two questions about build flavors.
1) Should we change the default build type back from debug to release?
When we made the switch to cargo, we changed to debug builds by default, which
made for some good “reduced build times” headlines, but has gotten me mail from
externals evaluating Servo asking why it’s so slow/choppy. It has also tripped
up internal folks doing performance or memory profiling more than once.
2) Should the builders test release only or release and debug?
We had release-only regressions during the last set of Rust and submodule
upgrades, which is really bad (e.g., right now, Servo release on OSX does not
display any content!). The only question in my mind here is whether we want to
test everything in release+debug, just test release, or mainly test release but
have a token debug build/test machine.
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
