Hi, Christopher D. Malon wrote: > 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?
Currently, the smokeserver does not run smartlinks.pl etc., but redirects to tests.pugscode.org via .htaccess: Redirect /iblech/stuff/pugs-smokes/t http://tests.pugscode.org/t Redirect /iblech/stuff/pugs-smokes/ext http://tests.pugscode.org/ext (tests.pugscode.org used to be an alias to something under http://feather.perl6.nl/.) This way the smokeserver doesn't need to do anything except storing the .html of smokes; especially it doesn't have to be updated WRT new synopses/tests/smartlinks.pl. Accordingly, ... > 3. What is the full path to smartlinks.pl on the smoke server? ...there is none. > 5. Will a commit that changes smokeserv-server.pl be > picked up by the smoke server right away? No; currently, you'll have to ping me (best by mail). (Note that testing the smokeserver locally shouldn't be hard, as it doesn't require setting up a proper database etc. Copying smokeserv-serv.pl somewhere under cgi-bin/ and adjusting the paths should suffice.) > I might down the whole smoke system with my commit. > Anyone willing to debug with me when I do? I am, of course. :) --Ingo
