Skip to content
CI

@/CivicSignalBlog - Add ability to manage CivicSignal content #3598

Sign in to view logs

@/CivicSignalBlog - Add ability to manage CivicSignal content

@/CivicSignalBlog - Add ability to manage CivicSignal content #3598

Triggered via pull request September 25, 2024 10:11
@m453hm453h
synchronize #901
feat/civic_signal_webtools_cms
Status Cancelled
Total duration 4m 10s
Artifacts –

ci.yml

on: pull_request
Matrix: Build and Test
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
Build and Test (20.16, ubuntu-latest)
Canceling since a higher priority waiting request for 'CI @ CodeForAfrica:feat/civic_signal_webtools_cms' exists
Build and Test (20.16, ubuntu-latest)
The operation was canceled.
Build and Test (20.16, ubuntu-latest): apps/climatemappedafrica/src/components/HURUmap/Chart/index.js#L107
Unexpected console statement
Build and Test (20.16, ubuntu-latest): apps/climatemappedafrica/src/components/HURUmap/Chart/index.js#L126
Unexpected console statement
Build and Test (20.16, ubuntu-latest): apps/pesayetu/src/components/HURUmap/Chart/index.js#L107
Unexpected console statement
Build and Test (20.16, ubuntu-latest): apps/pesayetu/src/components/HURUmap/Chart/index.js#L126
Unexpected console statement
Build and Test (20.16, ubuntu-latest): apps/promisetracker/src/components/DataSource/index.js#L33
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element