public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Igor Gnatenko <ignatenkobrain@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/rust-dtoa] epel10: Run tests in infrastructure
Date: Mon, 15 Jun 2026 14:12:46 GMT	[thread overview]
Message-ID: <178153276609.1.9500686663436077360.rpms-rust-dtoa-fc6e27dd5a8e@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/rust-dtoa
            Branch : epel10
            Commit : fc6e27dd5a8e865c1a7abe6263c21a808f0bf234
            Author : Igor Gnatenko <ignatenkobrain@fedoraproject.org>
            Date   : 2019-02-10T17:32:52+01:00
            Stats  : +26/-4 in 4 file(s)
            URL    : https://src.fedoraproject.org/rpms/rust-dtoa/c/fc6e27dd5a8e865c1a7abe6263c21a808f0bf234?branch=epel10

            Log:
            Run tests in infrastructure

Signed-off-by: Igor Gnatenko <ignatenkobrain@fedoraproject.org>

---
diff --git a/rust-dtoa.spec b/rust-dtoa.spec
index 34b35c8..8b599bd 100644
--- a/rust-dtoa.spec
+++ b/rust-dtoa.spec
@@ -1,18 +1,18 @@
 # Generated by rust2rpm
-%bcond_without check
+%bcond_with check
 %global debug_package %{nil}
 
 %global crate dtoa
 
 Name:           rust-%{crate}
 Version:        0.4.3
-Release:        4%{?dist}
+Release:        5%{?dist}
 Summary:        Fast functions for printing floating-point primitives to an io::Write
 
 # Upstream license specification: MIT/Apache-2.0
 License:        MIT or ASL 2.0
 URL:            https://crates.io/crates/dtoa
-Source0:        https://crates.io/api/v1/crates/%{crate}/%{version}/download#/%{crate}-%{version}.crate
+Source:         %{crates_source}
 
 ExclusiveArch:  %{rust_arches}
 
@@ -50,7 +50,7 @@ which use "default" feature of "%{crate}" crate.
 %ghost %{cargo_registry}/%{crate}-%{version}/Cargo.toml
 
 %prep
-%autosetup -n %{crate}-%{version} -p1
+%autosetup -n %{crate}-%{version_no_tilde} -p1
 %cargo_prep
 
 %build
@@ -65,6 +65,9 @@ which use "default" feature of "%{crate}" crate.
 %endif
 
 %changelog
+* Sun Feb 10 2019 Igor Gnatenko <ignatenkobrain@fedoraproject.org> - 0.4.3-5
+- Run tests in infrastructure
+
 * Sat Feb 02 2019 Fedora Release Engineering <releng@fedoraproject.org> - 0.4.3-4
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
 

diff --git a/tests/.fmf/version b/tests/.fmf/version
new file mode 100644
index 0000000..d00491f
--- /dev/null
+++ b/tests/.fmf/version
@@ -0,0 +1 @@
+1

diff --git a/tests/provision.fmf b/tests/provision.fmf
new file mode 100644
index 0000000..503a97c
--- /dev/null
+++ b/tests/provision.fmf
@@ -0,0 +1,5 @@
+---
+standard-inventory-qcow2:
+  qemu:
+    # `cargo test` usually eats more than 1G.
+    m: 4G

diff --git a/tests/tests.yml b/tests/tests.yml
new file mode 100644
index 0000000..488256f
--- /dev/null
+++ b/tests/tests.yml
@@ -0,0 +1,13 @@
+---
+- hosts: localhost
+  roles:
+  - role: standard-test-basic
+    tags:
+    - classic
+    repositories:
+    - repo: "https://src.fedoraproject.org/tests/rust.git"
+      dest: rust
+    tests:
+    - rust/cargo-test
+    environment:
+      pkg: rust-dtoa

                 reply	other threads:[~2026-06-15 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178153276609.1.9500686663436077360.rpms-rust-dtoa-fc6e27dd5a8e@fedoraproject.org \
    --to=ignatenkobrain@fedoraproject.org \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox