WASM build running hadrian in the browser #45
ci.yml
on: pull_request
Docker Build
1m 8s
Backend
6m 57s
WASM Build
5m 34s
Security Audit (cargo-audit)
3m 0s
Dependency Check (cargo-deny)
3m 45s
Frontend
9m 42s
Security Audit (Frontend)
18s
Documentation
2m 18s
OpenAPI Conformance
13s
Matrix: cross-build
Matrix: feature-check
E2E Tests
0s
Annotations
9 errors and 1 warning
|
Security Audit (Frontend)
Process completed with exit code 1.
|
|
Docker Build
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c cargo build --release && rm -rf src" did not complete successfully: exit code: 101
|
|
Feature Check (tiny)
Process completed with exit code 101.
|
|
Feature Check (minimal)
Process completed with exit code 101.
|
|
Feature Check (standard)
Process completed with exit code 101.
|
|
Feature Check (full)
Process completed with exit code 101.
|
|
Backend
Process completed with exit code 101.
|
|
Feature Check (headless)
Process completed with exit code 101.
|
|
Frontend
Process completed with exit code 1.
|
|
Documentation:
docs/app/(home)/page.tsx#L228
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
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
ScriptSmith~hadrian~V3LWBI.dockerbuild
|
71 KB |
sha256:10a90c4d03ac98f4be4db25a65e235d4d239aa2ce96462beb8990dd862421924
|
|
|
openapi-conformance-report
|
3.72 KB |
sha256:05d90e4f53fc02c5ff83b5a6ac867f7b4fdf29f3bdcd77497b2536e088c196f0
|
|