{"push_id":2444468279,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"b1fa08a975b326b59e9a511aff062e34a456f236","before":"45e68a352d4ceb2e2646170bf134ea22f46bc513","commits":[{"sha":"b1fa08a975b326b59e9a511aff062e34a456f236","author":{"name":"Konstantin Varlamov","email":"58fb2c763efb016031c88de46efb608aee8f4c6e@users.noreply.github.com"},"message":"C++ migration: fix some Timestamp tests failing on Linux. (#999)\n\nSome Timestamp tests check that constructor fails if given values beyond\r\nthe supported (pretty wide) range. In case Timestamp is created from\r\nchrono::time_point, the time_point's underlying duration is\r\nimplementation-defined and may overflow when tests try to set it to\r\na value beyond Timestamp supported range. To work around this, make\r\nthese tests not run if time_point cannot represent boundary values on\r\nthis platform. For example, on OS X, time_point has microseconds\r\nprecision, so the tests may run, but on Linux, time_point has\r\nnanoseconds precision, which would overflow.","distinct":true,"url":"https://api.github.com/repos/firebase/firebase-ios-sdk/commits/b1fa08a975b326b59e9a511aff062e34a456f236"}]}
{"actor":{"display_login":"var-const"}}