Giter Club home page Giter Club logo

libcircle's People

Contributors

adammoody avatar bringhurst avatar jlafon avatar juliankunkel avatar junghans avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

libcircle's Issues

v0.3: Tests segfaults on s390x

FAIL: check_queue
============================================================================
Testsuite summary for LibCircle 0.3.0
============================================================================
# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
============================================================================
See tests/test-suite.log
Please report to [email protected]
============================================================================
make[3]: Leaving directory '/builddir/build/BUILD/libcircle-0.3/openmpi/tests'
make[3]: *** [Makefile:687: test-suite.log] Error 1
make[2]: Leaving directory '/builddir/build/BUILD/libcircle-0.3/openmpi/tests'
make[2]: *** [Makefile:795: check-TESTS] Error 2
make[1]: *** [Makefile:869: check-am] Error 2
make[1]: Leaving directory '/builddir/build/BUILD/libcircle-0.3/openmpi/tests'
make: *** [Makefile:681: check-recursive] Error 1
make: Leaving directory '/builddir/build/BUILD/libcircle-0.3/openmpi'
+ cat openmpi/tests/test-suite.log
===========================================
   LibCircle 0.3.0: tests/test-suite.log
===========================================
# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: check_queue
=================
Running suite(s): check_queue
[buildvm-s390x-02:2699362] *** Process received signal ***
[buildvm-s390x-02:2699362] Signal: Segmentation fault (11)
[buildvm-s390x-02:2699362] Signal code: Address not mapped (1)
[buildvm-s390x-02:2699362] Failing at address: 0xfffffffffffff000
[buildvm-s390x-02:2699362] [ 0] [0x3fff6b7cf60]
[buildvm-s390x-02:2699362] [ 1] /lib64/libhwloc.so.15(+0x44870)[0x3ff96244870]
[buildvm-s390x-02:2699362] [ 2] /lib64/libhwloc.so.15(hwloc_topology_load+0xe6)[0x3ff96216ae6]
[buildvm-s390x-02:2699362] [ 3] /usr/lib64/openmpi/lib/libopen-pal.so.40(opal_hwloc_base_get_topology+0xfe2)[0x3ff966840d2]
[buildvm-s390x-02:2699362] [ 4] /usr/lib64/openmpi/lib/openmpi/mca_ess_hnp.so(+0x508c)[0x3ff95a8508c]
[buildvm-s390x-02:2699362] [ 5] /usr/lib64/openmpi/lib/libopen-rte.so.40(orte_init+0x2d2)[0x3ff96a912d2]
[buildvm-s390x-02:2699362] [ 6] /usr/lib64/openmpi/lib/libopen-rte.so.40(orte_daemon+0x26a)[0x3ff96a3c72a]
[buildvm-s390x-02:2699362] [ 7] /lib64/libc.so.6(__libc_start_main+0x10a)[0x3ff9672bb4a]
[buildvm-s390x-02:2699362] [ 8] orted(+0x954)[0x2aa3a900954]
[buildvm-s390x-02:2699362] *** End of error message ***
[buildvm-s390x-02:2699366] *** Process received signal ***
[buildvm-s390x-02:2699366] Signal: Segmentation fault (11)
[buildvm-s390x-02:2699366] Signal code: Address not mapped (1)
[buildvm-s390x-02:2699366] Failing at address: 0xfffffffffffff000

Build log here
Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1863982

Checkpointing

We should write in code to allow for checkpointing and restarting from checkpoint file(s).

Internal Queue Unit Test Failure

75%: Checks: 4, Failures: 1, Errors: 0
check_queue.c:38:F:Core:test_queue_pop_empty:0: Something was poped from an empty queue.
FAIL: check_queue

Aborting,exiting,failing.

We should choose how a user can exit unhappily. Perhaps CIRCLE_abort(), which should checkpoint if so configured.

check_queue test fails on s390x under Fedora Rawhide

From https://koji.fedoraproject.org/koji/taskinfo?taskID=40937782, only s390x fails:

===========================================
   LibCircle 0.3.0: tests/test-suite.log
===========================================

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: check_queue
=================

