Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container prepare 2026/07/11 23:01:46 Entrypoint initialization Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container place-scripts 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-0-nb2cm 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-1-mgr65 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-2-55m98 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-3-gl5xr 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-4-xddtj 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-5-k6db9 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-6-7xq4h 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-7-2rtx4 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-8-f5mxb 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-9-nl6kw 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-10-mrmv6 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-11-8cz7l 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-13-rrsj6 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-14-5lhjw 2026/07/11 23:01:47 Decoded script /tekton/scripts/script-15-cv2dm Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container working-dir-initializer Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-git-clone git cloning url: https://github.com/greencapitaltrade/flash.git version refs/pull/302/head:PR-302@15d85920f69ff0582c1aa56d30f118d52cd71726 to dir: source Cloning into 'source'... From https://github.com/greencapitaltrade/flash * [new ref] refs/pull/302/head -> PR-302 Switched to branch 'PR-302' HEAD is now at 15d8592 docs(ci): flag unverified preview-URL hostname assumption in acceptance step checked out revision: refs/pull/302/head:PR-302@15d85920f69ff0582c1aa56d30f118d52cd71726 to dir: source Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-git-merge setup git user email jenkins-x@googlegroups.com Using SHAs from PULL_REFS=main:5661ae7af804f2804f30fccf4cd50ff6a001592f,302:15d85920f69ff0582c1aa56d30f118d52cd71726:refs/pull/302/head using base branch main and base sha 5661ae7af804f2804f30fccf4cd50ff6a001592f merging sha: 15d85920f69ff0582c1aa56d30f118d52cd71726 Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-update-repomix repomix-output.xml is up to date. Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-jx-variables WARNING: no $GIT_SECRET_MOUNT_PATH environment variable set about to run: git clone --no-checkout --filter=blob:none --depth=1 https://github.com/greencapitaltrade/mcu.git /tmp/jx-git-2533585150 in dir /tmp Cloning into '/tmp/jx-git-2533585150'... about to run: git sparse-checkout set --no-cone jx-requirements.yml .jx/gitops/source-config.yaml in dir /tmp/jx-git-2533585150 about to run: git checkout in dir /tmp/jx-git-2533585150 Your branch is up to date with 'origin/main'. export APP_NAME='flash' export BRANCH_NAME='PR-302' export BUILD_NUMBER='5' export DOCKERFILE_PATH='Dockerfile' export DOCKER_REGISTRY='417755753340.dkr.ecr.ap-south-1.amazonaws.com' export DOCKER_REGISTRY_ORG='greencapitaltrade' export DOMAIN='gc-t.in' about to run: git rev-parse --abbrev-ref HEAD in dir . main export GIT_BRANCH='main' export JENKINS_X_URL='https://dashboard-jx.gc-t.in/greencapitaltrade/flash/PR-302/5' export JX_CHART_REPOSITORY='http://jenkins-x-chartmuseum.jx.svc.cluster.local:8080' export KANIKO_FLAGS='--skip-unused-stages --snapshotMode=redo' export MINK_AS='tekton-bot' version file VERSION does not exist export MINK_IMAGE='417755753340.dkr.ecr.ap-south-1.amazonaws.com/greencapitaltrade/flash:0.0.0-PR-302-5-SNAPSHOT' export NAMESPACE_SUB_DOMAIN='-jx.' export PIPELINE_KIND='pullrequest' export PUSH_CONTAINER_REGISTRY='417755753340.dkr.ecr.ap-south-1.amazonaws.com' export REPO_NAME='flash' export REPO_OWNER='greencapitaltrade' version file VERSION does not exist export VERSION='0.0.0-PR-302-5-SNAPSHOT' added variables to file: .jx/variables.sh added variables to file: .jx/variables.sh Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-build-yarn-install ➤ YN0000: Successfully set npmScopes.greencapitaltrade.npmRegistryServer to 'https://npm.pkg.github.com' ➤ YN0000: Successfully set npmScopes.greencapitaltrade.npmAuthToken to '********' ➤ YN0000: · Yarn 4.5.0 ➤ YN0000: ┌ Resolution step ➤ YN0000: └ Completed in 0s 481ms ➤ YN0000: ┌ Post-resolution validation ➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details. ➤ YN0000: └ Completed ➤ YN0000: ┌ Fetch step ➤ YN0066: │ typescript@patch:typescript@npm%3A5.9.3#optional!builtin::version=5.9.3&hash=8c6c40: Cannot apply hunk #1 ➤ YN0066: │ typescript@patch:typescript@npm%3A5.8.3#optional!builtin::version=5.8.3&hash=8c6c40: Cannot apply hunk #1 ➤ YN0000: └ Completed in 1m 5s ➤ YN0000: ┌ Link step ➤ YN0007: │ @biomejs/biome@npm:1.9.4 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.21.5 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.27.2 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.27.7 must be built because it never has been before or the last one failed ➤ YN0007: │ @pact-foundation/pact-core@npm:19.2.0 must be built because it never has been before or the last one failed ➤ YN0007: │ @scarf/scarf@npm:1.4.0 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.14.47 must be built because it never has been before or the last one failed ➤ YN0007: │ sharp@npm:0.34.5 must be built because it never has been before or the last one failed ➤ YN0007: │ esbuild@npm:0.25.10 must be built because it never has been before or the last one failed ➤ YN0007: │ @swc/core@npm:1.15.11 [36772] must be built because it never has been before or the last one failed ➤ YN0007: │ unrs-resolver@npm:1.11.1 must be built because it never has been before or the last one failed ➤ YN0007: │ protobufjs@npm:7.6.4 must be built because it never has been before or the last one failed ➤ YN0007: │ starter-free@workspace:. must be built because it never has been before or the last one failed ➤ YN0000: │ starter-free@workspace:. STDOUT Tamagui dependencies look good ✅ ➤ YN0000: │ starter-free@workspace:. STDOUT API package built ➤ YN0000: │ starter-free@workspace:. STDOUT [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D` ➤ YN0000: │ starter-free@workspace:. STDOUT built @my/config in 422 ms ➤ YN0000: │ starter-free@workspace:. STDOUT npm warn Unknown user config "unsafe-perm". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. ➤ YN0000: │ starter-free@workspace:. STDOUT [baseline-browser-mapping] The data in this module is over two months old. To ensure accurate Baseline data, please update: `npm i baseline-browser-mapping@latest -D` ➤ YN0000: │ starter-free@workspace:. STDOUT built @my/ui in 519 ms ➤ YN0000: │ starter-free@workspace:. STDOUT Done in 5s 153ms ➤ YN0000: └ Completed in 44s 997ms ➤ YN0000: · Done with warnings in 1m 51s Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-build-yarn-install-errors Showing logs for build greencapitaltrade/flash/pr-302 #5 stage from-build-pack and container step-unit-tests ! Corepack is about to download https://repo.yarnpkg.com/4.5.0/packages/yarnpkg-cli/bin/yarn.js RUN v2.1.9 /workspace/source ✓ packages/ui/src/__tests__/TeamSelector.test.tsx (10 tests) 155ms stderr | packages/ui/src/__tests__/TeamSelector.test.tsx Not implemented: navigation to another Document ✓ packages/app/features/asset/hooks/__tests__/useAssetTelemetry.test.ts (20 tests) 92ms stderr | packages/app/features/asset/screens/__tests__/reports-filters.test.tsx > ReportsScreen — Trips tab rendering (flag OFF by default) > Trips tab is visible regardless of enabled_features when flag is off React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexBasis` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexbasis` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexGrow` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexgrow` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Received `true` for a non-boolean attribute `horizontal`. If you want to write it to the DOM, pass a string instead: horizontal="true" or horizontal={value.toString()}. React does not recognize the `showsHorizontalScrollIndicator` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `showshorizontalscrollindicator` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingtop` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `showsVerticalScrollIndicator` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `showsverticalscrollindicator` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Unknown event handler property `onValueChange`. It will be ignored. React does not recognize the `flexDirection` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexdirection` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | packages/app/features/asset/screens/__tests__/reports-filters.test.tsx > ReportsScreen — v2 flag ON: filter bar, search, error, trips gating > search input filters rows by license_plate after 300ms debounce React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `$gtSm` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `$gtsm` instead. If you accidentally passed it from a parent component, remove it from the DOM element. Invalid attribute name: `$gtSm` ✓ packages/app/features/asset/screens/__tests__/reports-filters.test.tsx (18 tests) 491ms stderr | apps/next/__tests__/components/error-pages.test.tsx > 404 Not Found Page > renders 404 heading React does not recognize the `lineHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `lineheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `textAlign` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `textalign` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `maxWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `maxwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `backgroundColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `backgroundcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderRadius` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderradius` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `marginTop` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `margintop` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `alignItems` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `alignitems` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `justifyContent` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `justifycontent` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `marginBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginbottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `textTransform` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `texttransform` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `bordercolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `minWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `hoverStyle` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hoverstyle` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `minHeight` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `minheight` instead. If you accidentally passed it from a parent component, remove it from the DOM element. ❯ apps/next/__tests__/components/geofences-page.test.tsx (18 tests | 18 failed) 71ms × GeofencesPage component > renders without crashing 34ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > shows loading spinner when loading with no data 3ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > shows Zone Directory header 3ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > renders stat card labels 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > default active tab shows only enabled geofences 4ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > clicking All tab shows all geofences 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > search filters geofences by name 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > no search matches shows appropriate message 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > empty geofences shows no geofences yet message 3ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > toggle switch calls updateGeofence 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > Create Zone button navigates to /vehicles 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > export button is disabled when no geofences 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > renders map placeholder 1ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > geofence card shows type label for circle with radius 2ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > geofence card shows vehicle count 1ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > loading with existing data does not show spinner 1ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > null data renders empty state 1ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: × GeofencesPage component > alerts text shows Entry for entry-only geofence 1ms → [vitest] No "useAssetTeams" export is defined on the "app/features/asset/api/hooks" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: ❯ apps/next/__tests__/components/replay-page.test.tsx (0 test) stderr | apps/next/__tests__/components/error-pages.test.tsx > 500 Error Page > renders error heading React does not recognize the `paddingHorizontal` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddinghorizontal` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderBottomWidth` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomwidth` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `borderBottomColor` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `borderbottomcolor` instead. If you accidentally passed it from a parent component, remove it from the DOM element. stderr | apps/next/__tests__/components/error-pages.test.tsx > 403 Forbidden Page > renders 403 heading React does not recognize the `marginVertical` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `marginvertical` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `paddingBottom` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `paddingbottom` instead. If you accidentally passed it from a parent component, remove it from the DOM element. React does not recognize the `flexWrap` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `flexwrap` instead. If you accidentally passed it from a parent component, remove it from the DOM element. ❯ apps/next/__tests__/components/error-pages.test.tsx (23 tests | 2 failed) 561ms × 404 Not Found Page > has quick navigation links 31ms → expected false to be true // Object.is equality × 403 Forbidden Page > shows role subtitles 29ms → expected false to be true // Object.is equality stderr | apps/next/__tests__/components/create-team-client.test.tsx > CreateTeamPageClient > renders without crashing Invalid value for prop `icon` on