Marios Trivyzas created FLINK-24604:
---
Summary: Failing tests for casting decimals to boolean
Key: FLINK-24604
URL: https://issues.apache.org/jira/browse/FLINK-24604
Project: Flink
Issue
Greg Hogan created FLINK-6918:
-
Summary: Failing tests: ChainLengthDecreaseTest and
ChainLengthIncreaseTest
Key: FLINK-6918
URL: https://issues.apache.org/jira/browse/FLINK-6918
Project: Flink
Thank you, we'll try to address these issues soon...
On Fri, Jul 17, 2015 at 7:07 PM, Gábor Gévay wrote:
> > BlobUtilsTest.before:45 null
> > BlobUtilsTest.before:45 null
> > BlobServerDeleteTest.testDeleteFails:291 null
> > BlobLibraryCacheManagerTest.testRegisterAndDownload:196 Could n
> BlobUtilsTest.before:45 null
> BlobUtilsTest.before:45 null
> BlobServerDeleteTest.testDeleteFails:291 null
> BlobLibraryCacheManagerTest.testRegisterAndDownload:196 Could not
> remove write permissions from cache directory
> BlobServerPutTest.testPutBufferFails:224 null
> BlobServerP
Since the failing tests on windows have come up again, I did find some
failing tests when the community was testing the release candidates for
0.9.0 release.
Here is one of the log outputs: http://pastebin.com/raw.php?i=VWbx2ppf
These errors are on running mvn clean verify. Following were the
Yes, please open JIRAs for that.
If you want to provide some fixes, increasing the timeout in (4) is
probably reasonable.
On Fri, Jul 17, 2015 at 5:53 PM, Gábor Gévay wrote:
> Hello!
>
> I tried to setup a development environment on Windows, but several
> tests are failing:
>
> 1. The setWritab
Hello!
I tried to setup a development environment on Windows, but several
tests are failing:
1. The setWritable problem. This will be worked around by [1]
2. The tryCleanupOnError before close problem [2]. This could be
half-fixed by doing fixing 2. in the comment I wrote there, but I
think that
Matthias J. Sax created FLINK-2348:
--
Summary: Instable (failing) Tests
Key: FLINK-2348
URL: https://issues.apache.org/jira/browse/FLINK-2348
Project: Flink
Issue Type: Bug
<
mj...@informatik.hu-berlin.de> wrote:
> Hi,
>
> I hit two failing tests recently. The first once
> (flink-streaming-examples), failed a single time (see
> https://travis-ci.org/mjsax/flink/jobs/70396872)
>
> > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elap
Hi,
I hit two failing tests recently. The first once
(flink-streaming-examples), failed a single time (see
https://travis-ci.org/mjsax/flink/jobs/70396872)
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.057 sec
> <<<
igate the problem oneself and fix it.
>>>>
>>>> But this is basically our current approach and I don't know how to
>> enforce
>>>> this policy by some means. Maybe it's making people more aware of it and
>>>> motivating people to
>> But this is basically our current approach and I don't know how to
> enforce
> >> this policy by some means. Maybe it's making people more aware of it and
> >> motivating people to have a stable master.
> >>
> >> Cheers,
> >> Til
ally our current approach and I don't know how to enforce
>> this policy by some means. Maybe it's making people more aware of it and
>> motivating people to have a stable master.
>>
>> Cheers,
>> Till
>>
>> On Thu, Jun 4, 2015 at 9:06 AM, Matthias J. S
t; this policy by some means. Maybe it's making people more aware of it and
> motivating people to have a stable master.
>
> Cheers,
> Till
>
> On Thu, Jun 4, 2015 at 9:06 AM, Matthias J. Sax <
> mj...@informatik.hu-berlin.de> wrote:
>
>> I think, people should be
will lower the test coverage such that bugs that would
have been caught by an test that infrequently fails for another reason, are not
identified.
How about opening JIRAs for non-deterministically failing tests and assigning a
special label for that. Whenever, a test fails one can check if this
policy by some means. Maybe it's making people more aware of it and
motivating people to have a stable master.
Cheers,
Till
On Thu, Jun 4, 2015 at 9:06 AM, Matthias J. Sax <
mj...@informatik.hu-berlin.de> wrote:
> I think, people should be forced to fixed failing tests asap. One way
I think, people should be forced to fixed failing tests asap. One way to
go, could be to lock the master branch until the test is fixed. If
nobody can push to the master, pressure is very high for the responsible
developer to get it done asap. Not sure if this is Apache compatible.
Just a thought
ik.hu-berlin.de> wrote:
>
>> I basically agree that the current policy on not optimal. However, I
>> would rather give failing tests "top priority" to get fixed (if possible
>> within one/a-few days) and not disable them.
>>
>> -Matthias
>>
>> O
@matthias: That is the implicit policy right now. Seems not to work...
On Thu, Jun 4, 2015 at 12:40 AM, Matthias J. Sax <
mj...@informatik.hu-berlin.de> wrote:
> I basically agree that the current policy on not optimal. However, I
> would rather give failing tests "top priority&
I basically agree that the current policy on not optimal. However, I
would rather give failing tests "top priority" to get fixed (if possible
within one/a-few days) and not disable them.
-Matthias
On 06/04/2015 12:32 AM, Ufuk Celebi wrote:
> Hey all,
>
> we have certain te
Hey all,
we have certain test cases, which are failing regularly on Travis. In all
cases I can think of we just keep the test activated.
I think this makes it very hard for regular contributors to take these
failures seriously. I think the following situation is not unrealistic with
the current p
21 matches
Mail list logo
