Re: [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?

I have to put in a good work for Fortran. There are many parallels in capability with modern C++, and it only requires disregarding every implementation method you previously know and mapping them onto keywords that have different meanings in every other language. The tooling is comparable to

Re: [petsc-dev] test harness requires case independent

> $ make -f gmakefile.test test query='requires' queryval='*SuperLU_DIST*' > Using MAKEFLAGS: -- queryval=*SuperLU_DIST* query=requires > # No test results in ./arch-superlu_dist-single/tests/counts > > > I looked query_test.py and could not see where the queryv

Re: [petsc-dev] Gitlab workflow discussion with GitLab developers

ewers. And support for people outside of the Petsc group to set more > > things when they make MRs. And being to easily add non-PETSc folks as > > reviewers. > > > > Barry > > > > -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] [DocTip!] #3 CI docs build and preview

really rst+(extensions for book-like documentation) so the extensions won't be handled, But that will be true for MyST well. Scott -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] [DocTip!] #2: Aiming for self-updating docs

erimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/> -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] PETSCTEST_VALGRIND

T_VALGRIND, but it seems rather static and set > depending on PETSC_ARCH. > So even if there is src/snes/tutorials/ex19.c: requires: > defined(PETSC_USE_LOG) !defined(PETSCTEST_VALGRIND), > Running make -f gmakefile test s='snes*logviewmemory' VALGRIND=1 on my > machine

Re: [petsc-dev] Is this a bug in test generation?

1519558357 > > <https://gitlab.com/petsc/petsc/-/jobs/1519558357>, with a CI > > configuration without hypre. > > Other testset instances works fine if any “require:" is both specified in > > the testset body and in the specific test. > > Is this supposed to work? > > > > Thanks > > Stefano > -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] Kokkos make error on Spock

;, > > On Tue, Jul 20, 2021 at 9:00 AM Mark Adams wrote: > > > > > > > On Mon, Jul 19, 2021 at 6:41 PM Scott Kruger wrote: > > > >> > >> Mark, > >> > >> On tulip, things with fortran went wonky when a `-fast` flag snuck into > >> th

Re: [petsc-dev] Kokkos make error on Spock

>>>> undefined reference to > >>>>>>>> .omp_offloading.img_start.cray_amdgcn-amd-amdhsa > >>>>>>>> [--no-allow-shlib-undefined] > >>>>>>>> ld.lld: error: > >>>>>>>> /gpfs/alpine/phy122/proj-shared/spock/petsc/current/arch-opt-cray-k

Re: [petsc-dev] Auto-testing Failure?

nit tests look for some kind of positive result, but is there any > established way in the harness to test for failure of a particular kind? > > Best regards, > > Jacob Faibussowitsch > (Jacob Fai - booss - oh - vitch) > -- Scott Kruger Tech-X Corporation

Re: [petsc-dev] git worktree

h-partial-clone-and-shallow-clone/ > > <https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/> > > > > > Am 19.05.2021 um 05:54 schrieb Scott Kruger : > > > > > > > > A. I remember your email about it, and I ev

Re: [petsc-dev] git worktree

go to previous branch, > before git checkout (like - except handles multiple branch changes in the > script) > # git diffdo git diff HEAD~1 > # > # cizappipeline delete all the

Re: [petsc-dev] git worktree

ceiving objects: 100% (474/474), 430.41 KiB | 1.96 MiB/s, done. > Resolving deltas: 100% (296/296), completed with 110 local objects. > Updating files: 100% (9721/9721), done. > $ cd petsc-release/ > release= ~/petsc-release$ du -hs .git > 2.3M.git > > Scott Kruger writes: &

[petsc-dev] git worktree

ster way of getting the HEAD to point to the right sha in one go. I'd be very interested if someone knows a better method. Scott -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303

Re: [petsc-dev] Listing failed tests

lt. > > > > Thanks, > > > > Matt > > > > -- > > What most experimenters take for granted before they begin their > > experiments is infinitely more interesting than any results to which their > > experiments lead. > > --

Re: [petsc-dev] Strange issue with testsuite

/sys/objects/options.c:684 > [0]PETSC ERROR: #4 PetscOptionsInsert() at > /home/zampins/src/petsc/src/sys/objects/options.c:907 > [0]PETSC ERROR: #5 PetscInitialize() at > /home/zampins/src/petsc/src/sys/objects/pinit.c:1024 > > -- > Stefano -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] empty space on left side of website pages

