2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 <2017> 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Travis Builds of Base |
From: | "Johnson, Andrew N." <[email protected]> |
To: | Michael Davidsaver <[email protected]> |
Cc: | EPICS core-talk <[email protected]> |
Date: | Sat, 11 Nov 2017 21:16:05 +0000 |
I’m fairly sure I know what the msi problem is having thought about it overnight, and I agree that’s related to the reorganization of the source into modules. I will take a look at a fix for that later tonight.
I would still like to know why Travis seems to suppress almost all log message lines that have the word install in them (or something like that). That effect appears in all the build logs I have looked at, and is really annoying. Do we process the logs
ourselves at all, or is this effect definitely caused by Travis?
I’ve been trying to understand the build failure in the Travis-prepare script at line 1853 in https://travis-ci.org/epics-base/exampleCPP/jobs/300309821 and amazingly I think I just
worked out what happened there (it’s related to how our install Perl script works) and I might even know how to fix it...
- Andrew
--
Sent from my iPad
|