Failure without an error message

[est31]

Of the latest cargobomb run by @tomprince , the following regressions were reported without any error message:

• https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/radiant-rs-0.7.1/log.txt
• https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/pinyin-0.0.6/log.txt
• https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/ciruela-0.1.7/log.txt
• https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/ceramic-0.3.0/log.txt
• https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/bitarray-set-0.4.1/log.txt
• https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/bit-array-0.4.4/log.txt

[arielb1]

Occurred for ceramic again in http://cargobomb-reports.s3.amazonaws.com/pr-43880/b96d5eea76e758bdd82fd4169eb4d5f7e3ce4fe2/reg/ceramic-0.3.0/log.txt

[est31]

More from the latest report (1.20 stable vs 1.21 beta):

• http://cargobomb-reports.s3.amazonaws.com/stable-1.20-beta-1.21.0-beta.1/beta-2017-09-02/reg/assimp-0.2.0/log.txt
• http://cargobomb-reports.s3.amazonaws.com/stable-1.20-beta-1.21.0-beta.1/beta-2017-09-02/reg/bip_peer-0.2.4/log.txt
• http://cargobomb-reports.s3.amazonaws.com/stable-1.20-beta-1.21.0-beta.1/beta-2017-09-02/reg/bit-array-0.4.4/log.txt
• http://cargobomb-reports.s3.amazonaws.com/stable-1.20-beta-1.21.0-beta.1/beta-2017-09-02/reg/bitarray-set-0.4.1/log.txt
• http://cargobomb-reports.s3.amazonaws.com/stable-1.20-beta-1.21.0-beta.1/beta-2017-09-02/reg/ceramic-0.3.0/log.txt