all windows, at least. > >> > >> > >>> Am 23.04.2021 um 19:21 schrieb Barry Smith >>> <mailto:bsm...@petsc.dev>>: > >>> > >>> > >>> There is a lot of empty space on the left side of the website pages; > >>> under the Search slot. Does this empty left side need to be so large, > >>> seems to waste a lot of the screen? > >>> > >>> Barry > >>> > >> > > > -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] commenting on/asking questions on documentation pages

r/pydata_sphinx_theme/_templates/edit-this-page.html > > > > <https://github.com/pydata/pydata-sphinx-theme/blob/master/pydata_sphinx_theme/_templates/edit-this-page.html> > > > > Doesn't seem too bad but it relies on a pretty big chunk of Python as well: >

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

> > -- > What most experimenters take for granted before they begin their > experiments is infinitely more interesting than any results to which their > experiments lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/> -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] -with-kokkos-cuda-arch=AMPERE80 nonsense

I wrote sent this yesterday but am having some strange mailing issues. On 2021-04-03 22:42, Barry Smith did write: > > It would be very nice to NOT require PETSc users to provide this flag, how > the heck will they know what it should be when we cannot automate it > ourselves? > > Any i

Re: [petsc-dev] reproducing crashes in the test harness

bugger without them digging around > in the code to check arguments etc. > > So for example "Run: mpiexec -n N ./xxx args -start_in_debugger" to > reproduce this problem? Then one could just cut and paste and be debugging > away. > > Thanks > > Barry >

Re: [petsc-dev] Test harness + PETSC_HAVE_DEFINED

l workers, even those > which are not AVX512-capable?). > > Thanks, > Pierre > > > Why is this test skipped (on a worker other than linux-knl)? > > Thanks, > > Pierre > -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] 32 bit compilers and PETSc

;void-p'] == 8: > + self.addDefine('USING_64BIT_PTR',1) > self.executeTest(self.checkVisibility) > self.executeTest(self.checkMaxPathLen) > return > > > ./configure CFLAGS=-m32 CXXFLAGS=-m32 FFLAGS=-m32 --with-mpi=0 && make && > make check -- Scott Kruger Tech-X Corporation kru...@txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303Fax: (303) 448-7756

Re: [petsc-dev] Comparing binary output files in test harness

nical Engineering > Adjunct of the Center for Computation & Technology > Louisiana State University, Lockett Hall Room 344, Baton Rouge, LA 70803, USA > Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 Web > http://www.math.lsu.edu/~bourdin > -- Scott Kruger Tech-X Corporation

Re: [petsc-dev] "Search" does not work in the testing system?

, 2021 at 4:50 PM Scott Kruger <mailto:kru...@txcorp.com>> wrote: You can change the 'test' target to 'print-test' to see the actual targets you'll be testing. You can also just change your search string to src/snes/tutorials/ex1.c to gr

Re: [petsc-dev] "Search" does not work in the testing system?

You can change the 'test' target to 'print-test' to see the actual targets you'll be testing. You can also just change your search string to src/snes/tutorials/ex1.c to grab all tests associated with ex1.c. Scott On 1/27/21 4:45 PM, Zhang, Hong via petsc-dev wrote: make PETSC_DIR=/Users/

Re: [petsc-dev] bin/sh error while running tests

-@if test ${showreport} == "true"; then elapsed_time=$$(($(ENDTIME)- $(STARTTIME))) && \ - $(PYTHON) $(CONFIGDIR)/report_tests.py -m $(MAKE) -d $(TESTDIR)/counts -t 5 -e $${elapsed_time};\ -fi + elapsed_time=$$(($(ENDTIME)- $(STARTTIME))) && \ + $

Re: [petsc-dev] bin/sh error while running tests

I can't reproduce this with the latest master: hip 1261: git pull Already up to date. hip 1262: make -f gmakefile.test test search='notatest' Using MAKEFLAGS: -- search=notatest hip 1263: On 1/19/21 8:19 AM, Stefano Zampini wrote: Just rebased over latest master and got this zampins@vultur

Re: [petsc-dev] Testing seems broken in master

Yes.  There are test cases where a cast is done so for those. Scott On 1/4/21 10:29 AM, Satish Balay wrote: hm - indices are integers and its not ignored (i.e %d) - only the %f and %e diff is ignored (by default) Satish On Mon, 4 Jan 2021, Scott Kruger wrote: Is this just the 3rd

Re: [petsc-dev] Testing seems broken in master

Is this just the 3rd problem? Regarding how you can end up with changes not being caught: The default (going all the way back to the old harness) is to not check numbers to avoid round-off errors giving false negatives (failures). Of course, sometimes you *want* to check the numbers; e.g., fo

Re: [petsc-dev] slight inconsistency with test harness?

https://gitlab.com/petsc/petsc/-/merge_requests/3525 Your complaint about the test harness verbosity when running restricted set of tests is also fixed in this one as well (and this one is so nice I should have done this quite awhile ago). Scott On 12/29/20 8:32 PM, Barry Smith wrote: S

Re: [petsc-dev] Updated testing

Thanks.  Many thanks for the new sphinx documentation which I find easier to write in as I develop, and for the tutorial series which provided really useful feedback on what devs wanted. Scott On 11/17/20 3:05 PM, Matthew Knepley wrote: On Tue, Nov 17, 2020 at 12:00 PM Scott Kruger

[petsc-dev] Updated testing

As a heads up, the test harness changed a fair amount in master and release as a result of MR   !3382 which includes all of the changes suggested at the tutorial, as well as some other issues that were resolved. The latest documentation on the testing can be found here: https://docs.petsc.o

Re: [petsc-dev] Something is wrong with testing

It's doing the right thing: From src/dm/impls/plex/tests/ex35.c:  build:     requires: !define(PETSC_USE_64BIT_INDICES) double !complex !define(PETSC_HAVE_VALGRIND) So because you have it defined PETSC_HAVE_VALGRIND,  it's instructed to skip the build and thus you have: # SKIP Null r

Re: [petsc-dev] Test Harness Tutorial on October 29 at 2pm Central

For those that wish to follow along today: https://docs.google.com/presentation/d/1q3mExIBdpfDyxDx-1yDfZGH0v6HRSfWzWtFryV3CNb4/edit#slide=id.p On 10/28/20 8:27 AM, Munson, Todd via petsc-dev wrote: Dear all, A reminder that our next PETSc tutorial will be by Scott Kruger who will be

Re: [petsc-dev] [XSDK-DEV] PR20 - Vote next xSDK telecon (Oct 1st) (fwd)

Sorry if I'm missing something, but my take is that this is mostly going to affect  PETSc's spack package file which doesn't affect PETSc directly?    I'm struggling to see how this affects PETSc. Scott On 9/23/20 8:47 AM, Satish Balay via petsc-dev wrote: FYI - this policy change would

Re: [petsc-dev] testharness rerun test based on error condition; GPU; gitlab issues still broken

c # Approximate CPU time (not incl. build time): 0.01 sec # # To rerun failed tests: # /usr/bin/gmake -f gmakefile test test-fail=1 # # Timing summary (actual test time / total CPU time): # ksp_ksp_tests-ex49_cg: 0.01 sec / 0.01 sec [balay@pj01 petsc.x]$ echo $? 0 [balay@pj01 petsc.x]$ On Fr

Re: [petsc-dev] testharness rerun test based on error condition; GPU; gitlab issues still broken

That's a good idea, but I'll have to think about this a bit.   It seems relatively straightforward, but I'd be doing this in bash so I'd like to come up with an implementation that is not overly complicated.    Do you have a job that has the issue offhand? Scott On 9/4/20 10:27 AM, Barry

Re: [petsc-dev] Pause-for-approval Pipelines?

What's wrong with using the API to release the paused job instead of using it to start a fresh pipeline? Generally I like to pass the Pipeline before making a PR. So the test on creating a new MR is annoying. Yes after the initial MR I might be able to release the paused job in lieu of st

Re: [petsc-dev] Pause-for-approval Pipelines?

Does branch+master mean an automatic rebase? Scott On 8/27/20 10:59 AM, Satish Balay via petsc-dev wrote: BTW: here are some reasons for using the MR pipeline instead of the web interface pipeline. - it tests branch+master (more useful?) - instead of branch [web pipeline]. - you can skip t

