The character position was not correct with the Cocoa backend.
  (see https://sft.its.cern.ch/jira/browse/ROOT-6561)
Handle the case ROOT was built with configure/make to run the tutorials
Expect the hsimple.root in the current directory
New versions of FindCastor and FindPythia6
Convert the error stream before comparing with reference
Disable test-stressproof for the time being
Remove training spaces and try to avoid racing conditions when creating hsimple.root
Added missing dependency in tutorials
Fix bug in TAxis::Copy

The TAxis::Copy function did not correctly handle the case where
not all bins had labels.
Implement TH1::Clone

The previous Clone method called for a histogram relied on both
the I/O system and on Cint to function. This lead to either
data race conditions or synchronization points when working with
different  histograms on different threads. Using TClass to
create an empty instance and then calling Copy plus a bit of
cleanup allows different histograms to be uncoupled.
Avoid using "not" and "and" that makes compilation fail on Windows
Fix for ROOT-6830 (TUUID.h uuid.StreamerV1)
Revert change for ROOT-6830 (TUUID.h uuid.StreamerV1)
Fix for ROOT-6751 (etcdir not set)
Make caching of fProperty and fInterShowMembers thread safe

The setting of the caches held by fProperty and fInterShowMembers
can happen on different threads. Therefore the values themselves
are now atomic and appropriate locks are held when updating the values.
Take lock before calling cint

Must serialize access when getting type related information from
cint.
Added additional error reporting

While debugging a problem related to thread safety these additional
checks and error reports were very helpful.
Must take cint lock before calling TCint::CallFunc_Factory

Helgrind found that TCint::CallFunc_Factory indirectly updates
global cint state. Therefore one must take the cint lock before
calling the function. This was the only place (other than
TSelectorCint::Build) which calls this function without first
taking the lock.
Make G__FastAllocString cache thread safe

When using C++11, the cache used by G__FastAllocString utilizes
a non-locking thread safe circular buffer.
Synchronize construction of TApplication

It was possible for multiple threads to attempt construction of a
TApplication or for one thread to think the TApplication was already
constructed while another thread was in the process of doing the
construction.