{"push_id":1455706091,"size":1,"distinct_size":1,"ref":"refs/heads/development","head":"ac17ce8714ae3568054fb2c3c9abcbd14b30fc45","before":"f178deeaa7e8529faea0ebaca15fd079166fe317","commits":[{"sha":"ac17ce8714ae3568054fb2c3c9abcbd14b30fc45","author":{"name":"Arpad Tigyi","email":"15735cf82bdccbef550d1737e5e65e6a232b645c@logmein.com"},"message":"Feature/xcl 2674 travis fix (#72)\n\n[ Description ]\r\nFalse positive builds were experienced on Travis CI. This story investigated the root cause of not triggering red output for failing builds: except command swallowed the failures. Problem solved here, except script now throws problem out to Travis who makes failing builds red again. Hurray.\r\nThis \"bug\" was introduced a while ago (~a month) since then some failures were hidden by these false positives which were unveiled with this move. These bugs were also fixed and now all greens are true-positive builds. Hurray.\r\n\r\n[ JIRA ]\r\nfind reason of Travis CI's false positive greens\r\nhttps://jira.3amlabs.net/browse/XCL-2674\r\n\r\n[ Reviewer ]\r\n\r\n[ QA ]\r\nEye-o-scopic analysis of each Travis CI build output to check all greens are successful builds. Failing red builds proved that there are true-negative builds as well.\r\n\r\n[ Release Notes ]\r\nTravis CI maintenance.\r\n\r\n* Make expect return with the inner process's return value\r\n\r\n* Fixed a failing integration test\r\n\r\n* Added missing dependencies for travis\r\n\r\n* [build] trying the fix on the expect script\r\n\r\n* Init BSP rng in unit test where needed\r\n\r\n* [ travis false-positives ] using basic_utest_frame in all utest_time_frame to handle memory monitor well\r\n\r\n* [ travis false-positive ] review changes","distinct":true,"url":"https://api.github.com/repos/xively/xively-client-c/commits/ac17ce8714ae3568054fb2c3c9abcbd14b30fc45"}]}
{"actor":{"display_login":"atigyi"}}