Home
last modified time | relevance | path

Searched full:failures (Results 1 – 25 of 430) sorted by relevance

12345678910>>...18

/openbmc/u-boot/lib/efi_selftest/
H A Defi_selftest.c73 * @failures counter that will be incremented if a failure occurs
76 static int setup(struct efi_unit_test *test, unsigned int *failures) in setup() argument
86 ++*failures; in setup()
98 * @failures counter that will be incremented if a failure occurs
101 static int execute(struct efi_unit_test *test, unsigned int *failures) in execute() argument
111 ++*failures; in execute()
123 * @failures counter that will be incremented if a failure occurs
126 static int teardown(struct efi_unit_test *test, unsigned int *failures) in teardown() argument
136 ++*failures; in teardown()
185 * failures returns EFI_ST_SUCCESS if all test steps succeeded
[all …]
/openbmc/openbmc/poky/meta/classes/
H A Dreport-error.bbclass74 data['failures'] = []
101 # server will refuse failures longer than param specified in project.settings.py
111 jsondata['failures'].append(taskdata)
120 data['failures'] = []
126 data['failures'].append(taskdata)
136 data['failures'] = []
141 data['failures'].append(taskdata)
150 failures = jsondata['failures']
151 if(len(failures) > 0):
/openbmc/openpower-sbe-interface/
H A Dsbe_chipOp_handler.hpp22 * device and obtain the expected response .Internal device driver failures
26 * - Device driver internal failures
47 * - SBE Internal failures
60 * exception for any SBE internal failures.
63 * - Device driver failures
64 * - SBE internal failures
/openbmc/gpioplus/src/gpioplus/internal/
H A Dfd.hpp23 * @throws std::system_error for underlying syscall failures
32 * @throws std::system_error for underlying syscall failures
72 * @throws std::system_error for underlying syscall failures
78 * @throws std::system_error for underlying syscall failures
85 * @throws std::system_error for underlying syscall failures
/openbmc/u-boot/test/
H A Drun13 [ $? -ne 0 ] && failures=$((failures+1))
19 failures=0
56 if [ $failures == 0 ]; then
/openbmc/openbmc/poky/scripts/lib/resulttool/
H A Djunit.py18 failures = 0
30 failures += 1
42 testsuite_node.set("failures", "%s" % failures)
/openbmc/gpioplus/src/gpioplus/
H A Dhandle.hpp78 * @throws std::system_error for underlying syscall failures
91 * @throws std::system_error for underlying syscall failures
99 * @throws std::system_error for underlying syscall failures
106 * @throws std::system_error for underlying syscall failures
H A Devent.hpp68 * @throws std::system_error for underlying syscall failures
82 * @throws std::system_error for underlying syscall failures
90 * @throws std::system_error for underlying syscall failures
H A Dchip.hpp71 * @throws std::system_error for underlying syscall failures
78 * @throws std::system_error for underlying syscall failures
/openbmc/openbmc/meta-phosphor/recipes-phosphor/chassis/
H A Dobmc-host-failure-reboots.bb1 SUMMARY = "Enables reboots on host failures"
3 on host failures"
/openbmc/openbmc/poky/scripts/contrib/
H A Ddevtool-stress.py105 failures = 0
131 failures += 1
140 if failures:
151 failures = 0
194 failures += 1
203 if failures:
/openbmc/openbmc/poky/meta/lib/oeqa/core/
H A Drunner.py72 # Print the errors/failures early to aid/speed debugging, its a pain
74 for t in ['failures', 'errors', 'skipped', 'expectedFailures']:
92 …g += " (successes=%d, skipped=%d, failures=%d, errors=%d)" % (len(self.successes), len(self.skippe…
96 result_types = {'failures': 'FAILED', 'errors': 'ERROR', 'skipped': 'SKIPPED',
197 # Class setup failures wouldn't enter stopTest so would never display
235 # Override as we unexpected successes aren't failures for us
236 return (len(self.failures) == len(self.errors) == 0)
239 # Account for expected failures
/openbmc/u-boot/test/py/tests/
H A Dtest_efi_selftest.py19 m = u_boot_console.p.expect(['Summary: 0 failures', 'Press any key'])
21 raise Exception('Failures occurred during the EFI selftest')
119 m = u_boot_console.p.expect(['Summary: 0 failures', 'Press any key'])
121 raise Exception('Failures occurred during the EFI selftest')
198 m = u_boot_console.p.expect(['Summary: 0 failures', 'Press any key'])
200 raise Exception('Failures occurred during the EFI selftest')
/openbmc/qemu/linux-user/
H A Dlinuxload.c107 /* FIXME - handle put_user() failures */ in loader_build_argptr()
115 /* FIXME - handle put_user() failures */ in loader_build_argptr()
120 /* FIXME - handle put_user() failures */ in loader_build_argptr()
125 /* FIXME - handle put_user() failures */ in loader_build_argptr()
130 /* FIXME - handle put_user() failures */ in loader_build_argptr()
135 /* FIXME - handle put_user() failures */ in loader_build_argptr()
/openbmc/phosphor-hwmon/
H A Dmeson.options9 description: 'Set sensor value to -errno on read failures.',
22 …description: 'Update functional property on read failures. Incompatible with negative-errno-on-fa…
/openbmc/qemu/bsd-user/
H A Dbsdload.c110 /* FIXME - handle put_user() failures */ in loader_build_argptr()
114 /* FIXME - handle put_user() failures */ in loader_build_argptr()
119 /* FIXME - handle put_user() failures */ in loader_build_argptr()
122 /* FIXME - handle put_user() failures */ in loader_build_argptr()
127 /* FIXME - handle put_user() failures */ in loader_build_argptr()
/openbmc/qemu/python/qemu/qmp/
H A Derror.py6 semantic failures (e.g. "failed to connect") without needing to know the
40 Abstract error class for protocol failures.
/openbmc/openbmc-test-automation/redfish/dmtf_tools/
H A DRedfish_Reference_Checker.robot33 # Work complete, total failures: 0
34 Should Match Regexp ${output} Work complete, total failures:[ ]+0
/openbmc/ibm-logging/
H A Ddbus.hpp41 * Returns an empty map if there are any failures.
57 * Returns an empty map if there are any failures.
88 * Returns an empty map if there are any failures.
/openbmc/qemu/scripts/qapi/
H A Dbackend.py35 :raise QAPIError: On failures.
58 :raise QAPIError: On failures.
/openbmc/docs/designs/
H A Dbmc-service-failure-debug-and-recovery.md11 The capability to debug critical failures of the BMC firmware is essential to
14 This design addresses a few classes of failures:
32 As such, failures of BMC subsystems may impact external consumers.
38 Complexity and coupling drive concern around the risk of critical failures in
100 Failures of platform data transports generally leave out-of-band interfaces
152 ## Handling platform-data-transport-provider failures
165 …| Graceful reboot request | Normal circumstances or recovery from platform data provider failures |
442 ## Handling platform-data-provider failures
446 As noted above, these types of failures usually yield a system that can continue
476 failures and do the following when one fails from within the configuration
/openbmc/openbmc/meta-openembedded/meta-webserver/recipes-webadmin/cockpit/files/
H A D0001-Makefile-common.am-Create-src-common-directory-befor.patch9 it will end in build failures
28 # libcockpit-common.a static-links an HTML template to use on failures
/openbmc/u-boot/drivers/net/phy/
H A Dmeson-gxl.c15 /* This function is provided to cope with the possible failures of this phy
18 * - Early failures: MII_LPA is just 0x0001. if MII_EXPANSION reports that
21 * - Late failures: MII_LPA is filled with a value which seems to make sense
/openbmc/u-boot/tools/binman/
H A Dbinman91 for test, err in result.failures:
92 print err, result.failures
93 if result.errors or result.failures:
H A Dbinman.py91 for test, err in result.failures:
92 print err, result.failures
93 if result.errors or result.failures:

12345678910>>...18