-
Notifications
You must be signed in to change notification settings - Fork 16
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
Add simple test #28
Add simple test #28
Conversation
I am trying to figure out what the travies files should look like. This is what I have for language: python
jdk: oraclejdk8
python:
- "3.6"
- "3.7"
branches:
only:
- master
- "/.*-[0-9]+\\..*/"
install: true
script: ".travis/build.sh"
cache:
directories:
- "~/.m2/repository" And this is what I have for
|
@ctrueden I tried to check the travis ci locally but it did not work for me. Should we just merge and then fix the travis ci config if necessary? |
Fixed the merge conflicts introduced in #30 |
8d06cd2
to
6fb4b6b
Compare
Simple tests so far: - test resolution for - auto - copy - hard - soft - test parsington with argument `1+3`
6fb4b6b
to
eea0c71
Compare
I rebased this over the latest master, fixing the conflicts. So this PR became a single commit adding the test suite as well as the stdout+stderr arguments to various functions. Hopefully I did it right. I then pushed a commit adding the Travis CI configuration. Unfortunately, one of the tests is failing for me locally:
And Travis is reporting the same failure as well. Also, the |
The tests worked locally for me after fixing the merge issues. Should we restore from my local branch? |
@hanslovsky Maybe just look at the patch above and see if anything jumps out at you? It's not that complicated. I may have simply done something wrong in the merge. You could also see if this branch now works for you locally as well. |
The test does not run locally. I figure the fastest way forward is to force-push my local branch again but without any travis files. |
@hanslovsky Please push it to a different branch. Then I will diff it against this one. |
I can do that but I am bit puzzled why you did not do that in the first place. |
Close in favor of #32 |
Simple tests so far:
1+3
Should be merged only after #26 as it builds on top of the commits in #26.