Skip to content
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

Challenge 2 4 gives bad error on Windows #15

Open
niklasjansson opened this issue Mar 11, 2016 · 4 comments
Open

Challenge 2 4 gives bad error on Windows #15

niklasjansson opened this issue Mar 11, 2016 · 4 comments

Comments

@niklasjansson
Copy link

While running Challenge 2 4, the check

(is (= ["Peer executing task :identity"
              "Peer executing task :identity"
              "Peer executing task :identity"
              "Peer executing task :read-segments"
              "Peer executing task :write-segments"]
             (sort (butlast (rest results))))))))

fails. On windows, each row has an appended \r.

@lbradstreet
Copy link
Member

Thanks for the report. We admit that we had not tested it on Windows. We'll get it fixed up soon!

On 11 Mar 2016, at 9:28 PM, niklasjansson notifications@github.com wrote:

While running Challenge 2 4, the check

(is (= ["Peer executing task :identity"
"Peer executing task :identity"
"Peer executing task :identity"
"Peer executing task :read-segments"
"Peer executing task :write-segments"](sort %28butlast %28rest results%29%29))))))
fails. On windows, each row has an appended \r.


Reply to this email directly or view it on GitHub.

@lbradstreet
Copy link
Member

Challenge 2_4 also fails when the job can start and finish before three peers are assigned to :identity. This has happened on CI. I'm not sure what the best way to fix this is since we're trying to demonstrate that multiple peers started up and :identity is the task they have to define. I guess we could change the sample to say that the users should increase n-peers rather than max-peers?

@Engelberg
Copy link

Ditto on challenge 4_1. Easy fix, change the regex in split to:
(clojure.string/split output #"\r?\n")

@MichaelDrogalis
Copy link
Contributor

We need to excise everywhere that does stdout checking. This really hurt us when we moved to Onyx 0.9.6 since errors are pretty printed directly to stdout. Should eliminate this issue once we do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants