-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
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
Test on more elixir versions #74
Test on more elixir versions #74
Conversation
Looks like not all elixir/erlang combinations (apart from obvious ones, like elixir 1.x and erlang 19.0) are supported. I'll look closer at what's going on. |
First of all, the issues are not related to the code, they are related to the build. In one case, a test using So two issues block this PR at the moment:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quick question here:
.travis.yml
Outdated
sudo: false | ||
env: | ||
- MIX_ENV=test STRIPE_SECRET_KEY=non_empty_secret_key_string | ||
script: mix coveralls.travis | ||
after_script: | ||
- mix inch.report | ||
exclude: | ||
- otp_release: 19.0 | ||
elixir: 1.1.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the exclude
doing here when used in combination with those elixir
and otp_release
above?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshsmith Travis builds a matrix with values from otp_releases
as rows and values from elixir
as columns. Then it runs the test script for each "cell", e.g. a pair of elixir/otp_release.
Using exclude
we can "cross out" cells for which we don't want Travis to run the test script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gmile I guess my question though is whether we want exclude
when we're listing it above? Wouldn't we just not list it above and then exclude
isn't necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joshsmith I think elixir 1.1.x doesn't work with erlang 19.0, that's why it was listed
@gmile would you mind rebasing this onto latest? |
2 similar comments
1 similar comment
Hey @joshsmith, I just rebased the branch. Sorry it took a while. |
Hey @gmile no worries at all! I think I'm going to squash, too. I hadn't realized before that I can do this myself if you enable me to do so in your fork. |
@gmile reached out on the Elixir slack, but I can't actually update your branch. Would you be able to squash down to one commit or give me access to your fork to do so? Thanks! |
@joshsmith added you as collaborator of my fork, simply because that was quicker to do :) |
🙌 thanks for everything you did working through this. A lot of work for +9 LOC, but I know the work that went into it, so 👍 |
No description provided.