Skip to content
Build

Allow spaces (and other things) as separators when parsing RFC3339 #1707

Sign in to view logs

Allow spaces (and other things) as separators when parsing RFC3339

Allow spaces (and other things) as separators when parsing RFC3339 #1707

Triggered via pull request August 1, 2024 17:31
@fasterthanlimefasterthanlime
synchronize #700
bearcove:rfc3339-is-weird
Status Failure
Total duration 14m 35s
Artifacts –

build.yaml

on: pull_request
Matrix: check-targets
Matrix: test
Type-check benchmarks
15s
Type-check benchmarks
Cross-build
1m 22s
Cross-build
Formatting
12s
Formatting
Clippy
1m 9s
Clippy
Documentation
13s
Documentation
Test (miri)
14m 19s
Test (miri)
Coverage
1m 5s
Coverage
Publish docs  /  Deploy
Publish docs / Deploy
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Coverage
ENOENT: no such file or directory, opendir '/home/runner/work/time/time/target/tests/target'
Coverage
Error: ENOENT: no such file or directory, opendir '/home/runner/work/time/time/target/tests/target'
Test (miri)
Process completed with exit code 101.