Tue, 19 Sep 2017 10:06:46 +0200 *** empty log message ***
sr [Tue, 19 Sep 2017 10:06:46 +0200] rev 342
*** empty log message ***
Fri, 15 Sep 2017 13:19:23 +0200 *** empty log message ***
sr [Fri, 15 Sep 2017 13:19:23 +0200] rev 341
*** empty log message ***
Thu, 14 Sep 2017 15:02:12 +0200 *** empty log message ***
sr [Thu, 14 Sep 2017 15:02:12 +0200] rev 340
*** empty log message ***
Thu, 14 Sep 2017 11:38:31 +0200 *** empty log message ***
sr [Thu, 14 Sep 2017 11:38:31 +0200] rev 339
*** empty log message ***
Wed, 13 Sep 2017 13:37:42 +0200 *** empty log message ***
sr [Wed, 13 Sep 2017 13:37:42 +0200] rev 338
*** empty log message ***
Wed, 13 Sep 2017 10:36:41 +0200 *** empty log message ***
sr [Wed, 13 Sep 2017 10:36:41 +0200] rev 337
*** empty log message ***
Tue, 12 Sep 2017 15:37:32 +0200 *** empty log message ***
sr [Tue, 12 Sep 2017 15:37:32 +0200] rev 336
*** empty log message ***
Tue, 12 Sep 2017 13:33:30 +0200 *** empty log message ***
sr [Tue, 12 Sep 2017 13:33:30 +0200] rev 335
*** empty log message ***
Sat, 19 Aug 2017 14:43:15 +0100 Test report: print system identification in stacktrace jv stx-8.0.0
Jan Vrany <jan.vrany@fit.cvut.cz> [Sat, 19 Aug 2017 14:43:15 +0100] rev 334
Test report: print system identification in stacktrace Unfortunately, Jenkins's JUnit plugin does not show nor sort failed tests based on their report. This workaround make it easier.
Thu, 13 Jul 2017 03:57:41 +0000 update tags
convert-repo [Thu, 13 Jul 2017 03:57:41 +0000] rev 333
update tags
(0) -300 -100 -10 +10 +100 tip