You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yu Li (Jira)" <ji...@apache.org> on 2020/02/15 07:45:00 UTC

[jira] [Closed] (FLINK-16052) Homebrew test failed with 1.10.0 dist package

     [ https://issues.apache.org/jira/browse/FLINK-16052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yu Li closed FLINK-16052.
-------------------------
    Fix Version/s:     (was: 1.10.1)
                       (was: 1.11.0)
         Assignee: Yu Li
       Resolution: Not A Bug

Homebrew PR merged thus closing the JIRA, remove fix version since this is not a Flink bug. Thanks all for the efforts!

> Homebrew test failed with 1.10.0 dist package
> ---------------------------------------------
>
>                 Key: FLINK-16052
>                 URL: https://issues.apache.org/jira/browse/FLINK-16052
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Scripts
>    Affects Versions: 1.10.0
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Major
>
> After updating the Homebrew formula to 1.10.0 (in {{$(brew --repository homebrew/core)}} directory) with patch of this [PR|https://github.com/Homebrew/homebrew-core/pull/50110], executing `brew install --build-from-source Formula/apache-flink.rb` and then `brew test Formula/apache-flink.rb`, we could see below error:
> {code:java}
> [ERROR] Unexpected result: Error: Could not find or load main class org.apache.flink.runtime.util.BashJavaUtils
> [ERROR] The last line of the BashJavaUtils outputs is expected to be the execution result, following the prefix 'BASH_JAVA_UTILS_EXEC_RESULT:'
> Picked up _JAVA_OPTIONS: -Djava.io.tmpdir=/private/tmp/apache-flink-test-20200214-33361-1jotper -Duser.home=/Users/jueding/Library/Caches/Homebrew/java_cache
> Error: Could not find or load main class org.apache.flink.runtime.util.BashJavaUtils
> [ERROR] Could not get JVM parameters properly.
> Error: apache-flink: failed
> Failed executing:
> {code}
> After a bisect checking on {{flink-dist/src/main/flink-bin/bin}} changes, confirmed the above issue is related to FLINK-15488, but we will see new errors like below after reverting FLINK-15488 (and FLINK-15519):
> {code:java}
> ==> /usr/local/Cellar/apache-flink/1.10.0/libexec/bin/start-cluster.sh
> ==> /usr/local/Cellar/apache-flink/1.10.0/bin/flink run -p 1 /usr/local/Cellar/apache-flink/1.10.0/libexec/examples/streaming/WordCount.jar --input input --output result
> Last 15 lines from /Users/jueding/Library/Logs/Homebrew/apache-flink/test.02.flink:
> 	at akka.actor.ActorCell.receiveMessage(ActorCell.scala:592)
> 	at akka.actor.ActorCell.invoke(ActorCell.scala:561)
> 	at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258)
> 	at akka.dispatch.Mailbox.run(Mailbox.scala:225)
> 	at akka.dispatch.Mailbox.exec(Mailbox.scala:235)
> 	... 4 more
> Caused by: org.apache.flink.runtime.resourcemanager.exceptions.UnfulfillableSlotRequestException: Could not fulfill slot request b7f17c0928112209ae873d089123b1c6. Requested resource profile (ResourceProfile{UNKNOWN}) is unfulfillable.
> 	at org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl.lambda$fulfillPendingSlotRequestWithPendingTaskManagerSlot$9(SlotManagerImpl.java:772)
> 	at org.apache.flink.util.OptionalConsumer.ifNotPresent(OptionalConsumer.java:52)
> 	at org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl.fulfillPendingSlotRequestWithPendingTaskManagerSlot(SlotManagerImpl.java:768)
> 	at org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl.lambda$internalRequestSlot$7(SlotManagerImpl.java:755)
> 	at org.apache.flink.util.OptionalConsumer.ifNotPresent(OptionalConsumer.java:52)
> 	at org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl.internalRequestSlot(SlotManagerImpl.java:755)
> 	at org.apache.flink.runtime.resourcemanager.slotmanager.SlotManagerImpl.registerSlotRequest(SlotManagerImpl.java:314)
> 	... 27 more
> Error: apache-flink: failed
> Failed executing:
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)