EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: BETA: ci-scripts 3.0 (feat. Windows on Travis)
From: Ralph Lange via Core-talk <core-talk at aps.anl.gov>
To: EPICS Core Talk <core-talk at aps.anl.gov>
Date: Wed, 10 Jun 2020 12:45:54 +0200
Hi Mark,

On Wed, 10 Jun 2020 at 02:00, Mark Rivers <rivers at cars.uchicago.edu> wrote:

 

I have a question about what version of EPICS base BASE=7.0 actually is.  Is that a specific tag, or is it the tip of the 7.0 branch?


As Michael wrote, the setting must refer to the name of a branch or tag. In the case of the EPICS Base repo, '7.0' is the name of a branch.
 

Another question.  In base7.set I define MODULES="sncseq".  When building for RTEMS I use base7.set, but I want to add “ipac” to MODULES.  Is there a syntax to do that?  If I use this line:

  - env: SET=base7 RTEMS=4.10 MODULES="ipac"


There is the ADD_MODULES setting to allow adding modules to specific builds.
(Documented in the README.)
 

First I had a minor problem.  The .travis.yml.example-full file does not have an example of using the SET argument.  I was doing SET=base7.set, and I got an error message saying .ci-local/base7.set does not exist. But it does exist.  The problem is that the .set extension must be omitted, so it should be SET=base7.


Yes, without the extension.
(Documented in the README.)
I will fix the misleading error message.

Some of the builds are working, but some are failing for reasons I don’t understand. You can see them here: https://travis-ci.org/github/epics-modules/asyn/builds/696643004

 

The mingw cross builds for Windows  both fail with this error:

 

$ mingw --version

Traceback (most recent call last):

[...]


MinGW builds are now using the 'compiler: gcc' setting, both for the cross builds from Linux and for the native Windows builds.
You can just remove the 'compiler:' setting from your job lines, as 'gcc' is the default.
(Documented in the example config file.) 
 
Also: the 'STATIC=YES/NO' setting has been replaced by 'BCFG=default/static/debug/static-debug'.
(Also shown in the example config file.)

Cheers,
~Ralph


Replies:
RE: BETA: ci-scripts 3.0 (feat. Windows on Travis) Mark Rivers via Core-talk
References:
BETA: ci-scripts 3.0 (feat. Windows on Travis) Ralph Lange via Core-talk
RE: BETA: ci-scripts 3.0 (feat. Windows on Travis) Mark Rivers via Core-talk

Navigate by Date:
Prev: Build failed: epics-base base-integration-533 AppVeyor via Core-talk
Next: [Bug 1881563] Re: Empty arrays have undefined behavior Dirk Zimoch via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: BETA: ci-scripts 3.0 (feat. Windows on Travis) Michael Davidsaver via Core-talk
Next: RE: BETA: ci-scripts 3.0 (feat. Windows on Travis) Mark Rivers via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <20202021  2022  2023  2024 
ANJ, 10 Jun 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·