@Sachin: This looks like a file permission issue. We should have someone else verify that on a Windows system.
On Wed, Jun 10, 2015 at 11:28 AM, Sachin Goel <sachingoel0...@gmail.com> wrote: > I have run "mvn clean verify" five times now and every time I'm getting > these failed tests: > > 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 > BlobServerPutTest.testPutNamedBufferFails:286 null > JobManagerStartupTest.before:55 null > JobManagerStartupTest.before:55 null > DataSinkTaskTest.testFailingDataSinkTask:317 Temp output file has > not been removed > DataSinkTaskTest.testFailingSortingDataSinkTask:358 Temp output file > has not been removed > TaskManagerTest.testSubmitAndExecuteTask**:123 assertion failed: > timeout (19998080696 nanoseconds) during expectMsgClass waiting for > class > org.apache.flink.runtime.messages.RegistrationMessages$RegisterTaskManager > TaskManagerProcessReapingTest.testReapProcessOnFailure:133 > TaskManager process did not launch the TaskManager properly. Failed to > look up akka.tcp://flink@127.0.0.1:50673/user/taskmanager > > ** fails randomly. > > Is someone able to reproduce these while building on a windows machine? I > would try to debug these myself but I'm not yet familiar with the core > architecture and API. > > -- Sachin > > On Wed, Jun 10, 2015 at 2:46 PM, Aljoscha Krettek <aljos...@apache.org> > wrote: > > > The KMeans quickstart example does not work with the current state of > > the KMeansDataGenerator. I created PR that brings the two in sync. > > This should probably go into the release since it affects initial user > > "satisfaction". > > > > On Wed, Jun 10, 2015 at 11:14 AM, Márton Balassi > > <balassi.mar...@gmail.com> wrote: > > > As for the streaming commit cherry-picked to the release branch: > > > This is an unfortunate communication issue, let us make sure that we > > > clearly communicate similar issues in the future. > > > > > > As for FLINK-2192: This is essentially a duplicate issue of the > > testability > > > of the streaming iteration. Not a blocker, I will comment on the JIRA > > > ticket, Gabor Hermann is already working on the root cause. > > > > > > On Wed, Jun 10, 2015 at 11:07 AM, Ufuk Celebi <u...@apache.org> wrote: > > > > > >> Hey Gyula, Max, > > >> > > >> On 10 Jun 2015, at 10:54, Gyula Fóra <gyula.f...@gmail.com> wrote: > > >> > > >> > This feature needs to be included in the release, it has been tested > > and > > >> > used extensively. And many applciations depend on it. > > >> > > >> It would be nice to announce/discuss this before just cherry-picking > it > > >> into the release branch. The issue is that no one (except you) knows > > that > > >> this is important. Let's just make sure to do this for future fixes. > > >> > > >> Having said that... it seems to be an important fix. Does someone have > > >> time (looking at Aljoscha ;)) to review the changes? > > >> > > >> > Maximilian Michels <m...@apache.org> ezt írta (időpont: 2015. jún. > > 10., > > >> Sze, > > >> > 10:47): > > >> > > > >> >> With all the issues discovered, it looks like we'll have another > > release > > >> >> candidate. Right now, we have discovered the following problems: > > >> >> > > >> >> 1 YARN ITCase fails [fixed via 2eb5cfe] > > >> >> 2 No Jar for SessionWindowing example [fixed in #809] > > >> >> 3 Wrong description of the input format for the graph examples (eg. > > >> >> ConnectedComponents) [fixed in #809] > > >> >> 4 TaskManagerFailsWithSlotSharingITCase fails > > >> >> 5 ComplexIntegrationTest.complexIntegrationTest1() (FLINK-2192) > fails > > >> > > >> Can we verify that the tests are defect and not the tested component? > ;) > > >> Otherwise, I would not block the release on flakey tests. > > >> > > >> >> 6 Submitting KMeans example to Web Submission Client does not work > on > > >> >> Firefox. > > >> >> 7 Zooming is buggy in Web Submission Client (Firefox) > > >> >> Do we have someone familiar with the web interface who could take a > > >> look at > > >> >> the Firefox issues? > > >> > > >> If not, I would not block the release on this. > > >
