Home
last modified time | relevance | path

Searched refs:failed (Results 1 – 25 of 31) sorted by relevance

12

/petsc/src/snes/tutorials/output/
H A Dex15_nleqerr.out5 Line search: monotonicity check failed, ratio: 1.732490068050e+00
13 Line search: monotonicity check failed, ratio: 2.151157698837e+00
21 Line search: monotonicity check failed, ratio: 2.476742572785e+00
29 Line search: monotonicity check failed, ratio: 2.790877657608e+00
37 Line search: monotonicity check failed, ratio: 3.078507618381e+00
45 Line search: monotonicity check failed, ratio: 3.303996391609e+00
53 Line search: monotonicity check failed, ratio: 3.341289688370e+00
61 Line search: monotonicity check failed, ratio: 2.631466376143e+00
69 Line search: monotonicity check failed, ratio: 1.115209024616e+00
/petsc/src/ksp/ksp/tests/output/
H A Dex51_2_alt.out3 PC failed due to FACTOR_NUMERIC_ZEROPIVOT
6 PC failed reason is FACTOR_NOERROR
H A Dex51_1.out3 PC failed due to FACTOR_NUMERIC_ZEROPIVOT
6 PC failed reason is FACTOR_NOERROR
H A Dex51_2.out3 PC failed due to FACTOR_NUMERIC_ZEROPIVOT
6 PC failed reason is FACTOR_NOERROR
H A Dex51_2_alt_2.out5 PC failed reason is FACTOR_NOERROR
/petsc/doc/developers/contributing/
H A Dpipelines.md36 Examining a failed pipeline stage.
39 You can see the failed jobs by clicking on the X.
45 Locating the exact failed job in a pipeline stage.
51 A failure in running the job's tests will have `FAILED` and a list of the failed tests
53 :::{figure} /images/developers/failed-examples.png
66 A test that failed because of unfreed memory.
119 Downloading `configure.log` from a failed pipeline job.
/petsc/config/
H A Dpetsc_harness.sh264 (( failed=failed+1 ))
267 (( total=success+failed ))
282 printf "failed %s\n" "$failed" >> "$logfile"
/petsc/src/ksp/ksp/tutorials/output/
H A Dex72_zeropivot_3.out2 PC failed due to SUBPC_ERROR
H A Dex72_zeropivot.out2 PC failed due to SUBPC_ERROR
/petsc/lib/petsc/bin/
H A Dpetscdiff94 echo Error! file1 check failed: "${1}"
115 echo Error! file2 check failed: "${2}"
/petsc/src/snes/tests/output/
H A Dex69_5.out4 PC failed due to SUBPC_ERROR
H A Dex69_4.out4 PC failed due to FACTOR_NUMERIC_ZEROPIVOT
/petsc/src/sys/tests/output/
H A Dex73_0.out2 [0]PETSC ERROR: Write to file failed
H A Dex73_0_alt.out2 [0]PETSC ERROR: Write to file failed
/petsc/lib/petsc/bin/maint/abi-compliance-checker/modules/Internals/Styles/
H A DCmpSystems.css58 td.failed {
H A DReport.css225 .failed {
/petsc/src/tao/bound/tutorials/output/
H A Dplate2_15.out59 Solver failed: Maximum Iterations
H A Dplate2_14.out59 Solver failed: Maximum Iterations
H A Dplate2_13.out69 Solver failed: Maximum Iterations
/petsc/doc/developers/
H A Dtesting.md523 ### Determining the failed jobs of a given run
533 This method can also be used for the PETSc continuous integration (CI) pipeline jobs. For failed jo…
542 To see the list of all tests that failed from the last run, you can also run this command:
554 Once you know which tests failed, the question is how to debug them.
690 To re-run the last tests which failed:
1089 # failed 2/16 tests; 87.500% ok
/petsc/doc/manual/
H A Dtests.md58 - `not ok` The test failed.
/petsc/src/binding/petsc4py/src/petsc4py/PETSc/
H A DPETSc.pyx426 "PetscPopErrorHandler() failed "
432 "PetscFinalize() failed "
H A DKSP.pyx1738 constructing the preconditioner failed. Call
1740 failed and why. The option ``-ksp_error_if_not_converged`` or
2417 """Boolean indicating if the solver has failed."""
H A Dpetsctao.pxi226 # failed
/petsc/src/dm/impls/plex/
H A Dplexpartition.c1686 PetscInt failed, failedGlobal; in DMPlexRebalanceSharedPoints() local
1968 failed = (PetscInt)(part[0] != rank); in DMPlexRebalanceSharedPoints()
1969 PetscCallMPI(MPIU_Allreduce(&failed, &failedGlobal, 1, MPIU_INT, MPI_SUM, comm)); in DMPlexRebalanceSharedPoints()

12