History log of /petsc/src/sys/tests/ex48f90.F90 (Results 1 – 25 of 27)
Revision Date Author Comments
# 9b88ac22 29-Oct-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'MarDiehl/improve-Fortran-examples' into 'main'

Improve Fortran examples

See merge request petsc/petsc!8698


# 02c639af 14-Oct-2025 Martin Diehl <mail@martin-diehl.net>

Fortran: enforce lower case keywords and operators

also fixed occasional capitals in used modules with the help of @prj-


# c5e229c2 29-Sep-2025 Martin Diehl <mail@martin-diehl.net>

place all the include statements at the top

Repeated inclusion in multiple location, e.g. at the start of a
module or function is not needed. This becomes clear if all includes are
outside of the ac

place all the include statements at the top

Repeated inclusion in multiple location, e.g. at the start of a
module or function is not needed. This becomes clear if all includes are
outside of the actual Fortran code.
Added regex to check that with the help of @sbalay

show more ...


# edb0e59d 23-Sep-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2025-07-01/format-fortran-source-fprettify' into 'main'

format fortran source with fprettify

See merge request petsc/petsc!8514


# 4820e4ea 23-Sep-2025 Barry Smith <bsmith@mcs.anl.gov>

Run fprettify


# 6eff51de 04-Jul-2025 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2025-07-02/fortran-no-semicolon-end-of-line' into 'main'

fortran no semicolon at end of line

See merge request petsc/petsc!8519


# ccfd86f1 04-Jul-2025 Barry Smith <bsmith@mcs.anl.gov>

fortran no semicolon at end of line

Remove all unneeded ; at end of Fortran source code line

Add checkbadSource to check for semicolon at the end of lines


# 479160d7 12-Jul-2023 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2023-07-02/nice-error-message-when-first-error-is-not-properly-handled' into 'main'

When the user does not properly handle a returned error code and another error...

See merge r

Merge branch 'barry/2023-07-02/nice-error-message-when-first-error-is-not-properly-handled' into 'main'

When the user does not properly handle a returned error code and another error...

See merge request petsc/petsc!6655

show more ...


# e9a33e21 09-Jul-2023 Barry Smith <bsmith@mcs.anl.gov>

Need to have test harness remove -options_left to tests that test handling of errors in tests

Commit-type: testing


# ff1b2eb0 23-Sep-2022 Satish Balay <balay@mcs.anl.gov>

Merge branch 'jolivet/fix-egrep' into 'main'

Switch from egrep to grep -E

See merge request petsc/petsc!5674


# f53b81b6 22-Sep-2022 Pierre Jolivet <pierre@joliv.et>

Switch from egrep to grep -E


# bda77271 20-Jul-2022 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2022-06-24/linenumbers-petscstack' into 'main'

Fixes/improvements for PETSc stack handling

See merge request petsc/petsc!5368


# 660278c0 26-Jun-2022 Barry Smith <bsmith@mcs.anl.gov>

Add PETSc CI mode to allow better handling of errors and system dependent output when running in test harness

-petsc_ci - automatically set for all runs in test harness

-petsc_ci_portable_error_out

Add PETSc CI mode to allow better handling of errors and system dependent output when running in test harness

-petsc_ci - automatically set for all runs in test harness

-petsc_ci_portable_error_output - ensures all error messages (when possible are system and compiler information),
should be only used in tests that are explicitly testing the error handling

This allows proper comparisons of runs on different machines and when errors are intentionally triggered to test error handling

Commit-type: error-checking, testing-fix
/spend 5h

show more ...


# dc34d9f7 17-Jun-2022 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini/fix-function-composition' into 'main'

fix function composition

See merge request petsc/petsc!5274


# 2e956fe4 24-May-2022 Stefano Zampini <stefano.zampini@gmail.com>

PetscObjectFunctionCompose: clean up composed functions at Destroy time


# 540c0c32 02-Jun-2022 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2022-05-24/add-petsccall-fortran-examples' into 'main'

Update all Fortran examples to modern error checking with PetscCallXXX() wrappers around PETSc/MPI function calls.

See mer

Merge branch 'barry/2022-05-24/add-petsccall-fortran-examples' into 'main'

Update all Fortran examples to modern error checking with PetscCallXXX() wrappers around PETSc/MPI function calls.

See merge request petsc/petsc!5271

show more ...


# f8402805 24-May-2022 Barry Smith <bsmith@mcs.anl.gov>

Add modern error checking to sys/tests and tutorial Fortran examples

Commit-type: error-checking
/spend 45m


# f482f063 21-Jun-2021 Satish Balay <balay@mcs.anl.gov>

Merge branch 'stefanozampini/checkstack' into 'main'

Check Push/Pop

See merge request petsc/petsc!4077


# 362febee 10-Jun-2021 Stefano Zampini <stefano.zampini@gmail.com>

PetscStack : check for correct push/pop

Enforce checkstack for CI jobs
Fixes from testsuite


# a8cf78f8 24-May-2021 Satish Balay <balay@mcs.anl.gov>

Merge branch 'barry/2021-05-16/fix-double-lines' into 'main'

Fix typos in source

See merge request petsc/petsc!3984


# 4e278199 16-May-2021 Barry Smith <bsmith@mcs.anl.gov>

Remove all double blank lines from source

Commit-type: petsc-style
/2h


# 817aff64 26-Feb-2021 Satish Balay <balay@mcs.anl.gov>

Merge branch 'dalcinl/vendor-libyaml' into 'master'

Vendor LibYAML

See merge request petsc/petsc!3652


# 951eb098 22-Feb-2021 Lisandro Dalcin <dalcinl@gmail.com>

YAML: Enable use of vendored LibYAML


# 8ec9a424 15-Feb-2021 Satish Balay <balay@mcs.anl.gov>

Merge branch 'dalcinl/options-yaml' into 'master'

Enancements to YAML options

See merge request petsc/petsc!3618


# 5c23ca1c 10-Feb-2021 Lisandro Dalcin <dalcinl@gmail.com>

Enhancements to YAML options

* Pass PetscOptions object to PetscOptionsInsertFileYAML().

* PetscOptionsInsert{File|String}YAML() are now always available and
will fail at runtime if PETSc was not

Enhancements to YAML options

* Pass PetscOptions object to PetscOptionsInsertFileYAML().

* PetscOptionsInsert{File|String}YAML() are now always available and
will fail at runtime if PETSc was not configured with YAML.

* Mapping keys starting with '$$' are considered dummy and not inserted.
These keys can be used with `!include` tags and for the definition of
YAML anchors to be expanded later with the merge key '<<'.

* Sequences of one-mappings insert an option with the list of keys.
For example, the following YAML options

```yaml
map:
- key0: abc
- key1: xyz
- key2: 123
```

insert the following options

```
-map key0,key1,key2
-map_key0 abc
-map_key1 xyz
-map_key2 123
```

show more ...


12