Hi,
I wondered why I have not seen anything in our Jenkins and just found
out that the settings were broken and I have not actually built anything
for the last few weeks.
After fixing it I got success for 3.14, 3.15, 3.16 and failure for 7.
../../src/factory/FieldCreateFactory.cpp: In member function `size_t
epics::pvData::Structure::getFieldIndex(const std::string&) const':
../../src/factory/FieldCreateFactory.cpp:529: warning: converting of
negative value `-0x00000000000000001' to `size_t'
../../src/factory/FieldCreateFactory.cpp: In member function `size_t
epics::pvData::Union::getFieldIndex(const std::string&) const':
../../src/factory/FieldCreateFactory.cpp:723: warning: converting of
negative value `-0x00000000000000001' to `size_t'
../../src/factory/FieldCreateFactory.cpp: In static member function
`static void epics::pvData::FieldCreate::Helper::cache(const
epics::pvData::FieldCreate*, boost::shared_ptr<T>&) [with FLD =
epics::pvData::BoundedString]':
../../src/factory/FieldCreateFactory.cpp:1134: instantiated from here
../pv/pvIntrospect.h:352: error: `unsigned int
epics::pvData::Field::m_hash' is private
../../src/factory/FieldCreateFactory.cpp:58: error: within this context
../../src/factory/FieldCreateFactory.cpp:1134: instantiated from here
This error actually popped up several times.
Dirk
On 14.09.2018 23:10, Andrew Johnson wrote:
So why hasn't Travis been sending me emails about the broken epics-base
builds that I've been pushing? It's a shame that the final 3.14.12.8
build failed on Travis, but I'm not going to fix it and re-tag. I
assumed that the absence of emails from it was an indication of no build
problems, but no... (I haven't even checked Appveyor).
I really don't understand how/when Travis (and Appveyor for that matter)
decide when they should email me; can anyone explain where/how I should
change my settings to ensure that it does?
- Andrew