Running suite(s): check_queue
[d8f6aae043a2464bb6c5907f844aeb8c:19415] PMIX ERROR: ERROR in file dstore_segment.c at line 110
[d8f6aae043a2464bb6c5907f844aeb8c:19415] PMIX ERROR: OUT-OF-RESOURCE in file gds_ds21_lock_pthread.c at line 176
[d8f6aae043a2464bb6c5907f844aeb8c:19415] *** Process received signal ***
[d8f6aae043a2464bb6c5907f844aeb8c:19415] Signal: Segmentation fault (11)
[d8f6aae043a2464bb6c5907f844aeb8c:19415] Signal code: Address not mapped (1)
[d8f6aae043a2464bb6c5907f844aeb8c:19415] Failing at address: (nil)
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 0] [0x4001bce850]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 1] /usr/lib64/pmix/mca_gds_ds21.so(+0x1ef0)[0x4001396ef0]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 2] /usr/lib64/pmix/mca_gds_ds21.so(+0x246e)[0x400139746e]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 3] /lib64/libmca_common_dstore.so.1(pmix_common_dstor_add_nspace+0x29a)[0x40013aaeda]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 4] /lib64/libpmix.so.2(+0x4e98e)[0x40011ba98e]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 5] /lib64/libevent-2.1.so.6(+0x276ec)[0x4000cf06ec]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 6] /lib64/libevent-2.1.so.6(event_base_loop+0x644)[0x4000cf0fd4]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 7] /lib64/libpmix.so.2(+0x7ee0e)[0x40011eae0e]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 8] /lib64/libpthread.so.0(+0x9ab8)[0x4000903ab8]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [ 9] /lib64/libc.so.6(+0x120a46)[0x4000a3ea46]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] [10] [0x0]
[d8f6aae043a2464bb6c5907f844aeb8c:19415] *** End of error message ***
[d8f6aae043a2464bb6c5907f844aeb8c:19413] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ess_singleton_module.c at line 716
[d8f6aae043a2464bb6c5907f844aeb8c:19413] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ess_singleton_module.c at line 172
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
oPen MPI developer):

  orte_ess_init failed

To reproduce this run the following on Fedora:

dnf install fedpkg
fedpkg clone -a libcircle
cd libcircle
fedpkg srpm
mock -r fedora-rawhide-s390x --no-clean libcircle-0.3-1.fc32.src.rpm
mock -r fedora-rawhide-s390x --shell
cd /builddir/build/BUILD/libcircle-0.3/openmpi/tests

/cc @opoplawski

libcircle-3.0 :: configure does not detect pkg-config

Hello,

working from https://github.com/hpc/libcircle/releases/download/v0.3/libcircle-0.3.0.tar.gz

after running autogen.sh

module load openmpi/4.0.2 gcc/9.2.0 pkg-config/0.29.2

I tried to run ./configure and got

[gensoft@e211aa82115c libcircle-0.3.0]$ ./configure 
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking for pkg-config... yes
configure: error: *** Libcircle requires the pkg-config macros to be available!

problem does not arise whith version 0.2.1-rc.1
if I grab configure.ac from 0.2.1-rc1, edit Makefile.am to remove "unit tests if we found libcheck"
run ./autogen.sh
configure runs fine

regards

Eric

Documentation for Reduction

Not sure how to do this yet to make it easy for beginners -- just creating this issue for future reference.

Compiling in Cray Env

Hello,
I'm trying to compile libcircle on a Cray machine where the Cray MPICH binaries are
cc (for mpicc)
CC (for mpicxx)

If I try:

CC=cc CXX=CC MPICC=cc ./configure --prefix=$PWD/install --host=x86_64-suse-linux-gnu

I see this error:

checking for cc... /opt/cray/pe/craype/2.5.14/bin/cc
Checking whether /opt/cray/pe/craype/2.5.14/bin/cc responds to '-showme:compile'... no
Checking whether /opt/cray/pe/craype/2.5.14/bin/cc responds to '-showme'... no
Checking whether /opt/cray/pe/craype/2.5.14/bin/cc responds to '-compile-info'... no
Checking whether /opt/cray/pe/craype/2.5.14/bin/cc responds to '-show'... no
Unable to find suitable MPI Compiler. Try setting MPICC.
configure: error: You should check to see if MPI is setup properly.

