{"push_id":884155088,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"db2521ee67836bb6a1b50fb1213fc6352511c7bd","before":"74b6f70c80dc5c6119c2aa325959d77670541f98","commits":[{"sha":"db2521ee67836bb6a1b50fb1213fc6352511c7bd","author":{"email":"7cbee43f705a831eb570831b19794e0345151b0a@jetbrains.com","name":"Alexander Udalov"},"message":"Rework TestlibTest, use JUnit console runner instead of manual suite\n\nThe problem with the manually created suite was that it was created in setUp()\nand so a lot of the hard work (compilation, test case lookup) was happening in\nsetUp(). If any exception is thrown in setUp(), tearDown() is not called,\nleaving the application (~9000+ subsequent tests) in the inconsistent state.\n\nSupport JUnit 4 tests via JUnit4TestAdapter. Previously only a small number of\ntest classes were actually run because this test was looking only for JUnit 3\ntestcases.\n\nDelete FilesTest#relativePath because it was testing a deprecated function\nand was failing if run from the project root","distinct":true,"url":"https://api.github.com/repos/JetBrains/kotlin/commits/db2521ee67836bb6a1b50fb1213fc6352511c7bd"}]}