Re: [petsc-dev] test harness failure make -f gmakefile.test test query='requires' queryval='kokkos'

A.  gmakefile is not passing PETSC_DIR and PETSC_ARCH to query_tests.py like it should. The immediate fix is to set your env variables, but I'll do a quick MR to fix this. Scott On 8/11/20 8:11 PM, Barry Smith wrote:   Scott,    Sometimes when I run the below test the harness mis-be

Re: [petsc-dev] REPLACE=1 not working for me

Looks like a problem in petscdiff between the filter output flag and the move flag. I'll take a look. Scott On 7/10/20 9:15 AM, Mark Adams wrote: REPLACE=1 is doing something funny: 11:12 knepley/feature-swarm-fortran *= ~/Codes/petsc$ make -f gmakefile test search='dm_impls_swarm_tu

Re: [petsc-dev] How do I see the gcov results?

For more detail, Stage 4 of the pipeline ("analyze-pipeline") has all of the gcov data and you can download it from the right side after clicking "Download" from "Job Artifacts" tab. This is handled by the .gitlab-ci.yml file (search for gcov). If someone knows how gcov outputs it's data

Re: [petsc-dev] testing with Pipelines before making merge request

I see the value in this, but am somewhat ambivalent.. As a workflow, I did do the "Assign to me" and then when it was actually ready to merge, I changed the status to "Ready to merge" and assigned to Satish. I liked this because the gitlab MR button in the upper right shows the ones assign

Re: [petsc-dev] https://developer.nvidia.com/nccl

Here's a paper from a few years ago that uses NCCL to give a better mpi_bcast: https://arxiv.org/pdf/1707.09414.pdf But what's interesting is that they have this statement: In general, NCCL integration with MPI runtimes might lead to very complicated designs. Thus, the proposed work is a

Re: [petsc-dev] "alt" versions of tests

This is more about how the reporting is done than one should interpret what's actually happening under the hood. The way the test is formed is essentially: diff-test1 2> test.out || diff-test2 2> test.out So diff-test1 output gets overwritten by diff-test2. Let me see if I can fix. Sc

Re: [petsc-dev] testset + test with only args

This is probably more detail than you want, but: When you explicitly put in the suffix, you are telling the test harness to put each of those "subtests" into a separate script rather than a single script (multiple tests within a single script), so that's why it works. For the single scrip

Re: [petsc-dev] Issue with make test and globsearch

Can you send me these files? $PETSC_ARCH/tests/datatest.pkl $PETSC_ARCH/tests/testfiles Thanks, Scott On 4/9/20 10:47 AM, Stefano Zampini wrote: [szampini@localhost petsc]$ make -f gmakefile.test test globsearch='mat_*' Using MAKEFLAGS: -- globsearch=mat_* make: *** No rule to make target

Re: [petsc-dev] Globsearch fails for me when running tests

Sorry for the delay. Fixed in MR !2663. It turns out that the *read* for $(file <...) did not occur until gmake 4.2 so this bit me even on a (admittedly old) Linux dev box. To enable the widest range of usage, I keep a modified version of the current $(shell ...) usage, but have commented out

Re: [petsc-dev] Globsearch fails for me when running tests

re, probably put them in an argsfile $(file >$(TESTDIR)/globsearch.args,$(alltesttargets)) and make your Python read from that file. I don't know a way to pass it on stdin. Scott Kruger writes: What platform? On 3/25/20 3:20 PM, Stefano Zampini wrote: This was working before.. [s

Re: [petsc-dev] Globsearch fails for me when running tests

What platform? On 3/25/20 3:20 PM, Stefano Zampini wrote: This was working before.. [szampini@localhost petsc]$ make -f gmakefile.test test globsearch='dm*' make: execvp: /usr/bin/sh: Argument list too long Using MAKEFLAGS: -- globsearch=dm* # No tests run # No tests run # No tests run [sza

Re: [petsc-dev] ccache tips?

I didn't realize brew put the links in libexec. I did it manually like in this tutorial: https://software.intel.com/en-us/articles/accelerating-compilation-part-1-ccache This tutorial discusses the size of the cache. I made mine too small when I first set it up. I like Jed's mpi method

Re: [petsc-dev] Fortran equivalent + separate output with output_file

