Skip to content

Flaky test caused by resource fetching #446

@joepio

Description

@joepio

E.g. here

 fetching body of https://atomicdata.dev/properties/name
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: AtomicError { message: "Failed getting property https://atomicdata.dev/properties/name. Error when fetching https://atomicdata.dev/properties/name : https://atomicdata.dev/properties/name: Connection Failed: tls connection init failed: Resource temporarily unavailable (os error 11)", error_type: OtherError }', lib/src/parse.rs:274:59
failures:
    parse::test::parse_nested_resource_map_roundtrip

For some reason the default store wasn't loaded here. I think it's a good idea to do this by default when initializing a Store. Or maybe use a test helper function that always does this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions