In many places checking for nullptr is done using EXPECT test macros
that doesn't return from the function when condition is not met
(i.e. they are non-fatal). Lack of further error handling results
in a subsequent segfault. To avoid that in most places it's sufficient
to change macro type to ASSERT.
Signed-off-by: NRobert Drab <robert.drab@huawei.com>

Merge pull request !81 from zhouhouxin/N/A

Merge pull request !82 from zhouhouxin/N/A

Merge pull request !80 from zhouhouxin/N/A

Merge pull request !79 from zhouhouxin/N/A

Merge pull request !73 from 南先森/addbootstrapt_20210325_3

Change-Id: I6e1914c3e737ceccb4c84c7b23a9f98fbd1f292e

Merge pull request !68 from chuaizhzh/Sscanf_20210324

Change-Id: I3ad8064485ced9689f1d13feb27d63d6d96af9cc

Merge pull request !65 from gaohanyi1982/master

Merge pull request !64 from zhouhouxin/N/A

Merge pull request !61 from zjucx/N/A

Merge pull request !63 from zhouhouxin/N/A

Merge pull request !59 from zjucx/N/A

Merge pull request !52 from guyuanzhang/22

Merge pull request !53 from chuaizhzh/deletetestMaxPipe20210317

Change-Id: Ibbcb5e022ac97d6fb350399a6bca3d954b89b1e1

测试用例中遍历了32个pipe，其中有pipe被其他进程使用测试失败
删除遍历的操作，此处没有必要测试

Change-Id: I06414c93909fed65152c42c983ddf4ffe419d702

Change-Id: I583b28de8b3c0173193e3cedd3a94c6f84af437d

Merge pull request !50 from jiyong/N/A

Merge pull request !49 from jiyong/myfeature

Merge pull request !48 from jiyong/myfeature

Merge pull request !45 from jiyong/myfeature

Merge pull request !44 from jiyong/master