<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Guides on JVQ.net</title>
    <link>https://jvq.net/tags/guides/</link>
    <description>Recent content in Guides on JVQ.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jvq.net/tags/guides/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Set Up jvq Flaky With GitHub Actions and Retries in pytest and Go</title>
      <link>https://jvq.net/how-to-set-up-jvq-flaky-with-github-actions-and-retries-in-pytest-and-go/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://jvq.net/how-to-set-up-jvq-flaky-with-github-actions-and-retries-in-pytest-and-go/</guid>
      <description>&lt;p&gt;&lt;code&gt;jvq flaky&lt;/code&gt; needs two things from your CI: test results it can read, and a history file that survives from one run to the next. Everything else is optional. These are the setups we&amp;rsquo;d start with, each one run for real before it went on this page.&lt;/p&gt;&#xA;&lt;p&gt;They were tested with the released 0.7.0 binary on a small demo project: a pytest suite of four tests, one of which fails about one try in three, and a Go package with the same kind of test. That test fails at random, the way a test does that waits on a slow service. The outputs below are copied from those runs, and the script that made them is in &lt;a href=&#34;https://github.com/just-very-quickly/jvq/tree/main/test/results/case-studies/flaky/recipes&#34;&gt;test/results/case-studies/flaky/recipes&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
