Yeah - parallel builds have this issue. GNUMake4+ has an option '--output-sync=recurse' that we use to aovid this munging of output.
But some of the builds don't use gnumake [or have older versions of gnumake] - and this option misbehaves on some machines [freebsd/osx] - so some these builds will continue to have this issue. Satish On Wed, 2 Mar 2016, Patrick Sanan wrote: > Ah, I see - it probably got sent to me exactly because the output was > mangled, so the actual error message wasn't there. > On Wed, Mar 02, 2016 at 11:31:14AM -0600, Barry Smith wrote: > > > > Don't worry about it. We try to filter out that particular warning from > > the tests but sometimes it gets picked up and reported. > > > > Barry > > > > > On Mar 2, 2016, at 9:49 AM, Patrick Sanan <[email protected]> wrote: > > > > > > I'm not sure how to silence this (demangled) warning from the nightlies: > > > > > > "/export/home/petsc/petsc.clone-3/src/ksp/ksp/impls/fcg/pipefcg/pipefcg.c", > > > line 112: warning: statement not reached > > > > > > There are a few other warnings of the same form in the log linked below, > > > on the first source line > > > after something like > > > > > > #ifdef PETSC_USE_COMPLEX > > > .. > > > #endif > > > > > > or in the case of the particular warning here, the first source line > > > (after some other preprocessor directives) after > > > > > > #if (defined(PETSC_USE_COMPLEX) && !defined(PETSC_SKIP_COMPLEX)) > > > SETERRQ(PETSC_COMM_WORLD,PETSC_ERR_SUP,"PIPEFGMRES has not been > > > implemented for use with complex scalars"); > > > #endif > > > > > > > > > > > > > > > ----- Forwarded message from PETSc checkBuilds > > > <[email protected]> ----- > > > > > > From: PETSc checkBuilds <[email protected]> > > > To: Patrick Sanan <[email protected]>, PETSc checkBuilds > > > <[email protected]> > > > Date: Wed, 2 Mar 2016 09:00:08 -0600 (CST) > > > Subject: PETSc blame digest (next) 2016-03-02 > > > > > > > > > > > > Dear PETSc developer, > > > > > > This email contains listings of contributions attributed to you by > > > `git blame` that caused compiler errors or warnings in PETSc automated > > > testing. Follow the links to see the full log files. Please attempt to > > > fix > > > the issues promptly or let us know at [email protected] if you are > > > unable > > > to resolve the issues. > > > > > > Thanks, > > > The PETSc development team > > > > > > ---- > > > > > > warnings attributed to commit > > > https://bitbucket.org/petsc/petsc/commits/390d8e4 > > > KSP: Add KSPPIPEFCG > > > > > > src/ksp/ksp/impls/fcg/pipefcg/pipefcg.c:112 > > > > > > [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2016/03/02/build_next_arch-opensolaris-cmplx-pkgs-dbg_n-gage.log] > > > > > > "/export/home/petsc/petsc.clone-3/src/ksp/ksp/impls/fcg/pipefcg/pipefcg.c", > > > line 112: warning: CC > > > arch-opensolaris-cmplx-pkgs-dbg/obj/src/ksp/ksp/impls/symmlq/symmlq.o > > > > > > ---- > > > To opt-out from receiving these messages - send a request to > > > [email protected]. > > > > > > ----- End forwarded message ----- > > >
