Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #548 .
Instead of putting "tests" in the CI, I think we should put everything in examples for consistency. Ifthis get pulled I'll finnish the work with "tests".
The job is done by 2 bash lines in the .travis.yml to add them, as we should rely on "dub test" doing the biggest part of the job. This may not be the best way to do it, but it's better than what we used to have. Any advice / direction is welcome.
There are some examples that are build but not run:
daytime: Address specified is not correct + use a priviledged port;
mongodb: Needs a server
redis[-pubsub]: Needs a server;
sendmail: Needs a server
I don't think it's worth installing a mongodb / redis / smtp server on the CI machine just to test the driver, so there is no attempt to run them.