This option -showme appears to be not supported by Cray MPICH. Any suggestions on how to continue?

Thanks

Doesn't build on TOSS

We need to make this compatible with the TOSS autotools. I started hacking the configure.ac, but eventually gave up. The automate and autoconf versions of TOSS are not compatible with the requirements from configure.ac.

Output after hacking configure.ac:

./libtool: line 852: X--tag=CC: command not found
./libtool: line 885: libtool: ignoring unknown tag : command not found
./libtool: line 852: X--mode=compile: command not found
./libtool: line 1018: *** Warning: inferring the mode of operation is deprecated.: command not found
./libtool: line 1019: *** Future versions of Libtool will require --mode=MODE be specified.: command not found
./libtool: line 1162: Xgcc: command not found

Objects processed messages during run

I started using libcircle again. When I used this in June 2021 I would get messages like this in the log during a run...

1624401087:0:libcircle/token.c:207:Objects processed: 76456492 ...
1624401099:0:libcircle/token.c:207:Objects processed: 77419312 ...
1624401111:0:libcircle/token.c:207:Objects processed: 78430963 ...
1624401134:0:libcircle/token.c:207:Objects processed: 79577820 ...
1624401146:0:libcircle/token.c:207:Objects processed: 81504253 ...
1624401155:0:libcircle/token.c:207:Objects processed: 82556239 ...
1624401166:0:libcircle/token.c:207:Objects processed: 83496932 ...

These messages are now not appearing. In the code I see they are ate log level INFO. I still get the summary at the end with the number processed for each rank and then the total objects processed. This is also at log level INFO. What do I need to do to get these messages appearing again ? I have a python script that draws a graph of progress over time from these messages which is really useful so really want to get this functionality back.

check.h not found when building libcircle

G'Day,
On cloning and building libcircle using 'make all check' there is an error in
completing the check, as the file check.h does not exist:

[libcircle-src]$ make check
Making check in tests
make[1]: Entering directory '/libcircle-src/tests'
make  check_queue
make[2]: Entering directory '/libcircle-src/tests'
  CC     check_queue-check_queue.o
check_queue.c:1:19: error: check.h: No such file or directory
check_queue.c:24: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'START_TEST'
check_queue.c:49: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'START_TEST'
check_queue.c:80: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'START_TEST'
check_queue.c:166: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'Suite'
check_queue.c: In function 'main':
check_queue.c:187: error: 'Suite' undeclared (first use in this function)
check_queue.c:187: error: (Each undeclared identifier is reported only once
check_queue.c:187: error: for each function it appears in.)
check_queue.c:187: error: 's' undeclared (first use in this function)
check_queue.c:188: error: 'SRunner' undeclared (first use in this function)
check_queue.c:188: error: 'sr' undeclared (first use in this function)
check_queue.c:190: error: 'CK_NORMAL' undeclared (first use in this function)
make[2]: *** [check_queue-check_queue.o] Error 1
make[2]: Leaving directory '/libcircle-src/tests'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory '/libcircle-src/tests'
make: *** [check-recursive] Error 1

issue with finding MPI when building with spack

I'm getting a very strange issue when building with spack. It appears that configure finds MPI correctly, but then fails.

     77    checking for stdlib.h... (cached) yes
     78    checking for GNU libc compatible malloc... yes
     79    checking for /usr/local/bin/mpicc... /usr/local/bin/mpicc
     80    Checking whether /usr/local/bin/mpicc responds to '-showme:compile'.
           .. no
     81    Checking whether /usr/local/bin/mpicc responds to '-showme'... no
     82    Checking whether /usr/local/bin/mpicc responds to '-compile-info'...
            yes
  >> 83    configure: error: You should check to see if MPI is setup properly.

This does not happen when manually building libcircle. Does the build system properly detect the MPI that spack passes, or does it rely on hard coded paths?

Compiler warning

libcircle/token.c: In function ‘CIRCLE_token_recv’:
libcircle/token.c:490: warning: comparison between pointer and integer

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.