Success

Also defined in

• bazel Success The build (or test, or query) completed successfully.
• cargo Success The Cargo command completed successfully. For `cargo build` or `cargo test` this means compilation succeeded and all tests passed.
• cmake Success The cmake, ctest, or cpack command completed without errors.
• composer Success The command completed successfully. All packages were resolved, downloaded, and installed without errors.
• curl OK The operation completed successfully.
• docker Clean exit The container process exited successfully with no error.
• eslint Linting Successful, No Errors Linting completed successfully with no rule violations. If `--max-warnings` is set and warnings are within the limit, the exit code is still 0.
• git Success The command completed successfully.
• gradle Build Successful The Gradle build completed successfully. All requested tasks ran without error.
• homebrew Success The Homebrew command completed without error. The requested formula or cask was installed, upgraded, or otherwise processed successfully.
• icmp Echo Reply Sent in response to an Echo Request (type 8). Used by tools such as ping to confirm that a host is reachable and to measure round-trip time.
• jest Tests Passed All tests in the suite passed, or no tests were found and `--passWithNoTests` was specified. Jest exited cleanly with no failures.
• ldap success The operation completed successfully. No error occurred.
• make Success All requested targets were built successfully. Every recipe in the dependency graph completed with exit code 0.
• maven BUILD SUCCESS All specified lifecycle phases and goals executed without error. The build completed successfully.
• pytest OK All collected tests passed (or were xfailed/xpassed as expected). The test suite completed successfully.
• rsync Success The transfer completed successfully.
• shell Success The command completed successfully.
• systemd Success The service process exited successfully.
• vue Error in setup() An unhandled exception was thrown inside a component's setup() function. Check the error's stack trace for the specific line in your setup logic.

References

• docs.ansible.com/ansible/latest/reference_appendices/general_precedence.html

In this namespace