doctrine/doctrine2 — comment on commit bd5393a3187ab25136bcd8e5efea894928697e95
File:  line 0
By beberlei:

Asm89 found a fix already. Was just some side effect.

Am 24.10.2011 um 00:54 schrieb Guilherme Blanco:

> @beberlei what happened then? If this breaks a suite, then the ticket I closed is valid. I'll investigate this then.
>
> @jwage We already do that. Problem is that even this one that just added coverage to a non-tested environment may be valid on some drivers and invalid on other ones. It's impossible to be 100% sure without a CI that runs against all RDBMS the same suite.
> This for example is perfectly valid in SQLite, but if it fails on MySQL, then the ticket I closed became valid again. Since user didn't add the test environment, it's hard to decide how to test/patch it.
>
> Personally I think that instead of PR everything, we could put a CI online that runs our suite against all drivers.
> By doing that, we can receive mails of broken builds and can help us to identify possible broken state. What do you think?
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/doctrine/doctrine2/commit/bd5393a3187ab25136bcd8e5efea894928697e95#commitcomment-669533