Mock Version: 3.5 Mock Version: 3.5 Mock Version: 3.5 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target aarch64 --nodeps /builddir/build/SPECS/dsms-ui.spec'], chrootPath='/var/lib/mock/dist-an8.7-build-271636-64139/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=982gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target aarch64 --nodeps /builddir/build/SPECS/dsms-ui.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: aarch64 Building for target aarch64 Wrote: /builddir/build/SRPMS/dsms-ui-v1.0-1.an8.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target aarch64 --nodeps /builddir/build/SPECS/dsms-ui.spec'], chrootPath='/var/lib/mock/dist-an8.7-build-271636-64139/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=982gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target aarch64 --nodeps /builddir/build/SPECS/dsms-ui.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: aarch64 Building for target aarch64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.fB1qIX + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf dsms-ui-v1.0 + /usr/bin/gzip -dc /builddir/build/SOURCES/dsms-ui-v1.0.tar.gz + /usr/bin/tar -xof - + STATUS=0 + '[' 0 -ne 0 ']' + cd dsms-ui-v1.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + tar -xf /builddir/build/SOURCES/node_modules.tar.gz + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.0tFpOo + umask 022 build dsms-ui ... + cd /builddir/build/BUILD + cd dsms-ui-v1.0 + echo 'build dsms-ui ...' + echo + npm -v 6.14.17 + node -v v14.20.0 + npm run build > dsms-admin@1.0.0 build /builddir/build/BUILD/dsms-ui-v1.0 > vite build failed to load config from /builddir/build/BUILD/dsms-ui-v1.0/vite.config.ts error during build: Error: You installed esbuild for another platform than the one you're currently using. This won't work because esbuild is written with native code and needs to install a platform-specific binary executable. Specifically the "@esbuild/linux-x64" package is present but this platform needs the "@esbuild/linux-arm64" package instead. People often get into this situation by installing esbuild on Windows or macOS and copying "node_modules" into a Docker image that runs Linux, or by copying "node_modules" between Windows and WSL environments. If you are installing with npm, you can try not copying the "node_modules" directory when you copy the files over, and running "npm ci" or "npm install" on the destination platform after the copy. Or you could consider using yarn instead of npm which has built-in support for installing a package on multiple platforms simultaneously. If you are installing with yarn, you can try listing both this platform and the other platform in your ".yarnrc.yml" file using the "supportedArchitectures" feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures Keep in mind that this means multiple copies of esbuild will be present. Another alternative is to use the "esbuild-wasm" package instead, which works the same way on all platforms. But it comes with a heavy performance cost and can sometimes be 10x slower than the "esbuild" package, so you may also not want to do that. at generateBinPath (/builddir/build/BUILD/dsms-ui-v1.0/node_modules/esbuild/lib/main.js:1874:17) at esbuildCommandAndArgs (/builddir/build/BUILD/dsms-ui-v1.0/node_modules/esbuild/lib/main.js:1955:33) at ensureServiceIsRunning (/builddir/build/BUILD/dsms-ui-v1.0/node_modules/esbuild/lib/main.js:2119:25) at build (/builddir/build/BUILD/dsms-ui-v1.0/node_modules/esbuild/lib/main.js:2011:26) at bundleConfigFile (file:///builddir/build/BUILD/dsms-ui-v1.0/node_modules/vite/dist/node/chunks/dep-79892de8.js:63875:26) at loadConfigFromFile (file:///builddir/build/BUILD/dsms-ui-v1.0/node_modules/vite/dist/node/chunks/dep-79892de8.js:63851:31) at resolveConfig (file:///builddir/build/BUILD/dsms-ui-v1.0/node_modules/vite/dist/node/chunks/dep-79892de8.js:63466:34) at build (file:///builddir/build/BUILD/dsms-ui-v1.0/node_modules/vite/dist/node/chunks/dep-79892de8.js:46088:26) at CAC. (file:///builddir/build/BUILD/dsms-ui-v1.0/node_modules/vite/dist/node/cli.js:813:15) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! dsms-admin@1.0.0 build: `vite build` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the dsms-admin@1.0.0 build script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /builddir/.npm/_logs/2023-06-02T03_04_49_983Z-debug.log error: Bad exit status from /var/tmp/rpm-tmp.0tFpOo (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.0tFpOo (%build) Child return code was: 1 EXCEPTION: [Error('Command failed: \n # bash --login -c /usr/bin/rpmbuild -bb --noclean --target aarch64 --nodeps /builddir/build/SPECS/dsms-ui.spec\n', 1)] Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 93, in trace result = func(*args, **kw) File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 598, in do_with_status raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) mockbuild.exception.Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --noclean --target aarch64 --nodeps /builddir/build/SPECS/dsms-ui.spec