Searched refs:messages (Results 51 – 75 of 94) sorted by relevance
1234
5 …' => true, 'timesten' => false); // test runs on these DBs: different error messages from TimesTen
2 Check various LOB error messages
53 Delete 4 messages for Unique ID generation
28 echo "Messages: " . $status->messages . "\n";
13 // create a new mailbox and add two new messages to it
55 // without output buffering, the debug messages will cause all manner of warnings
2 more invalid arguments and error messages
2 recvmsg(): receive SCM_CREDENTIALS messages
35 …e routing table causes an interface other than lo to be used for sending messages to $mcastaddr\n";160 …g the routing table causes an interface other than lo to be used for sending messages to 224.0.0.23
21 "", // I think both p8 and php are wrong on the messages here22 //p8 generates different messages to php, php is probably wrong
27 // Otherwise the pipe may clog up with unread log messages.
68 Warning: stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages:
35 // Otherwise the pipe may clog up with unread log messages.
136 echo "Delete 4 messages for Unique ID generation\n";137 // Delete messages to remove the numerical ordering
43 * $tester->expectLogNotice() around last reload due to presence of debug messages.
158 * @param int $timeoutSeconds Timeout in seconds for reading of all messages.159 …am int $timeoutMicroseconds Additional timeout in microseconds for reading of all messages.
2 shmop extension error messages
69 HashTable messages; /* array of xmlNodePtr */ member
19 // If no error messages gets printed do not know if proper usage of closeCursor() makes any27 // This is proper usage of closeCursor(). It shall prevent any further error messages.
7 * that the function outputs proper warning messages wherever expected.
7 * and see that function emits proper warning messages wherever expected.
15 of parameters, and try to output meaningful error messages.29 the function should operate quietly and not output any error messages.
63 // Check that none of the above would have caused any error messages if MYSQL_REPORT_ERROR would
Completed in 99 milliseconds
