-
-
Notifications
You must be signed in to change notification settings - Fork 679
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
Issue #154: make journey-test.sh use exercises #277
Issue #154: make journey-test.sh use exercises #277
Conversation
…nstead of problems.
Yup and this script runs in CI and that works perfectly. I'm gonna "review" this as approved; feel free to merge whenever you're ready, @FridaTveit. It is a design goal of the script to both fail fast and give good signal as to what's wrong when something goes wrong. I'd be happy to work through whatever you're seeing to get it running locally. What happens when you run the script? |
Thanks! :) Well it had lots of complaints about ruby (first that I didn't have it, then that it didn't like version 2.2.6, then that gem needed some update) that I've managed to fix. But now it's saying |
Looks like the attempt to detect which OS your machine has failed. What do you get when you run:
(p.s. I'm online right now; find me at https://gitter.im/exercism/xjava or https://appear.in/exercism/xjava) |
I'm not a rubyist, but this line would appear to reference a Gemfile that's not part of the repo? |
From what I remember from trying to debug this, that Gemfile is from x-api which the script fetches at some point? An update on how I got on with this: I managed to get most of the script working with help from @jtigger on Saturday. Thanks! :) But now I'm getting this error:
|
Hey Frida... I notice that in the "GET" there's an extra character...
That 0x0D or decimal 13: the carriage return character...... oh! I see it right there in the command-line:
🤷♂️ ... looking into it... |
Yes, I did notice that but I have no idea where the |
I just tried running the script with it iterating over |
Hey now! Well then this script needs a few more lessons in diplomacy 'cause it needs to be running on whatever machine. I suspect we can tweak this |
I was able to get the exercise slugs on a single line like this:
Does that help? |
Great, that worked thanks! :) Now it's just complaining about the symlinks and from issue #148 it looks like they won't work on Windows. So maybe I should just admit defeat as it looks like this is as far as it'll get on my machine... :P |
I'd rather dereference the symlinks (i.e. remove them and copy the files) and rely on the journey test to catch problems, than have a core maintainer not have the ability to run the suite on her or his machine (of the OS of her or his choosing). I'm not saying you have to do that work, Frida, just that I'd rather it go that way. |
Sure, that's what I've been doing locally (removing them and copying the files) when I've needed to run tests with symlinks. I just didn't want to cause lots of problems with my uncooperative OS :P But I'm happy to do that work :) Or do you think they should be |
I see this as "discovered scope" in this PR — and should be done as part of getting the script "up-to-date". Yes, please! To put a finer point on all this: maintainers are an Free Open Source Software product's lifeblood. Without maintainers, very little gets done. It's a happystance that we, as maintainers, are delighted by the sheer doing of the work. But in every way that is in our control, the happy part of that stance should be cultivated. If there's an apparent conflict between some other need and what would make a maintainer's life better, the latter should usually prevail. This may seem like a little thing: copying files where there are symlinks. But even the little things add up. Thanks for volunteering to do this, @FridaTveit! |
Yay, it finally runs on my machine! Happy days! :D |
Awesome, nice work @FridaTveit! |
Nice work, indeed, @FridaTveit! I'm also starting to help maintain the Kotlin track. "Stealing" your work to update the journey test over there too. So, your efforts are immediately doubled!! |
Made bin/journey-test.sh iterate over exercises instead of problems. I've tested the individual lines I've changed and they give the same output as when they were iterating over problems. However I've not been able to run the entire script to test it... Any suggestions for how to do that are very welcome! :)