[petsc-dev] nightly build problems because dependencies are not properly listed in tests!
Tobin Isaac
tisaac at uchicago.edu
Mon Feb 27 10:52:44 CST 2017
On Mon, Feb 27, 2017 at 09:42:06AM -0700, Jed Brown wrote:
> Scott Kruger <kruger at txcorp.com> writes:
>
> > On 2/27/17 10:06 AM, Tobin Isaac wrote:
> >> On Sun, Feb 26, 2017 at 09:57:25PM -0600, Barry Smith wrote:
> >>>
> >>> # [0]PETSC ERROR: Mesh generation needs external package support.
> >>> # Please reconfigure with --download-triangle.
> >>>
> >>> is appearing in a bunch of nightly build errors
> >>>
> >>> http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2017/02/26/examples_full_next.log
> >>>
> >>> Please make sure you list all package dependencies in your test cases before pushing a branch to next. Though Jonathan Shewchuk is a god of programming this does not mean that triangle is always installed on all computers at birth. You waste everybody's time by not handling these basics before pushing to next, plus you slow down the process of moving your branch to master.
> >>>
> >>
> >> Good advice, but the specific problem here is win32fe + intel
> >> compilers wants to mixup the executables between directories. Satish
> >> and I have had a thread on this.
> >>
> >
> > It looks to me like a gmake bug, but we need verbose
> > output and some debugging to be sure.
>
> What do I need to reproduce it?
Good question. The original thread is here:
http://lists.mcs.anl.gov/pipermail/petsc-dev/2017-February/020456.html
Summary:
- I have tests in src/vec/vec/utils/tagger/examples/tutorials/ex1.c
- They are being run on the executable generated from
src/dm/impls/plex/examples/tests/ex1.c
- The problem only crops up on mswin-intel test builds:
not mswin-gnu, or mswin-uni which uses "win32fe cl".
- It happens consistently, so it doesn't appear to be a race
condition
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20170227/a2ae380d/attachment.sig>
More information about the petsc-dev
mailing list