Agentz++ writes, in a Pugs blog comment:
if someone can offer regular smoke results (i.e. the tests.yml
generated by `make smoke'), we can render the Synopses on feather
with smoke results as well
The obvious way to get this to happen, for all runtimes, is to
integrate the
synopsis-with-smoke production with the existing smoke server
infrastructure.
I've started hacking this in, but have some concerns.
A few are mainly directed to iblech++.
1. Multi-versioning the tests: The inlined tests need to match
the revision at which the smoke was produced. Is it okay to have
the smoke server check out the relevant revision of the pugs/t directory
each time a smoke of a new revision is submitted, or is that too
expensive?
2. Should the synopses just be provided by a third "ยป" column on
the existing smoke.pugscode.org index page, or should the
synopses-with-smoke have a dedicated index page organized
somewhat differently?
3. What is the full path to smartlinks.pl on the smoke server?
4. Is the smoke server getting refreshed copies of the
synopses somewhere already?
5. Will a commit that changes smokeserv-server.pl be
picked up by the smoke server right away?
I might down the whole smoke system with my commit.
Anyone willing to debug with me when I do?
In summary, the basic pattern would be:
(a) smokeserv-client sends both .html and .yml of smoke
(b) If smokeserv-server gets .yml, it checks out the t/ directory for
that revision, and
(c) smokeserv-server runs smartlinks.pl on the .yml with that t/
directory and indexes it.
Christopher
