We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ChannelAccessIFRemoteTest are currently failing on travis while still succeeding on Jenkins. The most likely reason is that the docker container has limitation on the n/w configuration which results in some of the client unit test failing to connect to the server (https://travis-ci.org/epics-base/pvAccessJava/builds/274601801?utm_source=github_status&utm_medium=notification)
@mdavidsaver @mrkraimer @ralphlange During the epics meeting it was stated that these tests should be considered as bad tests which should be updated.
The text was updated successfully, but these errors were encountered:
Try EPICS_PVA_ADDR_LIST=127.255.255.255
Sorry, something went wrong.
#12
bce320a
Create .travis.yml (#10)
d703982
* Create .travis.yml * Create README.md * Update README.md * #12
No branches or pull requests
ChannelAccessIFRemoteTest are currently failing on travis while still succeeding on Jenkins. The most likely reason is that the docker container has limitation on the n/w configuration which results in some of the client unit test failing to connect to the server (https://travis-ci.org/epics-base/pvAccessJava/builds/274601801?utm_source=github_status&utm_medium=notification)
@mdavidsaver @mrkraimer @ralphlange
During the epics meeting it was stated that these tests should be considered as bad tests which should be updated.
The text was updated successfully, but these errors were encountered: