garydgregory commented on PR #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-1105839064
OK, then if someone wants to get this build green, they know where to dig.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
garydgregory commented on PR #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-1104473323
@boris-petrov
#151 is in, but the builds still fail here. Any ideas?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
garydgregory commented on PR #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-1104060162
Hi @boris-petrov
May you rebase on master?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
garydgregory commented on pull request #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-752099832
Hi @boris-petrov
As you may have seen in the check list, this PR breaks the build:
```
Tests run: 93, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.007 sec
garydgregory commented on pull request #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-747478482
@boris-petrov
Please rebase on master to pickup better unit test assertion messages in
`ProviderWriteTests`.
garydgregory commented on pull request #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-747078789
Hi @boris-petrov
Please rebase on git master. TY!
This is an automated message from the Apache Gi
garydgregory commented on pull request #150:
URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-745262520
Hi @boris-petrov
Run a local build before you create a PR, as this would have show you this
change breaks the build.
I am not sure of the semantics, needs studying.
