collapse
0%
WDescription%
Build stability: All recent builds failed.0
Test Result: 54 tests failing out of a total of 2,844 tests.98
Build History
x
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer47 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB
 Trigger TimerTriggerCause : Started by timer65 MB

Project Xtreams

Xtreams is a generalized stream/iterator framework providing simple, unified API for reading from different kinds of sources and writing into different kinds of destinations (Collections, Sockets, Files, Pipes, etc). Streams themselves can be sources or destinations as well. This allows to stack streams on top of each other. At the bottom of such stack is some kind of non-stream (e.g. a collection), we will call it a terminal. Directly above that is a specialized stream providing a streaming facade over the terminal. The rest of the streams in the stack we'll call transforms. Their primary purpose is to perform some kind of transformation on the elements that are passing through. Application code interacts with the top stream of the stack the same way it would with any other stream (or stream stack) producing/consuming the same elements. The goal of the framework is to provide consistent behavior between different stacks so that the application can treat them the same way regardless of what exactly is the ultimate source or destination. For example if the application code analyzes binary data, it should be able to treat the source stream the same way if it is a simple stream over a ByteArray or if it is a stack that provides contents of a specific binary part of a mulitpart, gziped, chunked HTTP response from a socket. Xtreams is an attempt to achieve this goal in a scalable and efficient manner.

https://code.google.com/p/xtreams/

Configurations

UnstablePHARO=30 UnstablePHARO=40 UnstablePHARO=50 FailedPHARO=60 
Disk Usage Trend
Disk Usage Trend
Latest Test Result(54 failures / -1)
Disk Usage
Directory iconJob2 GB
Directory iconAll builds2 GB
Directory iconLocked builds167 MB
Directory iconAll workspaces48 KB
Directory iconSlave workspaces48 KB
Directory iconNon-slave workspaces-