| /openbmc/openbmc-tools/check_journal/ |
| H A D | check_journal | 50 failing = 0
74 failing += 1
93 failing += 1
97 if failing == 0:
100 print(f"{failing} TESTS FAILED")
|
| /openbmc/linux/tools/perf/tests/shell/ |
| H A D | record_bpf_filter.sh | 66 echo "Failing bpf-filter test"
72 echo "Failing bpf-filter test [Failed forbidden CPU]"
80 echo "Failing bpf-filter test [Failed should succeed]"
85 echo "Failing bpf-filter test [Success]"
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/postinst/ |
| H A D | postinst_1.0.bb | 6 PACKAGES = "${PN}-rootfs ${PN}-delayed-a ${PN}-delayed-b ${PN}-rootfs-failing"
11 ALLOW_EMPTY:${PN}-rootfs-failing = "1"
65 pkg_postinst:${PN}-rootfs-failing () {
|
| /openbmc/linux/arch/m68k/ifpsp060/ |
| H A D | CHANGES | 51 a failing value to the 68060SP, the package ignores
53 as if it never received a failing value.
59 requested by the package should return a failing value
71 Upon receiving a non-zero (failing) return value from
|
| /openbmc/openpower-debug-collector/dump/ |
| H A D | sbe_dump_collector.hpp | 56 * @param failingUnit The identifier of the failing unit prompting the dump
75 * @param failingUnit The identifier of the failing unit.
106 * failing or suspected to be the cause of the issue prompting the dump
133 * @param chipPos - Chip position of the failing unit
148 * @param failingUnit The ID of the failing unit.
|
| H A D | dump_collect_main.cpp | 43 app.add_option("--failingunit, -f", failingUnit, "ID of the failing unit"); in main()
59 << "Failing unit ID is required for Hardware and SBE type dumps\n"; in main()
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | failing_mtms.cpp | 56 lg2::error("Cannot unflatten failing MTM section: {EXCEPTION}", in FailingMTMS()
68 lg2::error("Invalid failing MTMS section ID: {HEADER_ID}", "HEADER_ID", in validate()
75 lg2::error("Invalid failing MTMS version: {HEADER_VERSION}", in validate()
|
| H A D | failing_mtms.hpp | 16 * This represents the Failing Enclosure MTMS section in a PEL.
89 * @return std::optional<std::string> - Failing MTMS section in JSON
|
| /openbmc/phosphor-fan-presence/monitor/ |
| H A D | fan_error.hpp | 91 * @param[in] fan - The failing fan's inventory path
92 * @param[in] sensor - The failing sensor's inventory path. Can be empty
200 * @brief The inventory name of the failing fan
205 * @brief The inventory name of the failing sensor, if there is one.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/cmake/cmake/ |
| H A D | 0001-CMakeDetermineCompilerABI-Strip-pipe-from-compile-fl.patch | 45 - # Avoid failing ABI detection on warnings.
46 + # Avoid failing ABI detection caused by non-functionally relevant
54 + # Avoid failing ABI detection on warnings.
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/python3/ |
| H A D | 0001-test_active_children-skip-problematic-test.patch | 6 This test is failing in some tests on the Autobuilder. Since it's of a
7 similar nature to other failing/hanging tests, disable it for now.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libcurses/libcurses-perl/ |
| H A D | 0001-testtyp.c-Use-proper-prototype-for-main-function.patch | 7 vigorously, and the test will end up failing for this reason instead of
8 real check it should be failing/passing for.
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/openssh/openssh/ |
| H A D | 0001-regress-banner.sh-log-input-and-output-files-on-erro.patch | 7 tests failing. There may be additional error messages in the
17 Full log of a failing banner test runs is:
|
| /openbmc/phosphor-hwmon/ |
| H A D | fan_speed.cpp | 38 log<level::INFO>(std::format("Failing sysfs file: {} errno: {}", file, in target()
73 log<level::INFO>(std::format("Failing sysfs file: {} errno: {}", in enable()
|
| /openbmc/webui-vue/docs/guide/unit-testing/ |
| H A D | readme.md | 43 test that is failing, follow the guidelines for debugging a failed tests or
48 The `test:unit:debugger` script will help to debug failing tests using the
58 the snapshot tests are failing, after manually verifying the UI changes, run the
|
| /openbmc/linux/Documentation/ABI/stable/ |
| H A D | sysfs-transport-srp | 22 layer error has been observed before failing I/O. Zero means
23 failing I/O immediately. Setting this attribute to "off" will
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | ibmpowernv.rst | 37 - 1: Failing fan
53 - 1: Failing power supply.
|
| /openbmc/linux/Documentation/power/ |
| H A D | basic-pm-debugging.rst | 111 dmesg obtained after the failing test). Failure at this level usually means
126 Once you have found the failing driver (there can be more than just one of
240 you may be able to search for failing drivers by following the procedure
241 analogous to the one described in section 1. If you find some failing drivers,
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/cpp/files/ |
| H A D | meson.options | 3 description : 'Compile a failing unit test to test the test infrastructure')
|
| /openbmc/openbmc/poky/meta-selftest/recipes-test/error/ |
| H A D | error.bb | 9 bbfatal "Failing as expected.";
|
| /openbmc/openbmc/poky/meta/recipes-kernel/lttng/babeltrace/ |
| H A D | run-ptest | 2 # use target=recheck if you want to recheck failing tests
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pytest-xdist_3.5.0.bb | 1 SUMMARY = "pytest xdist plugin for distributed testing and loop-on-failing modes"
|
| /openbmc/openbmc/meta-openembedded/meta-networking/dynamic-layers/meta-python/recipes-connectivity/firewalld/files/ |
| H A D | run-ptest | 17 # Failing testsuites: 203 226 241 250 270 280 281 282 285 286
|
| /openbmc/linux/arch/s390/include/asm/ |
| H A D | cio.h | 85 * @fsavf: failing storage address validity flag
88 * @fsaf: failing storage address format
149 * @faddr: failing storage address
|
| /openbmc/openbmc-test-automation/bin/plug_ins/Stop/ |
| H A D | parm_def | 3 # "rest_fail" indicates that the Stop plug-in should fail if REST commands to the BMC are failing.
|