Home
last modified time | relevance | path

Searched refs:wrong (Results 1 – 25 of 396) sorted by relevance

12345678910>>...16

/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-pylint/
H A D0001-Adjust-test-expectations-for-ptest.patch17 @@ -3,14 +3,14 @@ wrong-import-order:14:0:14:10::"standard
18 …wrong-import-order:15:0:15:15::"standard import ""datetime"" should be placed before third party i…
19 …wrong-import-order:18:0:18:22::"third party import ""totally_missing"" should be placed before loc…
20 …wrong-import-order:20:0:20:14::"third party import ""astroid"" should be placed before local impor…
21 -wrong-import-order:22:0:22:22::"first party import ""pylint.checkers"" should be placed before loc…
22 -wrong-import-order:23:0:23:25::"first party import ""pylint.config"" should be placed before local…
23 -wrong-import-order:24:0:24:17::"first party import ""pylint.sys"" should be placed before local im…
24 -wrong-import-order:25:0:25:28::"first party import ""pylint.pyreverse"" should be placed before lo…
25 -wrong-import-order:30:0:30:40::"third party import ""six.moves.urllib.parse.quote"" should be plac…
26 -wrong-import-order:31:0:31:23::"first party import ""pylint.constants"" should be placed before lo…
[all …]
/openbmc/qemu/tests/qapi-schema/
H A Denum-wrong-data.err1 enum-wrong-data.json: In enum 'MyEnum':
2 enum-wrong-data.json:2: 'data' must be an array
/openbmc/qemu/tests/qemu-iotests/
H A D207.out43 …0", "options": {"driver": "ssh", "location": {"host-key-check": {"hash": "wrong", "mode": "hash", …
45 Job failed: remote host key fingerprint 'md5:HASH' does not match host_key_check 'md5:wrong'
60 …0", "options": {"driver": "ssh", "location": {"host-key-check": {"hash": "wrong", "mode": "hash", …
62 Job failed: remote host key fingerprint 'sha1:HASH' does not match host_key_check 'sha1:wrong'
77 …0", "options": {"driver": "ssh", "location": {"host-key-check": {"hash": "wrong", "mode": "hash", …
79 Job failed: remote host key fingerprint 'sha256:HASH' does not match host_key_check 'sha256:wrong'
H A D174.out4 == reading wrong format should fail ==
/openbmc/linux/Documentation/networking/
H A Dxfrm_proc.rst33 i.e. Either inbound SPI, address, or IPsec protocol at SA is wrong
37 e.g. SA key is wrong
58 e.g. Inbound SAs are correct but SP rule is wrong
/openbmc/qemu/tests/tcg/multiarch/
H A Dnoexec.c.inc63 printf("[ FAILED ] wrong si_addr (%p != %p)\n",
71 printf("[ FAILED ] wrong pc (%p != %p)\n", pc, expected_pc);
77 printf("[ FAILED ] wrong arg (%d != %d)\n", arg, test->expected_arg);
/openbmc/linux/lib/
H A Dtest_uuid.c45 static void __init test_uuid_failed(const char *prefix, bool wrong, bool be, in test_uuid_failed() argument
51 wrong ? "passed on wrong" : "failed on", in test_uuid_failed()
/openbmc/openbmc/poky/meta/recipes-connectivity/nfs-utils/nfs-utils/
H A D0001-locktest-Makefile.am-Do-not-use-build-flags.patch6 Using CFLAGS_FOR_BUILD etc. here means it is using wrong flags
8 is common when cross-building. It can pass wrong paths to linker
/openbmc/linux/arch/xtensa/
H A DKconfig.debug8 This check can spot missing TLB invalidation/wrong PTE permissions/
31 It is easy to make wrong hardware configuration, this test should catch it early.
/openbmc/linux/tools/testing/selftests/x86/
H A Dtrivial_32bit_program.c8 # error wrong architecture
H A Dtrivial_64bit_program.c8 # error wrong architecture
/openbmc/linux/Documentation/process/
H A Dmanagement-style.rst51 Namely that you are in the wrong job, and that **they** should be managing
62 can be made small by just always making sure that if you were wrong (and
63 you **will** be wrong), you can always undo the damage later by
65 **two** inconsequential decisions - the wrong one **and** the right one.
91 wrong is sometimes very hard indeed.
103 might be the wrong thing. You should always reserve the right to change
130 something wrong with both projects, and the reason the people involved
131 couldn't decide was that they were both wrong. You end up coming up
219 Things will go wrong, and people want somebody to blame. Tag, you're it.
252 somebody else puts on airs, it **really** rubs us the wrong way. You may
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/cpprest/cpprest/
H A Ddisable-outside-tests.patch82 - TEST(hostname_mismatch) { handshake_error_test_impl(U("wss://wrong.host.badssl.com/")); }
83 + //TEST(hostname_mismatch) { handshake_error_test_impl(U("wss://wrong.host.badssl.com/")); }
/openbmc/linux/arch/arm/boot/dts/marvell/
H A Ddove-cubox-es.dts10 /* sdio0 card detect is connected to wrong pin on CuBox ES */
/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/
H A Dparselogs-ignores-x86_64.txt3 wrong ELF class
H A Dparselogs-ignores-x86.txt3 wrong ELF class
/openbmc/linux/Documentation/hwmon/
H A Dadm1025.rst52 properly, you'll have a wrong +12V reading or a wrong VID reading. The way
/openbmc/phosphor-logging/gen/
H A Dmeson.build11 warning('Generated meson files from wrong version of sdbus++-gen-meson.')
/openbmc/sdbusplus/example/gen/
H A Dmeson.build11 warning('Generated meson files from wrong version of sdbus++-gen-meson.')
/openbmc/phosphor-dbus-interfaces/gen/
H A Dmeson.build11 warning('Generated meson files from wrong version of sdbus++-gen-meson.')
/openbmc/sdbusplus/test/gen/
H A Dmeson.build11 warning('Generated meson files from wrong version of sdbus++-gen-meson.')
/openbmc/phosphor-networkd/gen/
H A Dmeson.build11 warning('Generated meson files from wrong version of sdbus++-gen-meson.')
/openbmc/openbmc/meta-facebook/meta-catalina/recipes-phosphor/state/phosphor-state-manager/
H A Dphosphor-wait-power-off@.service13 # This is wrong, but at least gives us something since we're not using
/openbmc/openbmc/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer/
H A Duse-native-pkg-config.patch7 to the default value which obviously is wrong.
/openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/state/phosphor-state-manager/
H A Dphosphor-wait-power-off@.service13 # This is wrong, but at least gives us something since we're not using

12345678910>>...16