-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Conversation
I am in love with the new way of selecting targets and entry points for tests, great job! :D |
@diasdavid that error should have been fixed from this: ipfs-inactive/interface-js-ipfs-core#148 might be others around as well. Jest validates things a bit more strict than mocha |
Updated and released interface-ipfs-core to 0.31.2 Now seeing other errors:
and
|
✅ Browser tests are working fine in isolation |
maybe try no-parallel? |
@diasdavid looking at these failures, they don't look related to aegir to me, rather than other things are actually broken |
Hm.. it might be that due to the new aegir, some things need to change, however, the tests do pass with old aegir. This is also happening with ipfs-inactive/js-ipfs-http-client#585 and even in the aegir-test-repo ipfs-inactive/aegir-test-repo#1 (comment) which suggests that it was not properly tested before the 12.0.0 release. Let's figure out first in aegir test repo, then js-ipfs-api (which is very close) and then here. Probably fixing for one will fix for all anyway :) |
This might also indicate that some things were not being properly tested before and we have actual failures in these cases |
fix for Buffer issue is here: https://github.com/pull-stream/pull-ws/pull/20/files |
package.json
Outdated
@@ -26,7 +26,7 @@ | |||
"release-minor": "aegir release --type minor --no-parallel", | |||
"release-major": "aegir release --type major --no-parallel", | |||
"test": "aegir test --no-parallel --timeout 50000", | |||
"test:node": "aegir test --target node --no-parallel", | |||
"test:node": "aegir test --target node --no-parallel --timeout 50000", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really prefer to see these timeouts in tests. It will help us target batch by batch and do improvs across the board :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
feel free, but I don't think it is that useful compared to the amount of time it costs to increase timeouts in each tests manually
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(and how often that is breaking)
Tests started working on circle now, due to the changes in the libp2p modules some hashes changed, (dag node protobuf orders the bytes a bit different now), but those fixes should be done independently |
@dignifiedquire went ahead to try js-ipfs with next AEgir but started seeing some strange behaviors and errors. From what I can infer, the new AEgir doesn't like how interface spec tests are loaded by. See errors below:
See how it is showing logs from PubSub tests and fails on the Files with an exception that is really unexpected:
describe does not expect any arguments
Mind checking?