Hi Ralph,
This is great, thanks.
I am testing using this new version for the asyn CI.
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?
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"
it does not find sncseq, presumably because MODULES on the env: line overrides that in base7.set. Is something like MODULES+=ipac supported? This line works:
- env: SET=base7 RTEMS=4.10 MODULES="sncseq ipac"
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.
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):
File ".ci/cue.py", line 987, in <module>
main(sys.argv[1:])
File ".ci/cue.py", line 983, in main
args.func(args)
File ".ci/cue.py", line 835, in prepare
sp.check_call([cc, '--version'])
File "/usr/lib/python2.7/subprocess.py", line 536, in check_call
retcode = call(*popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 523, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
The command "python .ci/cue.py prepare" failed and exited with 1 during .
The static-debug build with GCC on Windows failed with:
In file included from C:/Users/travis/.cache/base-7.0/include/pv/pvData.h:22,
from ../../src/server/pv/beaconServerStatusProvider.h:15,
from ../../src/server/pv/serverContext.h:13,
from ../../testApp/remote/testServer.cpp:8:
C:/Users/travis/.cache/base-7.0/include/pv/pvIntrospect.h:1128:21: note: declared here
FieldBuilderPtr addFixedArray(std::string const & name, ScalarType scalarType, std::size_t size) PVD_DEPRECATED_52;
^~~~~~~~~~~~~
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
The build has been terminated
The static-debug build with VS2017 failed with:
/usr/bin/sh: line 1: 2833 Segmentation fault ../../../../../../bin/windows-x64-static/msi.exe -D -I. -I.. -I../O.Common -I../../../../../../db -o ../O.Common/simmTest.db -S../simmTest.substitutions
> simmTest.db.d
make[5]: *** [../../../../../../configure/RULES.Db:477: ../O.Common/simmTest.db] Error -1073741819
make[4]: *** [../../../../../configure/RULES_ARCHS:58: install.windows-x64-static] Error 2
make[3]: *** [../../../configure/RULES_DIRS:85: std/rec.install] Error 2
make[3]: *** Waiting for unfinished jobs....
The command "python .ci/cue.py prepare" failed and exited with 2 during .
Your build has been stopped.
make[2]: *** [../../configure/RULES_DIRS:85: test.install] Error 2
make[1]: *** [../configure/RULES_DIRS:85: database.install] Error 2
make: *** [configure/RULES_DIRS:85: modules.install] Error 2
Thanks,
Mark
From: Core-talk <core-talk-bounces at aps.anl.gov>
On Behalf Of Ralph Lange via Core-talk
Sent: Monday, June 8, 2020 5:22 AM
To: EPICS Core Talk <core-talk at aps.anl.gov>
Subject: BETA: ci-scripts 3.0 (feat. Windows on Travis)
Dear all,
The next major update of the shared ci-scripts module is ready for some beta testing.
-
Single Python implementation for all services on all OSs
-
less maintenance effort: no more bash scripts
-
Support for native Windows builds on Travis
-
FAST: five parallel runners and cached dependency artifacts
As part of the streamlining process, the configuration had to change slightly (less on AppVeyor, more on Travis). Please refer to the (updated) documentation and examples on that branch for more details.
Up next (planned for version 3.1): support for GitHub Actions.
Please test and report any issues, observations and possible improvements.