Searched +full:check +full:- +full:each +full:- +full:commit (Results 1 – 7 of 7) sorted by relevance
| /petsc/lib/petsc/bin/maint/ |
| H A D | runjobs.py | 6 # runjobs.py [-f] [job1 job2 ... jobN] 10 # -f: when commits in the local "branch" are not in sync with "origin/branch" - runjobs.py will no… 11 # for the specified "jobs list". Use '-f' to force the creation of this commit [and then use '… 12 # branch's contents at GitLab] - if the intention is to overwrite these differences with your … 16 # lib/petsc/bin/maint/runjobs.py -f linux-cuda-pkgs 17 # lib/petsc/bin/maint/runjobs.py -f freebsd-cxx-pkgs-opt linux-clang-avx linux-clang-ubsan 18 …maint/runjobs.py -f $(grep -lE "download-(mpich|openmpi)" config/examples/arch-ci-*.py | cut -d '/… 20 # Note: If no jobs are listed, then all jobs in the pipeline are run but without a need to un-paus… 27 if ('-f' in jobs): 29 jobs.remove('-f') [all …]
|
| /petsc/doc/developers/contributing/ |
| H A D | pipelines.md | 14 :::{figure} /images/developers/pipeline-from-MR.png 21 To un-pause the pipeline, click the "play" button (or start a new one with "Run Pipeline" if necess… 23 :::{figure} /images/developers/run-paused-pipeline.png 27 Un-pausing a pipeline. 30 A pipeline consists of "Stages" each with multiple "Jobs". Every job is one configuration on one ma… 32 :::{figure} /images/developers/show-failure.png 41 :::{figure} /images/developers/find-exact-bad-job.png 49 Each test is a run of an example with a particular set of command line options 53 :::{figure} /images/developers/failed-examples.png 62 :::{figure} /images/developers/unfreed-memory.png [all …]
|
| /petsc/config/BuildSystem/config/ |
| H A D | package.py | 13 s -> (s0,s1,...s[n-1]), (s1,s2,...,sn), ... 42 …= None # path of the package installation point; for example /usr/local or /home/bsmith/mpich-2.0.1 44 … = '' # the version of the package that PETSc will build with the --download-package option 60 … # cannot tell the difference between user requiring it with --with-PACKAGE=1 and 65 self.gitcommit = None # Git commit to use for downloads 66 …self.gitcommitmain = None # Git commit to use for petsc/main or similar non-release branc… 67 …ile = None # File within the git clone - that has the gitcommit for the current build… 73 …self.liblist = [[]] # list of libraries we wish to check for (packages can override… 75 self.includes = [] # headers to check for 76 self.macros = [] # optional macros we wish to check for in the headers [all …]
|
| /petsc/doc/faq/ |
| H A D | index.md | 22 …e: A Guide to Good Style](https://www.cambridge.org/core/books/writing-scientific-software/2320670… 32 - Fast, **low-latency** interconnect; any ethernet (even 10 GigE) simply cannot provide 34 - High per-core **memory** performance. Each core needs to 43 many cores per memory socket and how much memory bandwidth for each. 69 fewer processes than cores and binding processes to separate sockets so that each process 72 - [MPICH2 binding with the Hydra process manager](https://github.com/pmodels/mpich/blob/main/doc/wi… 75 $ mpiexec.hydra -n 4 --binding cpu:sockets 78 - [Open MPI binding](https://www.open-mpi.org/faq/?category=tuning#using-paffinity) 81 $ mpiexec -n 4 --map-by socket --bind-to socket --report-bindings 84 - `taskset`, part of the [util-linux](https://github.com/karelzak/util-linux) package [all …]
|
| /petsc/ |
| H A D | .gitlab-ci.yml | 2 # stage-1 take only a few minutes; they do not run the full test suite or external packages. 4 # stage-2 runs on MCS systems and may take 10 to 15 minutes. They run the full test suite but with … 6 # stage-3 runs on MCS systems and may take an hour or more. They run the full test suite and heavil… 8 # The stage-(n) tests are only started if all of the stage-(n-1) tests run without error 13 - stage-1 14 - stage-2 15 - stage-3 16 - stage-4 19 GIT_CLEAN_FLAGS: -ffdxq 21 BASE_EXTRA_OPTIONS: -nox -nox_warning -malloc_dump [all …]
|
| /petsc/include/ |
| H A D | petscsys.h | 10 …PeOP - indicates an argument to a PETSc function is optional and one can pass `NULL` instead. This… 22 Put this in the function declaration in front of each variable that is optional 32 …PeNS - indicates a function that does not use the PETSc standard arguments which make it easy to g… 42 Shortened form of PETSc non-standard 49 …PeNSS - indicates a function that needs a special treatment in the C-side stub when generating the… 58 …lly but not the C stub, which should be added manually under the appropriate `ftn-custom` directory 61 Shortened form of PETSc non-standard stub 70 found automatically by the compiler due to the -I${PETSC_DIR}/${PETSC_ARCH}/include that 72 For --prefix installs the directory ${PETSC_ARCH} does not exist and petscconf.h is in the same 85 Feature test macros must be included before headers defined by IEEE Std 1003.1-2001 [all …]
|
| /petsc/include/petsc/private/valgrind/ |
| H A D | valgrind.h | 1 /* -*- c -*- 2 ---------------------------------------------------------------- 4 Notice that the following BSD-style license applies to this one 10 ---------------------------------------------------------------- 15 Copyright (C) 2000-2017 Julian Seward. All rights reserved. 48 ---------------------------------------------------------------- 50 Notice that the above BSD-style license applies to this one file 55 ---------------------------------------------------------------- 66 unchanged. When not running on valgrind, each client request 71 -DNVALGRIND) so that client requests are not even compiled in. */ [all …]
|