On 1/31/2017 4:30 PM, Jacob Champion wrote:
> On 01/30/2017 05:39 PM, Daniel Ruggeri wrote:
>> I'm tremendously inspired by this work. What are your thoughts on the
>> idea of having a series of docker container builds that compile and run
>> the test suite on various distributions? I'll
On 01/30/2017 12:02 PM, Jacob Champion wrote:
- run per-commit incremental builds
- run nightly clean builds
These two are implemented. Every commit you make to trunk (well, group
of commits, within fifteen seconds of each other) is run through an
incremental build, which takes about ten
On 01/30/2017 06:23 PM, Daniel Shahaf wrote:
You could also configure buildbot to detect any new compiler warnings.
That'll cause buildbot to report a FAILURE (red) or a WARNING (yellow),
instead of a SUCCESS (green), if the build succeeded but a compiler
warning has been issued.
Good
On 01/30/2017 05:39 PM, Daniel Ruggeri wrote:
I'm tremendously inspired by this work. What are your thoughts on the
idea of having a series of docker container builds that compile and run
the test suite on various distributions? I'll volunteer to give this a
whack since it's something that's
Jacob Champion wrote on Mon, Jan 30, 2017 at 12:02:35 -0800:
> On 01/02/2017 07:53 AM, Daniel Shahaf wrote:
> >Setting this up isn't a lot more complicated than filing an INFRA ticket
> >with a build script, a list of build dependencies, and a list of
> >branches to build, and deciding how build
I'm tremendously inspired by this work. What are your thoughts on the
idea of having a series of docker container builds that compile and run
the test suite on various distributions? I'll volunteer to give this a
whack since it's something that's been in the back of my mind for a long
while...
I
On 01/02/2017 07:53 AM, Daniel Shahaf wrote:
Setting this up isn't a lot more complicated than filing an INFRA ticket
with a build script, a list of build dependencies, and a list of
branches to build, and deciding how build failures would be notified.
To follow up on this, we now have an
On 31 Dec 2016, at 4:58 AM, William A Rowe Jr wrote:
> Thinking two things would help.
>
> Splitting our functional utilities into a libaputil would make it much easier
> to write the tests that exercise these elements of our code.
Definite +1.
I want to see a C based
On 12/30/2016 02:55 PM, Stefan Fritsch wrote:
Yes, httpd lacks unit tests. One problem is that many APIs depend on very
complex structs like request_rec, conn_rec, server_conf, etc. In order to
write unit tests for such APIs, one would need to write quite a bit of
infrastructure to set these
Luca Toscano wrote on Mon, Jan 02, 2017 at 15:51:43 +0100:
> I don't have a wide experience on build httpd on systems different than
> Debian/Ubuntu, so any help/suggestion/pointer would help a lot (for
> example, building on Windows).
I wouldn't worry about that just yet. Start by having only
Hi Stefan,
2016-12-30 23:55 GMT+01:00 Stefan Fritsch :
>
>
> Another thing that is missing: A buildbot that builds current trunk (and
> possibly 2.x branches) and runs the test suite and alerts the dev list of
> regressions. I guess this "just" needs a volunteer to set it up and
On Dec 30, 2016 14:55, "Stefan Fritsch" wrote:
Hi,
it's quite rare that I have a bit of time for httpd nowadays. But I want to
comment on a mail that Jacob Champion wrote on -security that contains some
valid points about the lack of our test framework. I am posting this to
12 matches
Mail list logo