yes it was not backported to the trunk branch.

After skipping the sign step, the build fails in yarn-ui with this error. I
have tried a few times by now but it always fails so it's not intermittent.
There was some python failure as well before this which I fixed by setting
the PYTHON env variable in the docker file. Any idea about this error?
Thanks

[INFO] --- exec-maven-plugin:1.3.1:exec (ember build) @ hadoop-yarn-ui ---
(node:10063) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use
os.tmpdir() instead.
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-array-contains-helper -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-bootstrap -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-bootstrap -> ember-wormhole -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-cli-app-version -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-cli-htmlbars-inline-precompile -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-cli-jquery-ui -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui -> moment ->
ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui -> ember-d3 ->
ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-disable-proxy-controllers -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui -> lodash ->
ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui -> ember-resolver
-> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-spin-spinner -> ember-cli-babel
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at
least ember-cli-babel 6.6. Version 5.2.8 located: yarn-ui ->
ember-truth-helpers -> ember-cli-babel
broccoli-babel-transpiler is opting out of caching due to a plugin that
does not provide a caching strategy: `function(babel) {
    var t = babel.types;
...
..
..
..

ENOENT: no such file or directory, stat
'/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/tmp/broccoli_merge_trees-input_base_path-rp0oGH9N.tmp/.bin/phantomjs'

Error: ENOENT: no such file or directory, stat
'/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/tmp/broccoli_merge_trees-input_base_path-rp0oGH9N.tmp/.bin/phantomjs'

    at Object.statSync (fs.js:1016:3)

    at buildEntry
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:343:17)

    at BroccoliMergeTrees._mergeRelativePath
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:251:19)

    at BroccoliMergeTrees._mergeRelativePath
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:304:31)

    at BroccoliMergeTrees.build
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/ember-cli/node_modules/broccoli-merge-trees/index.js:83:24)

    at
/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/broccoli-plugin/read_compat.js:93:34

    at tryCatch
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/rsvp/dist/rsvp.js:525:12)

    at invokeCallback
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/rsvp/dist/rsvp.js:538:13)

    at publish
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/rsvp/dist/rsvp.js:508:7)

    at flush
(/build/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/target/webapp/node_modules/rsvp/dist/rsvp.js:2415:5)

error Command failed with exit code 1.

yarn run v1.22.5

$ TMPDIR=tmp node/node ./node_modules/ember-cli/bin/ember build -prod

WARNING: Node v12.22.1 has currently not been tested against Ember CLI and
may result in unexpected behaviour.

version: 1.13.14

Could not find watchman, falling back to NodeWatcher for file system events.

Visit http://www.ember-cli.com/user-guide/#watchman for more info.

BuildingBuilding.Building..Building...BuildingBuilding.Building..Building...BuildingBuilding.Building..Building...BuildingBuild
failed.

info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this
command.

[*INFO*]
*------------------------------------------------------------------------*


On Mon, Jul 29, 2024 at 2:25 PM Steve Loughran <ste...@cloudera.com.invalid>
wrote:

> + one thing to consider is you don't need to sign the macos releases, or
> publish to maven staging. all we want is that native lib
>
> hadoop release support takes the 86 tarball and builds a new tar with a
> different name, the lib swapped over but the exact same jar files, then
> signs it outside of the docker image
>
> https://github.com/apache/hadoop-release-support
>
> On Mon, 29 Jul 2024 at 19:57, Steve Loughran <ste...@cloudera.com> wrote:
>
> >
> >
> >
> > On Fri, 26 Jul 2024 at 23:08, Mukund Madhav Thakur <mtha...@cloudera.com
> >
> > wrote:
> >
> >> Omg Steve already found and fixed the JAVA_HOME issue in create-release
> >> for arm64 which I had to spend some time recently.
> >> https://github.com/apache/hadoop/pull/6962
> >>
> >
> > i really don't remember that. Why did you have to repeat it...did I not
> do
> > the right branches?
> >
> >>
> >> Thanks for the  link Ayush. I don't see anything gpg related here
> though.
> >>
> >>
> >>
> >> On Fri, Jul 26, 2024 at 12:31 AM Ayush Saxena <ayush...@gmail.com>
> wrote:
> >>
> >>> Hi Mukund,
> >>> If I remember correctly, there were some issues with the
> >>> create-release for Arm, but after some changes it worked on branch-3,
> >>> but I think the changes were done only on branch-3, maybe because some
> >>> changes were already present on trunk.
> >>> You check this PR [1], if it has anything relevant missing on trunk
> >>>
> >>> -Ayush
> >>>
> >>> [1] https://github.com/apache/hadoop/pull/4953
> >>>
> >>> On Fri, 26 Jul 2024 at 03:46, Mukund Madhav Thakur
> >>> <mtha...@cloudera.com.invalid> wrote:
> >>> >
> >>> > Hi Everyone,
> >>> > I am trying to create arm64 binaries for RC 3.4.1 in my local MacOS
> >>> but it
> >>> > is failing with below gpg signing error inside docker. Same command
> >>> runs
> >>> > perfectly fine
> >>> > outside docker on my mac. Please advise of any solution/workaround if
> >>> any
> >>> > of you have seen this before. Thanks
> >>> >
> >>> > starting gpg agent
> >>> >
> >>> > GPG_AGENT_INFO=/home/mthakur/.gnupg/S.gpg-agent::1
> >>> >
> >>> > Warming the gpg-agent cache prior to calling maven
> >>> >
> >>> > gpg: WARNING: unsafe ownership on homedir '/home/mthakur/.gnupg'
> >>> >
> >>> > gpg: can't connect to the agent: IPC connect call failed
> >>> >
> >>> > gpg: can't connect to the agent: IPC connect call failed
> >>> >
> >>> > gpg: keydb_search failed: No agent running
> >>> >
> >>> > gpg: no default secret key: No agent running
> >>> >
> >>> > gpg: signing failed: No agent running
> >>> >
> >>> > rm: cannot remove '/build/source/patchprocess/warm.asc': No such file
> >>> or
> >>> > directory
> >>>
> >>
>

Reply via email to