On 1/13/20 8:32 AM, Pierre Jolivet wrote: Hello, This is actually two separate questions, sorry. 1) I’m looking for the Fortran equivalent of the following, but I couldn’t get any help looking at the sources. ierr = PetscOptionsBegin(PETSC_COMM_WORLD,"","","");CHKERRQ(ierr); ierr = Pets

Re: [petsc-dev] How to replace floating point numbers in test outputs?

It's a bug. Fixed in MR !2428 Scott On 1/4/20 1:27 PM, Smith, Barry F. wrote: Yes, since difference in floating point are considered not a change the REPLACE which only updates files with changes won't update them. I don't understand the output below, looks identical to me, why is

Re: [petsc-dev] Valgrind problems

Once MR!2329 is merged in, all of these test harness annoyances should be fixed. It wasn't a single issue, but rather a bunch of stdout/stderr and error code issues that were fixed in multiple MR's. Scott On 12/8/19 12:11 AM, Smith, Barry F. wrote: On Dec 7, 2019, at 6:00 PM, Matthe

[petsc-dev] Gitlab notifications and labels

In a conversation with Barry, he mentioned that we hadn't really discussed label subscription on this mailing list, despite the fact that this is perhaps the more useful control of notifications than what is in given in Settings. Following up on this discussion, if folks go here: https://git

Re: [petsc-dev] I think the test system is broken in master

Thanks for the debugging, Satish -- I was very confused because I recently changed petscdiff and I assumed I rebugged it. On 10/23/19 3:10 PM, Balay, Satish wrote: On Wed, 23 Oct 2019, Balay, Satish via petsc-dev wrote: On Wed, 23 Oct 2019, Matthew Knepley via petsc-dev wrote: On Wed, O

Re: [petsc-dev] Wrong "failed tests" command

When we created the map of directory+test+variants to targets we did not use enough delimiters to allow the inverse map to be determined so creating the proper list of target names is an ill-posed problem. The globsearch was a way of trying to just catch more of them, but obviously it sti

Re: [petsc-dev] test harness: output of actually executed command for V=1 gone?

In MR !2138 I have this target as show-fail which I think is more descriptive. config/report_tests.py -f is what's done directly. I made it such that one can copy and paste, but it might be too verbose. Scott On 9/20/19 8:53 PM, Jed Brown wrote: "Smith, Barry F." writes: Satish and

Re: [petsc-dev] Mixing separate and shared ouputs

Fixed in MR# 2138 https://gitlab.com/petsc/petsc/merge_requests/2138 Thanks for the report. Scott On 9/28/19 3:44 AM, Pierre Jolivet via petsc-dev wrote: Hello, If I put something like this in src/ksp/ksp/examples/tutorials/ex12.c args: -ksp_gmres_cgs_refinement_type refine_always -

Re: [petsc-dev] TAP file and testing error

My summary is that we can just do the easiest fix then and have test_tap.log and test_err.log Scott On 9/26/19 9:28 AM, Balay, Satish wrote: On Thu, 26 Sep 2019, Scott Kruger via petsc-dev wrote: On 9/26/19 12:45 AM, Stefano Zampini wrote: You usually get the backslash when you

Re: [petsc-dev] TAP file and testing error

On 9/26/19 12:45 AM, Stefano Zampini wrote: You usually get the backslash when you trying to be quick and tab-complete the command :-) Yes, I agree that the makefile should fix this. and, so far, PETSc accepted this. We should either filter the variable in the makefile, or change the filen

Re: [petsc-dev] TAP file and testing error

Can you try rerunning after removing the trailing backslash to PETSC_ARCH? Scott On 9/25/19 1:51 PM, Stefano Zampini wrote: If we specify a PETSC_ARCH with a trailing slash, the current testing makefile fails. Can this be fixed? *zampins@vulture*:*~/Devel/petsc*$ make -f gmakefile.test te

Re: [petsc-dev] test harness: output of actually executed command for V=1 gone?

On 9/20/19 2:49 PM, Jed Brown wrote: Hapla Vaclav via petsc-dev writes: On 20 Sep 2019, at 19:59, Scott Kruger mailto:kru...@txcorp.com>> wrote: On 9/20/19 10:44 AM, Hapla Vaclav via petsc-dev wrote: I was used to copy the command actually run by test harness, change to exa

