Comments (6)
@tiagomartinho the key here is maybe_nio_host='3(NXDOMAIN)'
which means host
was not able to correctly retrieve the host info which sometimes happens with VPN or proxies, i'll see if we can fail more clearly here
/cc @weissi
fwiw, all pull requests go through ci that runs these tests
from swift-nio.
@tomerd I'm not currently using a VPN or proxy, but maybe is a VPN configuration I have? Even if it's not currently active?
I also tried to run the integration test suite from Docker but I got:
FAILURE (oks: 3, failures: 14)
Is this expected?
Moreover I had 4 other questions:
- There is a particular reason not to use XCTest for the integration tests?
- Why the integration tests are not invoked with the command
swift test
? - Why are the tests 12, 13, and 14 skipped?
- I didn't found the CI documented in the project, is it public or private?
from swift-nio.
I also tried to run the integration test suite from Docker but I got:
how did you try to run it? in any case the work i am doing towards #83 should help make this run in docker correctly
Moreover I had 4 other questions:
- There is a particular reason not to use XCTest for the integration tests?
- Why the integration tests are not invoked with the command swift test?
- Why are the tests 12, 13, and 14 skipped?
- I didn't found the CI documented in the project, is it public or private?
i'll let @weissi answer 1-3. our ci is private atm
from swift-nio.
@tiagomartinho Sorry for the late reply, I was on holiday the last week:
There is a particular reason not to use XCTest for the integration tests?
Yes: These tests are end-to-end tests so they make sure everything works in an actual binary without mocking anything. This can't be done using XCTest. That said, we obviously have XCTest tests too. Some of those tests also test assertions (ie. make sure the program crashes) or compile binaries in a special mode. Also they for example test that we're compatible with a 3rd party HTTP client like cURL.
Why the integration tests are not invoked with the command swift test?
Because they're slower (they're not unit tests) and I'd also argue it'd be odd to shell out to an external program through swift test
Why are the tests 12, 13, and 14 skipped?
SKIP_test_13_http_pipelining.sh
: fixed with #62SKIP_test_12_headers_too_large.sh
&SKIP_test_14_strict_mode_assertion.sh
: because I didn't get to them yet, apologies, I;ll file an issue against me to do that.
from swift-nio.
filed as #132
from swift-nio.
With #132 present I think we can close this.
from swift-nio.
Related Issues (20)
- Remove all `#if swift(...)`s, all the ones I've seen in SwiftNIO are wrong. Needs to be `#if compiler` HOT 1
- 'LockStorage<Void>' has no member 'mutex' on Win11 HOT 1
- ByteBufferAllocator.allocate(capacity: Int) implementation does not correspond to the definition. HOT 7
- CMake build causes runtime crash from Atomics HOT 4
- Windows Support HOT 1
- ByteBuffer: Investigate optimal allocation sizes (probably just under a power of two) HOT 1
- MessageToByteHandler never shrinks its buffer (it should!) HOT 2
- We should offer the same `[get/set]MultipleIntegers` as we offer for `[read/write]MultipleIntegers` methods on ByteBuffer HOT 7
- Forceful unwrapping of bytes in NIOCore HOT 1
- Intermittent warning about liburing_nio.h not being included by CNIOLinux HOT 1
- NIOTypedWebSocketServerUpgrader hangs when connection is opened and closed without sending any data HOT 1
- _NIOFileSystem crash in swift v6 HOT 13
- ByteBuffer should have hex bytes initialiser / write method HOT 8
- macOS build broken (since Snippets) HOT 5
- add support of swift 6.0 with "-strict-concurrency=complete" HOT 1
- FileChunks isn't Sendable
- Give NIOLoopBoundBox a `sending` off-EL initialiser once compiler is ready
- raise CI timeout limit HOT 1
- NIOAsyncChannel doesn't flush all its writes if connection is closed HOT 5
- Support For Swift-HTTP-Types HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from swift-nio.