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

vibe.core 1429: Timeout occurred too late #55

Open
wilzbach opened this issue Feb 4, 2018 · 0 comments
Open

vibe.core 1429: Timeout occurred too late #55

wilzbach opened this issue Feb 4, 2018 · 0 comments
Labels
flaky-test CI tests that sometimes fail and sometimes succeed

Comments

@wilzbach
Copy link
Member

wilzbach commented Feb 4, 2018

+ echo '[INFO] Running test vibe.core.net.1429'
[INFO] Running test vibe.core.net.1429
+ cd tests/vibe.core.net.1429
+ dub --compiler=dmd --override-config=vibe-d:core/vibe-core --build-mode=separate
Performing "debug" build using dmd for x86_64.
taggedalgebraic 0.10.9: target for configuration "library" is up to date.
eventcore 0.8.27: target for configuration "epoll" is up to date.
stdx-allocator 2.77.0: target for configuration "library" is up to date.
vibe-core 1.4.0-alpha.1: target for configuration "epoll" is up to date.
vibe-d:utils 0.8.3-alpha.3: target for configuration "library" is up to date.
vibe-d:data 0.8.3-alpha.3: target for configuration "library" is up to date.
tests ~master: building configuration "application"...
../../../../.dub/packages/vibe-core-1.4.0-alpha.1/vibe-core/source/vibe/core/log.d(613,21): Deprecation: Built-in hex string literals are deprecated, use `std.conv.hexString` instead.
Linking...
To force a rebuild of up-to-date targets, run again with --force.
Running ./tests 
[main(fz4O) INF] Exception received: Receive timeout.
core.exception.AssertError@source/app.d(24): Timeout occurred too late (2 secs, 817 ms, 361 μs, and 4 hnsecs).
----------------
??:? _d_assert_msg [0x60b40e]
source/app.d:24 @safe void app._sharedStaticCtor1().__lambda2() [0x57e56e]
../../../../.dub/packages/vibe-core-1.4.0-alpha.1/vibe-core/source/vibe/core/task.d:552 void vibe.core.task.TaskFuncInfo.set!(void function() @safe*).set(ref void function() @safe*).callDelegate(ref vibe.core.task.TaskFuncInfo) [0x588292]
../../../../.dub/packages/vibe-core-1.4.0-alpha.1/vibe-core/source/vibe/core/task.d:573 void vibe.core.task.TaskFuncInfo.call() [0x5a5625]
../../../../.dub/packages/vibe-core-1.4.0-alpha.1/vibe-core/source/vibe/core/task.d:386 nothrow void vibe.core.task.TaskFiber.run() [0x5a4c3d]
??:? void core.thread.Fiber.run() [0x63973b]
??:? fiber_entryPoint [0x63960a]
??:? [0xffffffff]
Program exited with code -6

Seen here: https://ci.dlang.io/blue/organizations/jenkins/dlang-org%2Fphobos/detail/PR-6041/6/pipeline

@s-ludwig s-ludwig added the flaky-test CI tests that sometimes fail and sometimes succeed label Feb 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test CI tests that sometimes fail and sometimes succeed
Projects
None yet
Development

No branches or pull requests

2 participants