Re: [petsc-dev] test harness: output of actually executed command for V=1 gone?

On 9/20/19 10:44 AM, Hapla Vaclav via petsc-dev wrote: I was used to copy the command actually run by test harness, change to example's directory and paste the command (just changing one .. to ., e.g. ../ex1 to ./ex1). Is this output gone? Bad news. I think there should definitely be an o

Re: [petsc-dev] Gitlab notifications

Here's what I did: Settings -> Notifications -> developers + Participate The default is "Global". "Participate" is what I'm using now. There is a "Custom", but it confuses me since it says you can use it to match "Participate", but you can't do something like: Email all new issues, but only

Re: [petsc-dev] args loop in testset

Thanks for the report Jakub. I have a backlog of fixes to put into a PR, but am about to leave for vacation so it'll probably be a couple of weeks. Scott On 6/26/19 5:16 AM, Jakub Kruzik via petsc-dev wrote: Hello, args loop in test in testset does not insert a space after the argument.

Re: [petsc-dev] better regular testing on accelerators

I think trying to push the logic of the type 'requires: cuda' or 'requires: !cuda' to be implicit rather than explicit is a bad if it comes to that. Scott On 6/12/19 9:03 AM, Smith, Barry F. via petsc-dev wrote: On Jun 12, 2019, at 9:58 AM, Jed Brown wrote: Would it be sufficient to

Re: [petsc-dev] User(s) manual sections field in manual pages?

So many projects use it (including the linux kernel, moving away from bookdown, says wikipedia) They switched from Docbook to rst. https://www.kernel.org/doc/html/latest/ Is that the default C autodoc extension, or hawkmoth? https://hawkmoth.readthedocs.io/en/latest/extension.html

Re: [petsc-dev] Fwd: [DL-interest] The missing piece in deep learning?

On 5/16/19 4:57 PM, Mills, Richard Tran via petsc-dev wrote: Interesting. I expect that Google will be convinced to rewrite Tensorflow entirely in Fortran now. Seriously, I'm not sure what the motivation for this particular project is. Is it that people are tired of reading in their data

Re: [petsc-dev] testing in parallel

example, the goal would be to prevent multiple ex23 executables from being called at the same time. Of course, a better method would be to use some type of our own round-robin distribution based on an expected "JFLAG" value. That could perhaps be a flag passed to config/gmakegentest

Re: [petsc-dev] alternatives to alt files

On 5/3/19 3:13 PM, Smith, Barry F. wrote: On May 3, 2019, at 3:57 PM, Scott Kruger wrote: Sticking to the immediate issues and ignoring the other meta issues... I think what you want could possibly be used to simplify the test harness if we push things down to the petscdiff level

Re: [petsc-dev] alternatives to alt files

Sticking to the immediate issues and ignoring the other meta issues... I think what you want could possibly be used to simplify the test harness if we push things down to the petscdiff level. If we have petscdiff detect the diff then it will automatically apply the patches. This would elim

Re: [petsc-dev] testing in parallel

FYI -- I have reproduced all the problems but am still looking at it. I thought perhaps it would be something about the globsearch's invocation of python, but it's not -- I get the same thing even with gmake's native filter (and in fact, it appears to be worse). I'm getting something funny

Re: [petsc-dev] need for HDF5 < 1.8.0 support?

FWIW, spack only supports 1.8.10 and above which means that a significant fraction of the scientific software stack has moved on. Scott On 12/7/18 7:56 AM, Jed Brown via petsc-dev wrote: "Smith, Barry F." writes: A potential drawback is some users also use HDF5 directly in their code

Re: [petsc-dev] tests with multiple loops

Fixed in scott/fix-forloops. Could you take a look and see if that works for you? Thanks, Scott On 11/8/18 8:40 AM, Hapla Vaclav via petsc-dev wrote: Assume the following test test: suffix: 4_tet_test_orient nsize: 2 args: -dim 3 -distribute 0 args: -rotate_interf

Re: [petsc-dev] tests with multiple loops

Yes, that seems wrong. I'll take a look. Scott On 11/8/18 8:40 AM, Hapla Vaclav via petsc-dev wrote: Assume the following test test: suffix: 4_tet_test_orient nsize: 2 args: -dim 3 -distribute 0 args: -rotate_interface_0 {{0 1 2 11 12 13}} args: -rotate_interfa

