Hi Mads,
It might yes, I included also some info in the commit msg. May I ask why
are you asking this? I like to keep dev@ on track to allow more people to
chime in and comment, but I can stop if this is too spammy.
Luca
Il dom 29 dic 2019, 18:17 Mads Toftum ha scritto:
> On Sat, Dec 28, 2019
On Sat, Dec 28, 2019 at 09:46:28AM +0100, Luca Toscano wrote:
> sorry for the travis spam, I hope to have improved the config via r1872045.
>
Would it perhaps make more sense sending this to the same list as commit
messages or perhaps a new list?
vh
Mads Toftum
--
http://flickr.com/photos/q42/
Update: it seems an issue on the Travis side (
https://travis-ci.community/t/ppc64le-an-error-occurred-while-generating-the-build-script/6598),
plus I noticed other sporadic failures on different part of the CI config.
I just disabled email notifications to dev@ to avoid spamming the list :)
Luca
Hi everybody,
sorry for the travis spam, I hope to have improved the config via r1872045.
In this last build only one job failed:
https://travis-ci.org/apache/httpd/jobs/630258333
The error log says a very informative "An error occurred while generating
the build script." and nothing more. Since
Build Update for apache/httpd
-
Build: #137
Status: Errored
Duration: 11 mins and 45 secs
Commit: 2688e47 (trunk)
Author: Luca Toscano
Message: test/travis_before_linux.sh: make for loop more resilient
This is a follow up to my last commit to this file, to mak
