[NEB-92] Dashboard: Add Nebula Analytics dashboard (#6198) #18889
graphite-app[bot]CI.yml
on: push
optimize_ci
2s
Build Packages
54s
Lint Packages
2m 11s
Unit Tests
59s
Size
0s
Matrix: E2E Tests
Annotations
40 warnings
|
optimize_ci
Request body: {"token":"***","caller":{"name":"graphite-ci-action","version":"0.0.0"},"context":{"kind":"GITHUB_ACTIONS","repository":{"owner":"***-dev","name":"js"},"sha":"815b9b1ce109e466a8bf5f62b5acd2e0517fe4a9","ref":"refs/heads/main","head_ref":"","run":{"workflow":"CI","job":"optimize_ci","run":13249520635}}}
|
|
optimize_ci
Response status: 400
|
|
optimize_ci
***-dev/js/undefined
|
|
optimize_ci
Response returned a non-200 status. Skipping Graphite checks.
|
|
Build Packages
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (npm, esbuild)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (npm, esbuild)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
Unit Tests
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
Unit Tests
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (npm, vite)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (npm, vite)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (npm, webpack)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (bun, esbuild)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (npm, webpack)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (bun, esbuild)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (pnpm, webpack)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (pnpm, webpack)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (bun, vite)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (bun, vite)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (pnpm, vite)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (pnpm, vite)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (bun, webpack)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (bun, webpack)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (pnpm, esbuild)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (pnpm, esbuild)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (yarn, vite)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (yarn, vite)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (yarn, webpack)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (yarn, webpack)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
E2E Tests (yarn, esbuild)
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
E2E Tests (yarn, esbuild)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
Lint Packages
Cache not found for keys: node-cache-Linux-x64-pnpm-20f546f6aea7d223aca453400bbb92bc3c8251a7a87d852ee7744bae98b47135
|
|
Lint Packages
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L163
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L170
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/airdrop/TransactionResults.tsx#L177
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L161
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L168
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/TransactionResults.tsx#L175
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
Lint Packages:
apps/playground-web/src/components/engine/minting/erc1155-mint-to.tsx#L267
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|