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

Fixup the testsuite fails on macOS #373

Merged

Conversation

bak1an
Copy link
Contributor

@bak1an bak1an commented Nov 19, 2017

Default tmpdir on macOS is is a symlink pointing somewhere in
/private/.... Because of this in the testsuite we should
always use realpaths since byebug outputs those by default.

Without the fix it is full of failures like https://gist.github.com/bak1an/4f6bdbbadfe96c53bd9d16dd86a87779

The PR also disables WhereWithNotDeeplyNestedPathsTest for darwin since default $TMPDIR on macOS nowadays is something like /var/folders/5g/s0v3cc2x34ddw3ydhyvkryvr0000gn/T/ (which has realpath /private/var/folders/5g/s0v3cc2x34ddw3ydhyvkryvr0000gn/T/). This is the opposite of not deeply nested and just fails.

Copy link
Owner

@deivid-rodriguez deivid-rodriguez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bak1an Thanks so much for doing this! ❤️

Build on appveyor is failing due to an environmental issue, can you add the workaround mentioned here so that it passes?

@bak1an
Copy link
Contributor Author

bak1an commented Nov 20, 2017

It fails there with a new issue now. Will take a look into that.

@bak1an
Copy link
Contributor Author

bak1an commented Nov 20, 2017

Appveyor build fix went into #376

Default tmpdir on macOS is is a symlink pointing somewhere in
`/private/...`.  Because of this in the testsuite we should
always use realpaths since byebug outputs those by default.
@bak1an
Copy link
Contributor Author

bak1an commented Nov 20, 2017

Rebased that to include windows build fix

@deivid-rodriguez
Copy link
Owner

Thanks @bak1an!

I have another little request. I used to run Travis against both macOS and Linux in the past but I disabled it because macOS was hard to get passing and I didn't feel it was useful. However, most developers run macOS these days so it seems like a great thing to ensure that the tests pass in that environment.

Can you try enabling Travis on macOS and see if it passes? Ref: https://docs.travis-ci.com/user/multi-os/.

@bak1an
Copy link
Contributor Author

bak1an commented Nov 21, 2017

Makes sense @deivid-rodriguez

Will try and see what happens.

@deivid-rodriguez
Copy link
Owner

I'm going to merge this for now, we can take care of adding macOS to the CI in a separate PR!

Thanks @bak1an!!

@deivid-rodriguez deivid-rodriguez merged commit dea61c5 into deivid-rodriguez:master Nov 26, 2017
@bak1an bak1an deleted the macos_testsuite_fix branch November 26, 2017 15:52
@bak1an
Copy link
Contributor Author

bak1an commented Nov 26, 2017

Thanks @deivid-rodriguez!

Most likely will spend time on macOS travis configuration next week.

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

Successfully merging this pull request may close these issues.

None yet

2 participants