[gmx-users] GMX 2018 regression tests: cufftPlanMany R2C plan failure (error code 5)

Alex nedomacho at gmail.com
Thu Feb 8 18:29:00 CET 2018


uh, no sir.

>  9/39 Test  #9: GpuUtilsUnitTests ................***Timeout  30.43 sec


On Thu, Feb 8, 2018 at 10:25 AM, Mark Abraham <mark.j.abraham at gmail.com>
wrote:

> Hi,
>
> Those all succeeded. Does make check now also succeed?
>
> Mark
>
> On Thu, Feb 8, 2018 at 6:24 PM Alex <nedomacho at gmail.com> wrote:
>
> > Here you are:
> >
> > [==========] Running 35 tests from 7 test cases.
> > [----------] Global test environment set-up.
> > [----------] 7 tests from HostAllocatorTest/0, where TypeParam = int
> > [ RUN      ] HostAllocatorTest/0.EmptyMemoryAlwaysWorks
> > [       OK ] HostAllocatorTest/0.EmptyMemoryAlwaysWorks (5457 ms)
> > [ RUN      ] HostAllocatorTest/0.VectorsWithDefaultHostAllocato
> rAlwaysWorks
> > [       OK ] HostAllocatorTest/0.VectorsWithDefaultHostAllocato
> rAlwaysWorks
> > (2861 ms)
> > [ RUN      ] HostAllocatorTest/0.TransfersWithoutPinningWork
> > [       OK ] HostAllocatorTest/0.TransfersWithoutPinningWork (3254 ms)
> > [ RUN      ] HostAllocatorTest/0.FillInputAlsoWorksAfterCallingReserve
> > [       OK ] HostAllocatorTest/0.FillInputAlsoWorksAfterCallingReserve
> > (2221 ms)
> > [ RUN      ] HostAllocatorTest/0.TransfersWithPinningWorkWithCuda
> > [       OK ] HostAllocatorTest/0.TransfersWithPinningWorkWithCuda (3801
> ms)
> > [ RUN      ] HostAllocatorTest/0.ManualPinningOperationsWorkWithCuda
> > [       OK ] HostAllocatorTest/0.ManualPinningOperationsWorkWithCuda
> (2157
> > ms)
> > [ RUN      ] HostAllocatorTest/0.StatefulAllocatorUsesMemory
> > [       OK ] HostAllocatorTest/0.StatefulAllocatorUsesMemory (2179 ms)
> > [----------] 7 tests from HostAllocatorTest/0 (21930 ms total)
> >
> > [----------] 7 tests from HostAllocatorTest/1, where TypeParam = float
> > [ RUN      ] HostAllocatorTest/1.EmptyMemoryAlwaysWorks
> > [       OK ] HostAllocatorTest/1.EmptyMemoryAlwaysWorks (2739 ms)
> > [ RUN      ] HostAllocatorTest/1.VectorsWithDefaultHostAllocato
> rAlwaysWorks
> > [       OK ] HostAllocatorTest/1.VectorsWithDefaultHostAllocato
> rAlwaysWorks
> > (2731 ms)
> > [ RUN      ] HostAllocatorTest/1.TransfersWithoutPinningWork
> > [       OK ] HostAllocatorTest/1.TransfersWithoutPinningWork (3281 ms)
> > [ RUN      ] HostAllocatorTest/1.FillInputAlsoWorksAfterCallingReserve
> > [       OK ] HostAllocatorTest/1.FillInputAlsoWorksAfterCallingReserve
> > (2164 ms)
> > [ RUN      ] HostAllocatorTest/1.TransfersWithPinningWorkWithCuda
> > [       OK ] HostAllocatorTest/1.TransfersWithPinningWorkWithCuda (3908
> ms)
> > [ RUN      ] HostAllocatorTest/1.ManualPinningOperationsWorkWithCuda
> > [       OK ] HostAllocatorTest/1.ManualPinningOperationsWorkWithCuda
> (2202
> > ms)
> > [ RUN      ] HostAllocatorTest/1.StatefulAllocatorUsesMemory
> > [       OK ] HostAllocatorTest/1.StatefulAllocatorUsesMemory (2261 ms)
> > [----------] 7 tests from HostAllocatorTest/1 (19287 ms total)
> >
> > [----------] 7 tests from HostAllocatorTest/2, where TypeParam =
> > gmx::BasicVector<float>
> > [ RUN      ] HostAllocatorTest/2.EmptyMemoryAlwaysWorks
> > [       OK ] HostAllocatorTest/2.EmptyMemoryAlwaysWorks (2771 ms)
> > [ RUN      ] HostAllocatorTest/2.VectorsWithDefaultHostAllocato
> rAlwaysWorks
> > [       OK ] HostAllocatorTest/2.VectorsWithDefaultHostAllocato
> rAlwaysWorks
> > (2846 ms)
> > [ RUN      ] HostAllocatorTest/2.TransfersWithoutPinningWork
> > [       OK ] HostAllocatorTest/2.TransfersWithoutPinningWork (3283 ms)
> > [ RUN      ] HostAllocatorTest/2.FillInputAlsoWorksAfterCallingReserve
> > [       OK ] HostAllocatorTest/2.FillInputAlsoWorksAfterCallingReserve
> > (2131 ms)
> > [ RUN      ] HostAllocatorTest/2.TransfersWithPinningWorkWithCuda
> > [       OK ] HostAllocatorTest/2.TransfersWithPinningWorkWithCuda (3833
> ms)
> > [ RUN      ] HostAllocatorTest/2.ManualPinningOperationsWorkWithCuda
> > [       OK ] HostAllocatorTest/2.ManualPinningOperationsWorkWithCuda
> (2232
> > ms)
> > [ RUN      ] HostAllocatorTest/2.StatefulAllocatorUsesMemory
> > [       OK ] HostAllocatorTest/2.StatefulAllocatorUsesMemory (2164 ms)
> > [----------] 7 tests from HostAllocatorTest/2 (19261 ms total)
> >
> > [----------] 3 tests from AllocatorTest/0, where TypeParam =
> > gmx::Allocator<float, gmx::HostAllocationPolicy>
> > [ RUN      ] AllocatorTest/0.AllocatorAlignAllocatesWithAlignment
> > [       OK ] AllocatorTest/0.AllocatorAlignAllocatesWithAlignment (0 ms)
> > [ RUN      ] AllocatorTest/0.VectorAllocatesAndResizesWithAlignment
> > [       OK ] AllocatorTest/0.VectorAllocatesAndResizesWithAlignment (0
> ms)
> > [ RUN      ] AllocatorTest/0.VectorAllocatesAndReservesWithAlignment
> > [       OK ] AllocatorTest/0.VectorAllocatesAndReservesWithAlignment (0
> ms)
> > [----------] 3 tests from AllocatorTest/0 (0 ms total)
> >
> > [----------] 3 tests from AllocatorTest/1, where TypeParam =
> > gmx::Allocator<int, gmx::HostAllocationPolicy>
> > [ RUN      ] AllocatorTest/1.AllocatorAlignAllocatesWithAlignment
> > [       OK ] AllocatorTest/1.AllocatorAlignAllocatesWithAlignment (0 ms)
> > [ RUN      ] AllocatorTest/1.VectorAllocatesAndResizesWithAlignment
> > [       OK ] AllocatorTest/1.VectorAllocatesAndResizesWithAlignment (0
> ms)
> > [ RUN      ] AllocatorTest/1.VectorAllocatesAndReservesWithAlignment
> > [       OK ] AllocatorTest/1.VectorAllocatesAndReservesWithAlignment (0
> ms)
> > [----------] 3 tests from AllocatorTest/1 (0 ms total)
> >
> > [----------] 3 tests from AllocatorTest/2, where TypeParam =
> > gmx::Allocator<gmx::BasicVector<float>, gmx::HostAllocationPolicy>
> > [ RUN      ] AllocatorTest/2.AllocatorAlignAllocatesWithAlignment
> > [       OK ] AllocatorTest/2.AllocatorAlignAllocatesWithAlignment (0 ms)
> > [ RUN      ] AllocatorTest/2.VectorAllocatesAndResizesWithAlignment
> > [       OK ] AllocatorTest/2.VectorAllocatesAndResizesWithAlignment (0
> ms)
> > [ RUN      ] AllocatorTest/2.VectorAllocatesAndReservesWithAlignment
> > [       OK ] AllocatorTest/2.VectorAllocatesAndReservesWithAlignment (0
> ms)
> > [----------] 3 tests from AllocatorTest/2 (0 ms total)
> >
> > [----------] 5 tests from PinnedMemoryCheckerTest
> > [ RUN      ] PinnedMemoryCheckerTest.DefaultContainerIsRecognized
> > [       OK ] PinnedMemoryCheckerTest.DefaultContainerIsRecognized (3248
> ms)
> > [ RUN      ] PinnedMemoryCheckerTest.NonpinnedContainerIsRecognized
> > [       OK ] PinnedMemoryCheckerTest.NonpinnedContainerIsRecognized
> (2752
> > ms)
> > [ RUN      ] PinnedMemoryCheckerTest.PinnedContainerIsRecognized
> > [       OK ] PinnedMemoryCheckerTest.PinnedContainerIsRecognized (2709
> ms)
> > [ RUN      ] PinnedMemoryCheckerTest.DefaultCBufferIsRecognized
> > [       OK ] PinnedMemoryCheckerTest.DefaultCBufferIsRecognized (2675
> ms)
> > [ RUN      ] PinnedMemoryCheckerTest.PinnedCBufferIsRecognized
> > [       OK ] PinnedMemoryCheckerTest.PinnedCBufferIsRecognized (2686 ms)
> > [----------] 5 tests from PinnedMemoryCheckerTest (14071 ms total)
> >
> > [----------] Global test environment tear-down
> > [==========] 35 tests from 7 test cases ran. (74549 ms total)
> > [  PASSED  ] 35 tests.
> >
> >
> > On Thu, Feb 8, 2018 at 10:00 AM, Szilárd Páll <pall.szilard at gmail.com>
> > wrote:
> >
> > > It might help to know which of the unit test(s) in that group stall?
> Can
> > > you run it manually (bin/gpu_utils-test) and report back the standard
> > > output?
> > >
> > >
> > > --
> > > Szilárd
> > >
> > > On Thu, Feb 8, 2018 at 3:56 PM, Alex <nedomacho at gmail.com> wrote:
> > >
> > > > Nope, still persists after reboot and no other jobs running:
> > > >  9/39 Test  #9: GpuUtilsUnitTests ................***Timeout  30.59
> sec
> > > >
> > > > Any additional suggestions?
> > > >
> > > > --
> > > > Gromacs Users mailing list
> > > >
> > > > * Please search the archive at http://www.gromacs.org/Support
> > > > /Mailing_Lists/GMX-Users_List before posting!
> > > >
> > > > * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> > > >
> > > > * For (un)subscribe requests visit
> > > > https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-users
> or
> > > > send a mail to gmx-users-request at gromacs.org.
> > > >
> > > --
> > > Gromacs Users mailing list
> > >
> > > * Please search the archive at http://www.gromacs.org/
> > > Support/Mailing_Lists/GMX-Users_List before posting!
> > >
> > > * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> > >
> > > * For (un)subscribe requests visit
> > > https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-users or
> > > send a mail to gmx-users-request at gromacs.org.
> > >
> > --
> > Gromacs Users mailing list
> >
> > * Please search the archive at
> > http://www.gromacs.org/Support/Mailing_Lists/GMX-Users_List before
> > posting!
> >
> > * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> >
> > * For (un)subscribe requests visit
> > https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-users or
> > send a mail to gmx-users-request at gromacs.org.
> --
> Gromacs Users mailing list
>
> * Please search the archive at http://www.gromacs.org/
> Support/Mailing_Lists/GMX-Users_List before posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-users or
> send a mail to gmx-users-request at gromacs.org.
>


More information about the gromacs.org_gmx-users mailing list