sdods report prints (missing) for the html report after a CI run

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.

Our CI job runs the suite and archives the run, someone downloads the archive and opens it locally. Locally, straight after a run, everything is there. On the downloaded copy:

text

Run 017af9c1-4b02-7d31-8e55-2a9c41d0e118  /home/tobi/dl/.sdods/runs/017af9c1-...
project demo-shop · env staging · 2021-08-02T21:14:07.882Z
18 passed  1 failed  0 flaky  0 skipped

report      path
--------    ----
html        (missing)
dashboard   (missing)
messages    /home/tobi/dl/.sdods/runs/017af9c1-.../messages.ndjson

So the summary and the ndjson survived and the two things I actually want did not. We pass --reporter-mode quiet in CI to keep the log readable. Is that dropping them?

reporting ci cli

asked by Tobi Schrader

2 answers

Accepted answer
--reporter-mode only swaps the console reporter — list by default, line for the server, dot for quiet. The HTML report, the NDJSON and the dashboard are always in the reporter list, so all three were written. Your archive step did not pick two of them up.
The usual cause is an archive pattern that matches files rather than directories, so the JSON and the ndjson come through and playwright-report/ and dashboard/ do not. Archive the run directory itself:
bash
```
tar -czf sdods-run.tgz -C .sdods/runs 017af9c1-4b02-7d31-8e55-2a9c41d0e118
```
sdods report only looks for <runDir>/playwright-report/index.html and <runDir>/dashboard/index.html on disk and prints (missing) when they are not there. It never regenerates them, so there is nothing to re-run on the downloaded copy.
answered by Reeta NandalSDODS team
Second thing that bites here even once the archive is right. --last picks the newest run directory under the artifacts root of wherever you are standing. If you unpack the archive into ~/dl and then run sdods report --last from your own checkout, it happily finds one of your own local runs and tells you the truth about that one instead.
Be explicit:
bash
```
SDODS_ARTIFACTS_DIR=/home/tobi/dl/.sdods/runs sdods report --run 017af9c1-4b02-7d31-8e55-2a9c41d0e118 --open
```
Ours printed a perfectly plausible summary of a run from the previous afternoon for about a week before anyone noticed the timestamps.
answered by Vikram Rajagopal

Know the answer?

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.

sdods report prints (missing) for the html report after a CI run

2 answers

Know the answer?

Related