Re: [Boost-bugs] [Boost C++ Libraries] #11529: regression: boost::archive::archive_exception exception during serialization non latin1 strings to xm

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11529: regression: boost::archive::archive_exception exception during serialization non latin1 strings to xm
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-10-06 15:51:45

#11529: regression: boost::archive::archive_exception exception during
serialization non latin1 strings to xm
-------------------------------+---------------------------
  Reporter:  nikolay@…         |      Owner:  ramey
      Type:  Bugs              |     Status:  reopened
 Milestone:  To Be Determined  |  Component:  serialization
   Version:  Boost 1.58.0      |   Severity:  Regression
Resolution:                    |   Keywords:
-------------------------------+---------------------------

Comment (by ramey):

 I'd certainly be happy to look at them.

 Do you run the serialization test suite on your own equipment.  This would
 be very helpful and isn't very hard.

 a) build some boost tools b2, process_jam_log, library_status
 b) cd libs/serialization/test
 c) invoke library_test ...
 d) deal with setting up of b2 user config, site config, environment
 variables etc.

 Of course this is pain in the rear.  And probably "wastes" a workday.  But
 in my view for an enterprise which depends upon boost software - it's a
 very good investment.  It verifies that the the boost libraries you use
 actually pass all tests on your local combination of compiler, compiler
 version, operating system etc.

 If you want to submit a few tests, I'd like it if you looked at the tests
 I have and follow the scheme that I use so I don't have to adapt them.
 This also means

 a) not introducing dependencies on other boost libraries
 b) using the "test_tools.hp"
 c) using the macros for stream settings and archive settings.  This means
 that serialization of one data structure can be tested with all archives
 types without any extra effort.

 Alternatively, you can add tests to the CMakeLists.txt file that you find
 there.  This isn't as elaborate as the Bjam setup.  But it does work well
 for me when I develop/debug using the IDE - which is most of the time.

 My usual regimen is:

 a) get a complaint at this site
 b) make a test for it.
 c) put it into the test_z file
 d) debug it and make fixes
 e) build and test with jam - using the gcc compiler - I need to use at
 least two compilers - more would be better.
 f) maybe add to the official test suite - update CMakeList.txt and jam
 files
 g) test again
 h) upload to the develop branch - cross fingers.
 i) await results on the develop branch
 j) merge develop into release.

 Other points.

 a) you really should have cygwin installed.
 b) You really should become familiar with GIT. It's included in cygwin.
 For windows you can use SourceTree GUI for git which I find convenient.

 So that's all you need to become a boost developer!

 Robert Ramey

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/11529#comment:15>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.