[petsc-dev] gitlab time tracking feature

2020-07-03 Thread Barry Smith
https://gitlab.com/help/user/project/time_tracking.md I'm going to use it to replace my previous home-brew version

Re: [petsc-dev] -on_error_attach_debugger

2020-07-03 Thread Jed Brown
Pierre Jolivet writes: > Hello, > (Probably nobody cares, but) it looks like -on_error_attach_debugger is > neither “-malloc_dump"-clean nor valgrind-clean. Any reason not to pop it in PetscFinalize? We'd normally do that via PetscRegisterFinalize/PetscSysFinalizePackage, but perhaps it shoul

Re: [petsc-dev] GitLab: Resolve this thread in a new issue

2020-07-03 Thread Stefano Zampini
very useful, thanks https://gitlab.com/petsc/petsc/-/issues/676 Il giorno ven 3 lug 2020 alle ore 13:32 Hapla Vaclav < vaclav.ha...@erdw.ethz.ch> ha scritto: > I just used for the first time the feature of GitLab called "Resolve this > thread in a new issue". It's the button next to Resolve threa

[petsc-dev] -on_error_attach_debugger

2020-07-03 Thread Pierre Jolivet
Hello, (Probably nobody cares, but) it looks like -on_error_attach_debugger is neither “-malloc_dump"-clean nor valgrind-clean. $ cd src/ksp/ksp/tutorials $ ~/petsc/arch-darwin-c-debug-real/bin/mpiexec -n 2 valgrind --leak-check=full --show-leak-kinds=all ./ex2 -on_error_attach_debugger Norm of

[petsc-dev] GitLab: Resolve this thread in a new issue

2020-07-03 Thread Hapla Vaclav
I just used for the first time the feature of GitLab called "Resolve this thread in a new issue". It's the button next to Resolve thread. [cid:32269E33-5AA2-4613-B308-8DF8F78D61BE@aircard] It automatically created issue https://gitlab.com/petsc/petsc/-/issues/675 from a thread https://gitlab.co