[docs, MG_Test] (P7): the Ph / P3b-P4b / P7 program plan, and the pull flavour builds its tests again

Plan for driving the roadmap to P7 close-out, from a per-item audit of the three
rows against a96875bf (19 reader groups, two refuters per done/obsolete verdict,
one completeness critic): what is landed, what is declined and why, what remains
with file anchors, five waves, the P7 subsystem denominator for the 40%
re-baseline checkpoint, and eleven integrator decisions (ID-P7-1..11).

The three findings the roadmap text did not carry: Magma has zero two-process
integration coverage (every split arm hardcodes DirectGLES), the 184-symbol
ratchet has no instrument, and the device DirectVulkan divergence was never
diagnosed (the lockstep control was never run under golden).

MG_Test/Util/PipeStatsTest.cpp: the pull flavour (MOBILEGL_PIPE_PUSH=OFF) did not
compile since the P6 wrap-up - the window-arithmetic case used the push-only
PipeStats::Gauge API unguarded. CI's pull control builds with
MOBILEGL_BUILD_TEST=OFF and never saw it. The gauge lines are now #if
MOBILEGL_PIPE_PUSH; the case name stays registered in both flavours for G2/G14.
This commit is contained in:
2026-09-22 13:03:20 -04:00
parent b95f5f1a20
commit e8b2c4bd05
3 changed files with 173 additions and 0 deletions
+6
View File
@@ -134,13 +134,19 @@ namespace {
PS::Init();
for (Uint32 i = 0; i < 5; ++i) {
#if MOBILEGL_PIPE_PUSH
PS::PublishGauge(PS::Gauge::ServerWaits, static_cast<Uint64>(100 * (i + 1)));
#endif
PS::OnPresent();
}
EXPECT_EQ(PS::FrameCount(), 5u);
#if MOBILEGL_PIPE_PUSH
// The gauge is a RUN TOTAL: publishing five increasing values leaves the last one,
// never their sum. This is the mistake the report's first aggregation script made.
// Gauges are push-only (gate G1, see PipeStats.h); the pull flavour keeps the case
// registered for name parity and asserts only the window arithmetic above.
EXPECT_EQ(PS::GaugeValue(PS::Gauge::ServerWaits), 500u);
#endif
MobileGL::MG_Config::Features.PipeStatsPeriod = saved;
PS::Init();