Skip to content
This repository was archived by the owner on Aug 12, 2020. It is now read-only.

Some tests are failing on Windows #196

Closed
richardschneider opened this issue Nov 8, 2017 · 0 comments
Closed

Some tests are failing on Windows #196

richardschneider opened this issue Nov 8, 2017 · 0 comments
Assignees

Comments

@richardschneider
Copy link
Contributor

richardschneider commented Nov 8, 2017

The with-dag-api tests are still failing, because it uses IPFS for testing and IPFS is not yet windows ready.

When IPFS is windows ready, we can update the package.json and then re-test.

Also re-enable the tests.

daviddias pushed a commit that referenced this issue Nov 10, 2017
* fix: export files with a POSIX path

* test(with-dag-api): some fixup for windows

It is still failing, because it uses IPFS for testing and IPFS is not yet windows ready.

* chore: run on appveyor

* test: run more tests in the browser

* test: timeout

* test: remove debug code

* test: fix lint issues

* test(browser): are taking forever!!!

* test: skip with-dag-api until #196 is resolved

* test: more timeouts

* Revert "test: run more tests in the browser"

This reverts commit c6f2bff.

* test: more testing issues

* chore: npm ERR! peer dep missing: ajv@^5.0.0, required by ajv-keywords@2.1.1

* test: lint issues

* test: more issues

* test: follow the standards

* test: ipfs-repo@0.18.3 breaks our tests

* chore: bump deps

* chore: bump timeouts for nodejs 6
@richardschneider richardschneider self-assigned this Nov 11, 2017
richardschneider added a commit that referenced this issue Nov 11, 2017
As the new js-ipfs is not yet available on NPM, I've linked to the master branch.
@ghost ghost added the status/in-progress In progress label Dec 5, 2017
@ghost ghost removed the status/in-progress In progress label Dec 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant