Hello community,

here is the log from the commit of package dmtcp for openSUSE:Factory checked 
in at 2018-01-19 11:50:55
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/dmtcp (Old)
 and      /work/SRC/openSUSE:Factory/.dmtcp.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "dmtcp"

Fri Jan 19 11:50:55 2018 rev:25 rq:560483 version:2.5.2

Changes:
--------
--- /work/SRC/openSUSE:Factory/dmtcp/dmtcp.changes      2017-01-25 
23:35:41.371049632 +0100
+++ /work/SRC/openSUSE:Factory/.dmtcp.new/dmtcp.changes 2018-01-19 
11:51:27.576597408 +0100
@@ -1,0 +2,63 @@
+Wed Dec 27 13:17:07 UTC 2017 - ka...@ccs.neu.edu
+
+- Disabled some troublesome tests.
+- Updated to 2.5.2.
+  Release notes for 2.5.2:
+  ========================
+  * All fixes in Release DMTCP-2.4.9 are incorporated in this release.
+  * An incompatibility of DMTCP with Open MPI 1.10 when using orterun (mpirun)
+    was discovered. This does not affect recent versions, such as Open MPI 2.x.
+  * In some rare cases, open files were not properly restored due to
+    a use-after-free bug. This is now fixed.
+  * In some rare cases, one process had created a SysV shared memory object,
+    and a different process was assigned to restore it on restart. This
+    was not handled correctly, and is now fixed.
+  * Correctly restore CPU affinities of threads
+  * Virtualized SysV shared memory keys to avoid race condition on restart
+  * Fixed logic for checking if relative path to file was a duplicate
+    of another existing path
+  * The NSCD area for name service caching daemon was not handled correctly
+    in CentOS 6.8 and later correctly. Fixed now.
+  * The Linux sched.h include file for scheduling of cores was added to
+    satisfy some older Linux distros that needed it for compiling DMTCP.
+  * Fixed a regression in which --enable-debug (for verbose debug logs)
+    was not being properly written.
+  * The DMTCP coordinator was displaying a spurious warning, "Failed to find
+    coordinator IP address", because it did not check for a canoncial hostname.
+  * A related issue prevented DMTCP from working properly on some
+    SUSE/openSUSE distros.
+
+  Release notes for 2.5.1:
+  ========================
+  This release mostly provides added robustness.  Two notable items of
+  added functionality are:
+   i. DMTCP_RESTART_PAUSE and DMTCP_RESTART_PAUSE0 environment variables
+      for easier debugging upon initial restart
+   ii. The --debug-logs flag was added to dmtcp_launch/dmtcp_restart.
+       One can now turn on logging individually for separate plugins,
+       instead of only turning it on globally.
+  
+  An incompatibility of DMTCP with Open MPI 1.10 when using orterun (mpirun)
+  was discovered.  This may also affect some other versions of Open MPI 1.10.
+  This bug will be fixed in a future release.
+  
+  * Fixed an issue when starting multiple DMTCP coordinators on same host
+    at approximately the same time
+  * Fixed issue with PBS scheduler for HPC
+  * Fixed issue when restarting on a different host with a larger
+    limit on the number of open file descriptors
+  * dmtcp_launch/dmtcp_restart now accept '--debug-logs' flag to specify
+    which DMTCP plugins should produce logging information
+    (It used to be all or nothing.)
+  * Improved robustness for IB (InfiniBand) plugin
+  * Fixed DMTCP_RESTART_PAUSE and DMTCP_RESTART_PAUSE0 environment variables
+     for debugging upon restart
+  * The brk() call was failing on restart on Debian due to overly strict assert
+  * dmtcp_launch was hanging on some RHEL5 and RHEL6 due to deadlock with
+      libc low-level locks.  Fixed now.
+  * Updated tls_pid_offset in DMTCP to handle newer GLIBc (versions > 2.24)
+  * Fixed launch of 32-bit binary when forking/execing from a 64-bit executable
+  * Fixed issue that can affect a parent holding a malloc-lock while forking
+  * Fixed issue when a user thread calls 'dmtcp_get_coord_ckpt_dir()'
+
+-------------------------------------------------------------------

Old:
----
  2.5.0.tar.gz

New:
----
  2.5.2.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ dmtcp.spec ++++++
--- /var/tmp/diff_new_pack.A8YukL/_old  2018-01-19 11:51:28.484554610 +0100
+++ /var/tmp/diff_new_pack.A8YukL/_new  2018-01-19 11:51:28.484554610 +0100
@@ -18,24 +18,30 @@
 
 
 Name:           dmtcp
-Version:        2.5.0
+Version:        2.5.2
 Release:        0
 Summary:        Checkpoint/Restart functionality for Linux processes
 License:        LGPL-3.0+
 Group:          System/Packages
 Url:            https://github.com/%{name}
 Source0:        https://github.com/%{name}/%{name}/archive/%{version}.tar.gz
+
 BuildRequires:  gcc
 BuildRequires:  gcc-c++
 BuildRequires:  glibc-devel
 BuildRequires:  python-base
+
+# Disable spurious destbufferoverflow warning.
+BuildRequires:  -post-build-checks
+
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+
 # This package is functional only on i386 and x86_64 architectures.
 ExclusiveArch:  %{ix86} x86_64
 
 %description
 DMTCP (Distributed MultiThreaded Checkpointing) is a tool to transparently
-checkpointing the state of an arbitrary group of programs including
+checkpoint the state of an arbitrary group of programs including
 multi-threaded and distributed computations.  It operates directly on the user
 binary executable, with no Linux kernel modules or other kernel mods.
 
@@ -65,7 +71,15 @@
 
 %check
 make %{?_smp_mflags} tests
-./test/autotest.py --retry-once --slow || :
+
+# Test suite disabled for non-x86_64 architectures.
+%ifarch x86_64
+# Disable syscall-tester, file, and posix-mq tests until fixed upstream.
+sed -i -e's:\(runTest("syscall-tester"\):pass #\1:' test/autotest.py
+sed -i -e's:\(runTest("file\):pass #\1:' test/autotest.py
+sed -i -e's:\(runTest("posix-mq\):pass #\1:' test/autotest.py
+make AUTOTEST="--retry-once" check || :
+%endif
 
 %install
 %make_install

++++++ 2.5.0.tar.gz -> 2.5.2.tar.gz ++++++
++++ 12096 lines of diff (skipped)


Reply via email to