docs: Fix broken links
Sys: dump filename and linenumber in filename:linenumberSo that in supported IDEs such as VS Code one can click the url-like filename:linenumber to go to that line
Merge remote-tracking branch 'origin/balay/add-valgrind.h'valgrind.h: add to petsc repoSee merge request petsc/petsc!4094
PetscStack : check for correct push/popEnforce checkstack for CI jobsFixes from testsuite
valgrind.h: add to petsc at include/private/valgrind
Merge remote-tracking branch 'origin/release'
Begin adding missing descriptions to manual pagesCommit-type: bug-fix, docs-onlyReported-by: sowing error detection
Update badsource rules- Zero or more spaces are not allowed for more returning types- zero spaces not allowed for for|if|while
Add pointers to https://docs.nvidia.com/cuda/cuda-memcheck/index.html into PETSc source and docsThese are added in the same locations as mentions of valgrindCommit-type: error-checking, documenta
Add pointers to https://docs.nvidia.com/cuda/cuda-memcheck/index.html into PETSc source and docsThese are added in the same locations as mentions of valgrindCommit-type: error-checking, documentation\spend 5mThanks-to: Jacob Faibussowitsch <jacob.fai@gmail.com>
show more ...
Minor fixesUnneeded dependency for Htool + typo
Remove use of * at beginning of comment line and /** and **/
Remove all double blank lines from sourceCommit-type: petsc-style/2h
Cleanup output of PetscStackView()Commit-type: improved error clarity/spend 5m
Linter using libClang that checks PetscValidHeaderSpecifcType, PetscValidHeaderSpecific, PetscValidHeader, PetscValid[XXX]Pointer, PetscValidType, PetscCheckSameComm, PetscValidLogicalCollectiveXXX f
Linter using libClang that checks PetscValidHeaderSpecifcType, PetscValidHeaderSpecific, PetscValidHeader, PetscValid[XXX]Pointer, PetscValidType, PetscCheckSameComm, PetscValidLogicalCollectiveXXX for validity. Automatically generates diff files for problems with a known solution.
Check that PETSc is returning appropriate error codes to C main() program.When run on UTK NVIDIA GPU system it never indicates an inapproproriate error code returned up to main, though the test har
Check that PETSc is returning appropriate error codes to C main() program.When run on UTK NVIDIA GPU system it never indicates an inapproproriate error code returned up to main, though the test harness receives many inappropriate error codes. This indicates that something after the PETSc program is changing the error code. Bash shell?I think this means that the test harness should always issue a retry for any #define PETSC_ERR_MAX_VALUE 99
Merge branch 'barry/2021-04-09/fix-long-error-codes/release' into 'release'Do not set higher bits in error codes since error codes should never be larger than 255See merge request petsc/petsc!3845
Do not set higher bits in error codes since error codes should never be larger than 255These higher bits were apparently causing the confusing error codes produced in the CI when GPU jobsran out o
Do not set higher bits in error codes since error codes should never be larger than 255These higher bits were apparently causing the confusing error codes produced in the CI when GPU jobsran out of resources.Do not trap SIGTERM with OpenMPI since OpenMPI uses it to shut down MPI jobs and thisproduces identical confusing messages to the user/spend 6h
Add proper error return codes for cuSolver error checker. CHKERRCUSOLVER()Don't check PetscCUDAInitialized in CHKERRCU* routines since it will not be set yet/spend 2h
PetscSignalHandlerDefault(): extra space
SYS: print errors with filename:lineSo that it is easier to open with other tools such as vim, vscode
CHKERRQ() -> CHKERRMPI()
PetscError: add missing PETSC_ERR_GPU string
Insure that PetscErrorPrintfHilight() does not use special charactors while runningtest harness by skipping highlighting if PETSC_STDERR is PETSC_STDOUT.Remove sed handling of special hightlightin
Insure that PetscErrorPrintfHilight() does not use special charactors while runningtest harness by skipping highlighting if PETSC_STDERR is PETSC_STDOUT.Remove sed handling of special hightlighting in output from PetscErrorPrintfHilight() becauseit was not portable to all systems. And it would result say two different files where the same.Remove detailed printing from ts/tutorials/advection-diffusion-reaction/ex3.c output because eachmachine uses a slighly different number of function evaluations, etc.Commit-type: portability-fix, testing-fix/spend 3.5h
Convert MPI error type to PETSc error with string message for all MPI callsNow PETSc examples will ONLY return PETSc error codes and never MPI error codes directly so we can understand and post-pro
Convert MPI error type to PETSc error with string message for all MPI callsNow PETSc examples will ONLY return PETSc error codes and never MPI error codes directly so we can understand and post-process their errors better.The test harness will now automatically retry tests that fail with MPI, this may help with Intel MPI that produces seemingly random failures.Commit-type: error-checking/spend 30m
12345678910>>...23