https://bugzilla.redhat.com/show_bug.cgi?id=2296539

            Bug ID: 2296539
           Summary: Review Request: rust-hyper-timeout - Connect, read and
                    write timeout aware connector to be used with hyper
                    Client
           Product: Fedora
           Version: rawhide
          Hardware: All
                OS: Linux
            Status: NEW
         Component: Package Review
          Severity: medium
          Priority: medium
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected]
  Target Milestone: ---
    Classification: Fedora



Spec URL:
https://github.com/LecrisUT/tonic-rpmspec/raw/f7b19948b281b06bae4abaed199dfac901547333/rust-hyper-timeout/rust-hyper-timeout.spec
SRPM URL:
https://download.copr.fedorainfracloud.org/results/packit/LecrisUT-tonic-rpmspec-main/fedora-rawhide-x86_64/07718146-rust-hyper-timeout/rust-hyper-timeout-0.5.1-1.fc41.src.rpm
Description: Dependency for `tonic` -> `atuin`
Fedora Account System Username: lecris

rust2rpm.toml
```toml
[tests]
skip = [
    "tests::test_read_timeout",
]
comments = [
    "Probably failing because of DNS resolution",
]
```


-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
https://bugzilla.redhat.com/show_bug.cgi?id=2296539

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202296539%23c0

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to