Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
New pool of agents. The first thing the job does is a preflight:
sdods browsers list -p demo-shopSome browsers are not installed.
Run `sdods browsers install --with-deps`.Exits 1. I can obviously run the suggested command, but adding a browser download to every job feels wrong when the agents are supposed to be identical. What do people do?
Accepted answer
Run the install once and cache it, rather than either downloading every time or pretending the agents are prepared.
sdods browsers install --with-deps--with-deps also pulls the system libraries the engines need, which is the part that bites on a minimal agent — the browser downloads fine and then fails to start with a missing shared library.
Cache the browser directory keyed on the engine version, and keep your browsers list preflight: it exits 1 when anything is missing, so a cache that silently went stale fails in a step called "preflight" instead of halfway through the suite.
If you control the agent image, bake the browsers into it and drop the install step entirely. Then browsers list becomes an assertion about the image rather than a step that does work, and a bad image is caught in seconds.
Either way, only install what the project declares — -p <slug> limits the list to that project's browsers, so a chromium-only project does not pay for webkit.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.