Luca Toscano

travis: remove verbose arg for Ubuntu Worker
travis: disable email notifications

There are still some spurious failures to iron out,

turn off email notification to avoid too many failure

emails to dev@.

travis: add verbose config to perl test suite for Ubuntu Worker All Modules

For some reason we get sporadic failures only in Ubuntu Worker All Modules' test:

t/apache/rwrite.t ................... 53/? # Failed test 113 in /home/travis/build/apache/httpd/test/perl-framework/blib/lib/Apache/TestCommon.pm at line 56 fail #113

t/apache/rwrite.t ................... Failed 1/114 subtests

Recent examples:

https://travis-ci.org/apache/httpd/jobs/632425202

https://travis-ci.org/apache/httpd/jobs/633250739

Add "-verbose" as test option to capture more data about the failure

when it happens.

test/travis_before_linux.sh: increase backoff time before executing svn export
travis: restore email notifications for dev@

The issue with ppcle64 seems to be fixed from [1],

and Joe fixed the APR 1.7.x issue as well. Builds are

back to normal.

[1]: https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598/6

test/travis_before_linux.sh: move retry logic to function

Move the retry logic to a bash function and restore the -e

failure policy in the script (to have cleaner log traces

in base of build failures).

travis: temporary disable notifications to dev@

There seem to be some issues to iron out, disabling

email notifications to avoid spamming dev@.

test/travis_before_linux.sh: make for loop more resilient

This is a follow up to my last commit to this file, to make

the for loop more resilient with the following:

- use --force in svn export, otherwise the second attempt will

always fail due to the dest directory already present.

- exit 1 in case the 5 tries end up in a non zero exit code

(to fail fast the build).

test/travis_before_linux.sh: remove bash -e flag

To allow a proper fail/retry, -e needs to be removed.

Ideally this shouldn't happen, so I'd consider this

a test to see if the bash for workaround is a viable

option or not.

test/travis_before_linux.sh: add a simple bash retry to svn export

Sometimes a build is killed by Travis due to svn export taking

a long time to complete (> 10m). This change should be a test to see

if a simple workaround reduces the noise to the dev@ mailing list.

travis: sync trunk's notification config with 2.4.x

travis: send notification to httpd-dev@ only on failure

Due to a combination of Daniel's work and probably some fix

on Travis end, we are now finally getting Travis emails in

httpd-dev@. Since having notifications for successful builds

might become a little spammy, let's just alert when a build

fails (like we do with buildbot IIUC).

travis: enable email notifications on success as test
Documentation rebuild
Update travis config

* Add 'if TRAVIS_OS_NAME' to before_install/before_script/script to allow multi-os testing.

* Add separation lines in matrix config (better visual impact).

* Add Linux to all the current job's name.

* Add tests for Worker mpm.

Add note to my old backport proposal.
Propose Yann's patch to fix a regression in mod_ratelimit
mod_rewrite doc rebuild
mod_rewrite.xml: add an example about override behavior

A user in PR 63051 was confused about the default behavior

of mod_rewrite (override) when merging two sections in the

directory context at the same nesting level. I was confused

as well, but after a quick look at the code I figured out that

RewriteOptions Inherit seems to solve the issue (naming is,

in this case, a bit counter intuitive).

mod_rewrite doc rebuild
mod_rewrite.xml: add an example about override behavior

A user in PR 63051 was confused about the default behavior

of mod_rewrite (override) when merging two sections in the

directory context at the same nesting level. I was confused

as well, but after a quick look at the code I figured out that

RewriteOptions Inherit seems to solve the issue (naming is,

in this case, a bit counter intuitive). I hope that I added

a good clarification in the code, if not please amend it as

you think it's best!

documentation rebuild
documentation rebuild
documentation rebuild
mod_proxy.xml: backport r1844556
documentation rebuild
mod_proxy.xml: explicitly state that proxypass cannot be used with If
add note about PR 62025 for backport proposal of r1832092
documentation rebuild
mod_headers.xml: backport r1844401