运行失败的命令并停止truss。
如果您使用服务的用户运行失败。
当采用其他分配策略时，这个程序应该会运行失败。
The same program can and should fail when it runs with different allocation policy.
如果运行失败，函数将返回False。
在本文所介绍的场景中，程序可能会因为缺少内存而运行失败。
In the scenario presented here, a program can fail due to the lack of memory.
现在可以再次运行测试，其中一个测试如预期一样运行失败。
I can now run the tests again, and one of the tests breaks as expected.
该错误通常发生在尝试启动外部工具并且该工具运行失败时。
This error generally occurs when you attempt to launch an external tool and the tool fails to run.
它可能也会运行失败，但是在失败时，该脚本会说明哪个参数需要调整。
It will probably fail too, but in doing so it will indicate which parameters need to be adjusted. The parameters are stored in this file.
由于日志客户端的同步特性，如果日志应用程序运行失败则业务应用程序同样也会失败。
Due to the synchronous nature of the logging client, the business application needs to fail in case the logging application fails.
图像显示包含允许在一个网格的特定节点上重新运行失败的命令的选项的快照。
Image shows snapshot with option to rerun failed commands on specific nodes of a grid.
您的框架应该为每个测试用例分配一个数，为了简单地再次运行失败的测试用例。
Your framework should assign a number to each test case to allow for easy rerunning of failing test cases.
如果make运行失败，那么在顶层目录中寻找适合自己系统的makefile。
If the make fails, look in the topmost directory for a makefile specific to your system.
更有利的是，TestNG采取了只重新运行失败测试的机制，这使它的依赖性测试设置更为完善。
Better yet, TestNG complements its dependency testing setup with a mechanism for rerunning only failed tests.
在大型测试套件中，这种重新运行失败测试的能力显得尤为方便。这是TestNG独有的一个特性。
The ability to rerun failed tests is especially handy in large test suites, and it's a feature you'll only find in TestNG.
如果函数运行成功，它将以字节书的形式返回文件大小；如果运行失败，它将返回False。
This function returns the file size in bytes on success or FALSE on failure.
在这种情况下，recipe会在正确的位置添加所有必要的代码，这会显著减少导致运行失败或安全脆弱性的错误机会。
In this case the recipe would add all the necessary code in the right places, greatly reducing the chance of a mistake leading to a runtime failure or security vulnerability.
要在一个节点上重新运行失败的命令，请选定该服务器并单击action下拉菜单，然后单击rerunCommand。
You can rerun the failed command on a node by choosing the server and clicking on the Action drop-down menu, then rerun command.
一个程序在测试它的JVM上运行非常完美，但在你最重要客户支持的JVM上它却糟糕地运行失败了，这是完全有可能的。
It is entirely possible that such a program will run perfectly on the JVM on which you test it and then fail miserably on the JVM favored by your most important customer.
例如，如果一个系统调用返回 Err#2ENOENT（没有这样的文件或目录），就表示此命令要寻找一个文件或目录，但是无法找到，因此运行失败。
For example, a system call returning with Err#2 ENOENT (No such file or directory) would indicate that the command is expecting to find a file or directory but can't and subsequently fails.
如果你正经历失败，那是因为你正在运行引起失败的软件。
If you are failing, it's because you're running on software that causes failure.
所以，在前面的例子里，您只需重新运行那三个失败的测试，而不是整个测试套件。
So, in the previous example, you would only have to rerun the three failed tests and not the whole suite.
在编写代码前编写测试这种作法意味着，在测试运行并失败之前，不会做工作中真正有趣的部分。
Writing a test before the code means you don't get to do the fun part of the job until the test runs and fails.
如果该代码包含任何错误输入，它在运行时肯定会失败。
The code can fail at run time if it includes even a simple typo.
然后运行这个测试证实测试失败。
但是，等一下—当我重新运行该行为时，它仍然失败！
如果后端数据库失败，或者您的网络连接失败或较慢，您的应用程序可以继续运行，这种失败对于应用程序是透明的，不会产生任何影响。
If the back-end database fails, or if your network connection to it fails or slows, your application keeps running, and this failure is transparent to and does not affect your application.
没有比发现运行构建失败的原因仅仅是由于存在以前构建的工件这件事更让人郁闷的了。
There are few more frustrating things than running a build that fails, only to discover that it's because artifacts from a previous build are still resident.
这个版本与需要XSDsdo转换功能生成的SDO的那个不相容，因此可能引起应用程序的运行时失败。
This version is not compatible to the one required by the generated SDOs used by the XSD SDO transform feature, and therefore may cause run time failure of the application.
当我运行测试时，我失败了，预期的结果为31，但实际结果为32。
When I run the tests, I get a failure that tells me 31 was expected, but the result was 32.
否则，测试样例将完整运行，然后失败。
Otherwise, the test case is run to completion and then it is failed.
应用推荐