Hi
I have an issue while running the following line while usig flink v 0.8.1 (:
val asdf = new AvroTypeInfo[AlignmentRecord](classOf[AlignmentRecord])
Alignment record belongs to the package :
org.bdgenomics.formats.avro.AlignmentRecord
http://mvnrepository.com/artifact/org.bdgenomics.bdg-for
Hi,
I'm Akshay Dixit[1], a 4th year undergrad at VIT Vellore, India. I'm
currently interested in distributed systems and stream processing and am
looking to delve deeper into the subject, and hope to get some insight by
contributing to Apache Flink. I've gathered some idea of the
flink-streaming co
It seems that the current master is broken, with respect to the tests.
I see all build on Travis consistently failing, in the gelly project. Since
Travis is a bit behind in the "apache" account, I triggered a build in my
own account. The hash is the same, it should contain the master from
yesterda
Cause of the Failures:
The tests in DegreesWithExceptionITCase use the context execution
environment without extending a test base. This context environment
instantiates a local excution environment with a parallelism equal to the
number of cores. Since on travis, build run in containers on big ma
I am fixing this with a slight modification of
https://github.com/apache/flink/pull/475
On Sun, Mar 15, 2015 at 3:54 PM, Stephan Ewen wrote:
> Cause of the Failures:
>
> The tests in DegreesWithExceptionITCase use the context execution
> environment without extending a test base. This context en
Hi Stephan,
The degree of parallelism was manually set there. MultipleProgramsTestBase
cannot be extended; Ufuk explained why.
But I see that for the latest travis check, that test passed.
https://github.com/apache/flink/pull/475
On Sun, Mar 15, 2015 at 3:54 PM, Stephan Ewen wrote:
> Cause of
Hi Filip,
thank you for reporting the issue. Its an issue with the AvroTypeInfo. I've
pushed a fix to the "master" branch.
If you want, you can port your program to 0.9-SNAPSHOT, there, the issue
should be fixed.
I'll also push a fix to the "release-0.8" branch if you want to keep using
the 0.8 s
I think the issue is that our tests are executed on travis machines with
different physical CPU core counts.
I've pushed a 5 days old commit (
https://github.com/rmetzger/flink/commit/b4e8350f52c81704ffc726a1689bb0dc7180776d)
to travis, and it also failed with that issue:
https://travis-ci.org/rme
Waiting for travis to give me the green light, then I'll push the fix...
On Sun, Mar 15, 2015 at 5:04 PM, Robert Metzger wrote:
> I think the issue is that our tests are executed on travis machines with
> different physical CPU core counts.
>
> I've pushed a 5 days old commit (
>
> https://githu
I've just pushed a fix to my "release-0.8" branch.
If you want, you can build the version with the fix yourself:
git clone https://github.com/rmetzger/flink.git
cd flink
git checkout release-0.8
mvn clean install -DskipTests
Once that has finished, you can set the version in your pom.xml to
"0.8-
Hi,
thanks a lot for fixing this so quickly!
Just to make sure I fully understand what happened, how come the travis
build was successful when we merged this, but failed later?
Is there a way to avoid such issues in the future?
Cheers,
Vasia.
On 15 March 2015 at 17:07, Stephan Ewen wrote:
>
11 matches
Mail list logo
