Haris Peco

@nachtighall You can also look at https://github.com/jcabi/jcabi-aspects/issues/159

Since tests print - HTTP response status is not equal to 201: or - HTTP response status is not equal to 204: the problem can be caused with some temporary...

@darkled @dmarkov @yegor256 I have also tried rultor build locally. The build pass all tests. However, there are a difference. When running a build after 'at rultor merge', the build...

@yegor256 @dmarkov @darkled I have tried the build more times (with the failsafe.github.key property). One build fails with the following failure: ``` Tests run: 6, Failures: 1, Errors: 0, Skipped:...

@yegor256 :( not addressed again. All discussion is related to this issue: "RtReleaseAssetsITCase and RtReleasesITCase tests fail randomly". I have changed the title to "Integration tests fail randomly", because it...

@yegor256 This PR is relevant: https://github.com/jcabi/jcabi-github/pull/1162. The com.jcabi.github.RtReposITCase test also fails sometimes.

@yegor256 I also can happen when port is free, but it is still in TIME_WAIT state. The solution is to use ``` TCPSelectorHandler.setReuseAddress(true} ``` that is ``` Socket.setReuseAddress(true) ``` anywhere....

@yegor256 It is clear to run some separate tests, but I want to run all tests in same way as rultor run them. > RtForksITCase requires additional parameter -Dfailsafe.github.organization= where...

@yegor256 It is weird that rultor persistently fails when merge https://github.com/jcabi/jcabi-github/issues/932. I have managed to reproduce it once in Eclipse and once or twice with command line using only failsafe.github.key....

There are two issues here. 1) The RtGithub class creates the USER_AGENT constant using the manifest file. Android repacks all libraries and the 'JCabi-Version' property and other similar properties doesn't...