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

t0030: replace some expect_failure with expect_success #926

Merged
merged 1 commit into from
Apr 1, 2015

Conversation

chriscool
Copy link
Contributor

It looks like some tests that were expected failures
are now always succeeding, so let's mark them as such.

License: MIT
Signed-off-by: Christian Couder chriscool@tuxfamily.org

@btc btc added the status/in-progress In progress label Mar 14, 2015
@jbenet
Copy link
Member

jbenet commented Mar 17, 2015

I'm not sure these are fixed on OSX.

@chriscool
Copy link
Contributor Author

Yeah, maybe they are not fixed on OSX.

I saw an OSX Jenkins test before, so I thought that the tests would tell us about OSX, but it looks like the OSX test has been removed from Jenkins.


test_expect_failure "'ipfs mount' fails when no mount dir (issue #341)" '
test_expect_success "'ipfs mount' fails when no mount dir" '
Copy link
Member

Choose a reason for hiding this comment

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

This one fails in osx still.

checking known breakage:
    test_must_fail ipfs mount -f=not_ipfs -n=not_ipns >actual

test_must_fail: command succeeded: ipfs mount -f=not_ipfs -n=not_ipns
not ok 6 - 'ipfs mount' fails when no mount dir (issue #341) # TODO known breakage

@jbenet
Copy link
Member

jbenet commented Mar 18, 2015

@chriscool i've fixed the outstanding osx issue (#935) and enabled the osx test-- so presumably it wiill run next time you push. (so will need to rebase to grab the fix)

@jbenet
Copy link
Member

jbenet commented Mar 20, 2015

I saw an OSX Jenkins test before, so I thought that the tests would tell us about OSX, but it looks like the OSX test has been removed from Jenkins.

Yeah, it was flakey unfortunately. I've replaced it with OSX on travis, which has been working well.

@whyrusleeping whyrusleeping added the kind/test Testing work label Mar 28, 2015
@chriscool chriscool force-pushed the t0030_remove_expected_failures branch from dcd254e to 8254724 Compare March 31, 2015 19:43
@chriscool
Copy link
Contributor Author

I just rebased and force pushed to see if the OSX test pass now...

@jbenet
Copy link
Member

jbenet commented Apr 1, 2015

@chriscool sorry about that, the repo location change does not mesh well with how Go likes doing imports. A fix went in for that at #996 -- still wondering what to do about the past history (bisecting to the past will not work with go's imports :( ).

It looks like some tests that were expected failures
are now always succeeding, so let's mark them as such.

License: MIT
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
@jbenet jbenet force-pushed the t0030_remove_expected_failures branch from 8254724 to e0c4638 Compare April 1, 2015 00:26
@jbenet
Copy link
Member

jbenet commented Apr 1, 2015

just rebased

@jbenet
Copy link
Member

jbenet commented Apr 1, 2015

Looks like it passed!

jbenet added a commit that referenced this pull request Apr 1, 2015
t0030: replace some expect_failure with expect_success
@jbenet jbenet merged commit 9d7603e into master Apr 1, 2015
@jbenet jbenet deleted the t0030_remove_expected_failures branch April 1, 2015 00:52
@jbenet jbenet removed the status/in-progress In progress label Apr 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/test Testing work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants