Skip to content
Novus Examples
xml1 KB

Flaky Run — Timing Race, Build #104 (failing)

Build #104 of five consecutive runs of checkout.SessionTest, in which expiresSessionAfterTimeout is failing while the other five cases pass every time. The underlying cause is a 250 ms sleep racing the session expiry sweep. Read the whole family in build order to reproduce what a flake detector sees.

Preview — first 16 linesxml
<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
  <testsuite name="checkout.SessionTest" tests="6" failures="1" errors="0" skipped="0" time="3.368" timestamp="2026-08-07T09:14:22" hostname="ci-runner-04" id="104">
    <testcase classname="checkout.SessionTest" name="createsSessionForNewCart" time="0.039"/>
    <testcase classname="checkout.SessionTest" name="expiresSessionAfterTimeout" time="0.472">
      <failure message="expected session to be expired but it was still active" type="java.lang.AssertionError"><![CDATA[expected session to be expired but it was still active
	at checkout.SessionTest.expiresSessionAfterTimeout(Test.java:63)
]]></failure>
    </testcase>
    <testcase classname="checkout.SessionTest" name="restoresCartOnResume" time="0.703"/>
    <testcase classname="checkout.SessionTest" name="rotatesSessionToken" time="0.633"/>
    <testcase classname="checkout.SessionTest" name="rejectsExpiredToken" time="0.616"/>
    <testcase classname="checkout.SessionTest" name="persistsCartAcrossRestart" time="0.905"/>
  </testsuite>
</testsuites>

Specifications

Seed
61200
Build Number
104
Build Index
4
Builds In Family
5
Suite
checkout.SessionTest
Tests
6
Flaky Test
checkout.SessionTest.expiresSessionAfterTimeout
Flaky Test Outcome
fail
Other Tests Outcome
pass
Root Cause
a 250 ms sleep racing the session expiry sweep
Dialect
surefire
Line Endings
LF

Testing contract

Expected to pass
Scenario
Ingest build #104 as one sample in a five-build flake-detection window.
Expected result
expiresSessionAfterTimeout is recorded as failing in this build while the other five cases pass, so no single build on its own identifies the flake.

What is a .xml file?

XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.

How to use this file

Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.

How to use this file for testing

“Flaky Run — Timing Race, Build #104 (failing)” is a deterministic Novus Examples fixture for Error handling, Log parsing, Conversion testing. Deliberately corrupt and invalid files, clearly labelled, for testing how your tool fails.

Documented properties for this file: seed 61200 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Test and coverage reports document their totals (suites, cases, passes, failures, skips, covered lines) in the spec table. Point your CI dashboard, coverage gate, or report converter at the file and assert those counts survive; format twins carry identical numbers so a conversion can be scored exactly.

Code examples

import xml.etree.ElementTree as ET

tree = ET.parse("timing-race-build-104.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])

Generated by generation/testing.py. Free for any use, no attribution required — license.