Re: [petsc-dev] tiny issues in test harness

Fix for #1 is merged into next. See ecc1beb596a8093f7509ca38016ed30c93784193 For #2, I think it'll work if you use double quotes and egrep. If you do this: cd $PETSC_DIR/src/sys/examples/test grep filter *.c I think you'll see some examples of complicated filters that Barry got working. S

Re: [petsc-dev] Test output broken for test sets

Matt, I'm a bit confused as to what you want to do here. I put this block in ksp/ksp/examples/test/ex1.c just for testing. I get: > config/gmakegentest.py Warning: /Users/kruger/ptroot/upstream/petsc/src/sys/examples/tests/output/ex1_6_tet.out not found. Warning: /Users/kruger/ptroot/upstr

Re: [petsc-dev] Test output broken for test sets

I'll take a look. Scott On 9/26/18 8:58 AM, Jed Brown wrote: Scott, do you know how to fix this? Jakub Kruzik writes: Related issues: https://lists.mcs.anl.gov/pipermail/petsc-dev/2018-August/023448.html Jakub On 9/24/18 3:26 PM, Matthew Knepley wrote: At least on my machine, this d

Re: [petsc-dev] test harness hiccup

The line is this: @$(RM) -rf $(TESTDIR)/counts $(TESTLOGFILE) so I'm a bit confused how this could happen. Are you on master? Scott On 9/8/18 4:06 PM, Smith, Barry F. wrote: $ make alltests rm: ./arch-simple/tests/counts: Directory not empty make[2]: *** [pre-clean] Error 1

[petsc-dev] Fwd: Re: [petsc-users] PETSc doesn't allow use of multithreaded MKL with MUMPS + fblaslapack?

Forwarded Message Subject: Re: [petsc-users] PETSc doesn't allow use of multithreaded MKL with MUMPS + fblaslapack? Date: Sun, 12 Aug 2018 14:20:42 -0500 From: Satish Balay Reply-To: petsc-users To: Appel, Thibaut CC: petsc-us...@mcs.anl.gov Hm - its just a default - s

Re: [petsc-dev] Test parsers is parsing *.c~ files

Yes, as you surmise Barry, I am a vim user. Based on earlier comments, I have this in config/gmakegentest.py: # Ignore emacs and other temporary files if exfile.startswith("."): continue if exfile.startswith("#"): continue I assume that this: if exfile.endwith(

Re: [petsc-dev] [petsc-users] Using PETSC with an openMP program

On 3/2/18 12:44 PM, Matthew Knepley wrote: On Fri, Mar 2, 2018 at 2:39 PM, Jed Brown > wrote: Matthew Knepley mailto:knep...@gmail.com>> writes: > That is not the same as printing unused arguments. Michael's Pythia > does this correctly, but it is even

Re: [petsc-dev] new test harness in PETSc

ETSc examples over from the old test system (where tests were written in the makefile) to a new system, provided by Scott Kruger, where the test rules are written in bottom of the source file of the example. Directions for usage and adding new tests can be found in the PETSc developer

Re: [petsc-dev] test harness loops with different outputs

On 1/24/18 6:50 AM, Vaclav Hapla wrote: 24. 1. 2018 v 14:45, Vaclav Hapla : How should I specify output files for {{...}} with different outputs, please? Oh I see, {{...}separateoutput} is meant literally. But in that case typesetting it in italics is confusing. It's clearer in the exa

Re: [petsc-dev] Our pull request work flow is terrible and horrible

On 1/12/18 9:53 PM, Jed Brown wrote: "Smith, Barry F." writes: Sadly you cannot reply to previous comments for Github PRs, there is just a mass of unorganized previous comments. If this is fixed then Github becomes more desirable looking. I think it was an intentional choice to

Re: [petsc-dev] Our pull request work flow is terrible and horrible

On 1/11/18 10:40 AM, Patrick Sanan wrote: One idea is to impose a stricter guideline that things on the bitbucket PR page are things that everyone is actively trying to merge. That way, maintainers can just look at the bottom of the list to see what's lagging, instead of having to to work up

Re: [petsc-dev] limiting tests to avoid unneeded ones

On 1/11/18 5:05 AM, Jed Brown wrote: You'd need to know that 'master' was actually clean for that commit with your configuration on your machine. If an automated system, where would that information be stored? If not automated, just run the git diff and then make test the desired packages.

Re: [petsc-dev] Experiments in test timing with new harness

, Scott Kruger wrote: On my laptop: rm -rf $PETSC_ARCH/tests time make -f gmakefile.test test NO_RM=1 Results were this: 603.458u 191.569s 20:29.22 64.6%6030+0k 3297+2284io 224278pf+0w Immediately redo (NO_RM=1 => no rebuilding of executables): time make -f gmakefile.test test NO_R

[petsc-dev] Experiments in test timing with new harness

On my laptop: rm -rf $PETSC_ARCH/tests time make -f gmakefile.test test NO_RM=1 Results were this: 603.458u 191.569s 20:29.22 64.6%6030+0k 3297+2284io 224278pf+0w Immediately redo (NO_RM=1 => no rebuilding of executables): time make -f gmakefile.test test NO_RM=1 Results were this: 280

Re: [petsc-dev] remove temporary output with new test-harness

On 11/29/17 10:25 AM, Matthew Knepley wrote: On Wed, Nov 29, 2017 at 11:23 AM, Scott Kruger <mailto:kru...@txcorp.com>> wrote: The generated scripts automatically run in a subdirectory to avoid name conflicts.  For example, runex1.sh creates a runex1 directory relati

Re: [petsc-dev] remove temporary output with new test-harness

x27;t been a problem yet. Scott On 11/29/17 9:43 AM, Matthew Knepley wrote: On Wed, Nov 29, 2017 at 10:38 AM, Scott Kruger <mailto:kru...@txcorp.com>> wrote: rm $PETSC_ARCH/tests// I assume you really mean something else, specifically related to the generated test scr

Re: [petsc-dev] remove temporary output with new test-harness

rm $PETSC_ARCH/tests// I assume you really mean something else, specifically related to the generated test script, but there isn't enough information to answer that. Or more specifically, the test language was not written to generate scripts that have an `rm` command in them, so perhaps e

Re: [petsc-dev] test harness chokes

PR here: https://bitbucket.org/petsc/petsc/pull-requests/805/bug-fix-for-empty-tests-default/diff On 11/20/17 2:11 PM, Smith, Barry F. wrote: on /*TEST test: test: suffix: 2 nsize: 2 TEST*/ with $ ./config/gmakegentest.py KeyError: 0 -- Tech-X Corporat

Re: [petsc-dev] test harness with tests that depend on multiple source files

On 11/20/17 8:59 PM, Smith, Barry F. wrote: On Nov 20, 2017, at 9:37 PM, Jed Brown wrote: Scott Kruger writes: depends keyword: From: dm/examples/tutorials/ex13f90.F90 !/*TEST ! ! build: ! requires: !complex ! depends: ex13f90aux.F90 ! !TEST*/ How would anyone know

Re: [petsc-dev] test harness with tests that depend on multiple source files

depends keyword: From: dm/examples/tutorials/ex13f90.F90 !/*TEST ! ! build: ! requires: !complex ! depends: ex13f90aux.F90 ! !TEST*/ Scott On 11/19/17 10:48 AM, Smith, Barry F. wrote: Scott, I asked you this before and you responded but I forgot and lost your res

Re: [petsc-dev] nightlybuilds (next vs next-tmp)

  ./config/gmakegentest.py --petsc-arch=arch-master-debug I have encountered a strange behavior, perhaps only on my machine, where if I do not run   PETSC_ARCH=arch-master-debug ./config/gmakegentest.py --petsc-arch=arch-master-debug then it does not update correctly. I don't know w

Re: [petsc-dev] nightlybuilds (next vs next-tmp)

On 11/15/17 8:48 PM, Smith, Barry F. wrote: For those of us who have no idea how to do this, could someone please give me a pointer or two on where to look for an example or two or some documentation? I should probably be spending a few minutes a day converting some examples, but I don

Re: [petsc-dev] broken nightlybuilds (next vs next-tmp)

On 11/11/17 11:47 AM, Jed Brown wrote: The way I see it - a broken next [where folks can't easily figure out who or which commit is responsible for the brakages] - doesn't help much.. The fundamental problem here is that we aren't accurate enough at placing blame and getting the appropriate p

  1   2   >