Re: hanging tests

["Johnson, Andrew N. via Core-talk" <core-talk@aps.anl.gov>]

Hello Heinz,

Can you run the netget test which is hanging by hand and send me the
output please. Do this in your base-7.0 source tree:

cd modules/database/test/std/rec/O.linux-x86_64
perl netget.t

and send me whatever it outputs. You may have to Control-C if it hangs.

Thanks,

- Andrew


On 11/10/18 10:20 AM, Heinz P. Junkes wrote:
> I also have a similar problem as Dirk, but with epics-base master
> 
> I finally managed to translate epics-base with RTEMS 4.10 (with the
> Rtems builder system) so far. Everything seems to work, too.
> 
> I'm still stuck in tap file generation. Although in different ways
> (depending on option with -j, with j 2, with and without -O,...) but
> always here:
> 
> perl -CSD netget.t -tap > netget.tap
> make[5]: Nothing to be done for 'tapfiles'.
> make[5]: Leaving directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/std/filters/O.linux-x86_64'
> 
> make -C O.RTEMS-pc386-qemu -f ../Makefile TOP=../../../.. \
>     T_A=RTEMS-pc386-qemu tapfiles
> make[5]: Entering directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/std/filters/O.RTEMS-pc386-qemu'
> 
> make[5]: Nothing to be done for 'tapfiles'.
> make[5]: Leaving directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/std/filters/O.RTEMS-pc386-qemu'
> 
> make[4]: Leaving directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/std/filters'
> 
> make -C ./tools tapfiles
> make[4]: Entering directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/tools'
> 
> make -C O.linux-x86_64 -f ../Makefile TOP=../../.. \
>     T_A=linux-x86_64 tapfiles
> make[5]: Entering directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/tools/O.linux-x86_64'
> 
> make[5]: Nothing to be done for 'tapfiles'.
> make[5]: Leaving directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/tools/O.linux-x86_64'
> 
> make -C O.RTEMS-pc386-qemu -f ../Makefile TOP=../../.. \
>     T_A=RTEMS-pc386-qemu tapfiles
> make[5]: Entering directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/tools/O.RTEMS-pc386-qemu'
> 
> make[5]: Nothing to be done for 'tapfiles'.
> make[5]: Leaving directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/tools/O.RTEMS-pc386-qemu'
> 
> make[4]: Leaving directory
> '/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/modules/database/test/tools'
> 
> 
> 
> ^C/home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/configure/RULES_BUILD:379:
> recipe for target 'netget.tap' failed
> make[5]: [netget.tap] Interrupt (ignored)
> /home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/configure/RULES_ARCHS:58:
> recipe for target 'tapfiles.linux-x86_64' failed
> make[4]: *** [tapfiles.linux-x86_64] Interrupt
> /home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/configure/RULES_DIRS:84:
> recipe for target 'std/rec.tapfiles' failed
> make[3]: *** [std/rec.tapfiles] Interrupt
> /home/h1/WIP/EPICS_PORT/4.10/epics-base/epics-base/configure/RULES_DIRS:84:
> recipe for target 'test.tapfiles' failed
> make[2]: *** [test.tapfiles] Interrupt
> ../configure/RULES_DIRS:84: recipe for target 'database.tapfiles' failed
> make[1]: *** [database.tapfiles] Interrupt
> configure/RULES_DIRS:84: recipe for target 'modules.tapfiles' failed
> make: *** [modules.tapfiles] Interrupt
> 
> I'm in sync with the master:
> 
> [h1@earth epics-base (7.0 *)]$ git fetch
> remote: Enumerating objects: 45, done.
> remote: Counting objects: 100% (45/45), done.
> remote: Compressing objects: 100% (4/4), done.
> remote: Total 19 (delta 15), reused 19 (delta 15), pack-reused 0
> Unpacking objects: 100% (19/19), done.
> From https://github.com/epics-base/epics-base
>    00d937c..30268e3  7.0        -> origin/7.0
> [h1@earth epics-base (7.0 *)]$ git status
> On branch 7.0
> Your branch is behind 'origin/7.0' by 2 commits, and can be fast-forwarded.
>   (use "git pull" to update your local branch)
> 
> Changes not staged for commit:
>   (use "git add <file>..." to update what will be committed)
>   (use "git checkout -- <file>..." to discard changes in working directory)
> 
>     modified:   configure/CONFIG_SITE
>     modified:   configure/os/CONFIG_SITE.Common.RTEMS
>     modified:   modules/libcom/src/osi/os/RTEMS/osdThread.c
> 
> no changes added to commit (use "git add" and/or "git commit -a")
> 
> I'll discuss it with Andrew over a beer tonight.
> 
> Heinz
> 
> 
> 
> 
> 
> On 11/9/18 4:54 PM, Dirk Zimoch wrote:
>>
>>
>> On 09.11.2018 06:07, Johnson, Andrew N. wrote:
>>> Hi Dirk,
>>>
>>> If you have (or can install) GNUmake 4.x there is a -O option that
>>> separates the output from different builds. This makes parallel jobs
>>> reasonable to use.
>>>
>>> The ‘tapfiles’ target was added in Base-3.14.12.6 and is documented
>>> in the release notes for that release. That is generally the only
>>> place I document build system features because the AppDevGuide
>>> chapter is so old. After ‘make -O -j tapfiles’ you can do ‘make
>>> test-results’ to have the results printed, or ‘make junitfiles’ to
>>> feed junit results into a Jenkins plugin if you don’t like the tap
>>> plugin. Those are also documented in the release notes...
>>>
>>> - Andrew
>>>
>>
>> Found it. Thanks. I will try to use it in Jenkins with the TAP plugin.
>> Dirk

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon