deploy previews not working

[thescientist13]

At least for runtime-keys repo, we've noticed that the Deno based deploy preview GitHub Action is failing with a bit of cryptic error

• Draft Technical Report runtime-keys#30
• https://github.com/WinterTC55/runtime-keys/actions/runs/23953977627/job/69867920069?pr=30

Run mkdir -p out
  mkdir -p out
  curl --retry 2 --fail https://api.csswg.org/bikeshed/ --output out/index.html --header "Accept: text/plain, text/html" -F die-on=fatal -F file=@"index.bs"
  shell: /usr/bin/bash -e {0}
curl: (26) Failed to open/read local data from file/application
Error: Process completed with exit code 26.

---

Is there anyone that can help us with debugging Deno hosting / builds? Will this potentially be happening with other WinterTC55 repos / deploy previews and so we would need them all fixed?

[andreubotella]

This particular error has nothing to do with Deno Deploy. That particular workflow first builds the spec/TR locally, and then uses deployctl to deploy a static server to serve the build result. This error happens in the build stage.

For Runtime Keys in particular, the reason the build fails in WinterTC/runtime-keys#30 is because that PR changes the spec from Bikeshed to ecmarkup. The build expects the input to be index.bs, rather than spec.html; and even if it'd found the file, the build would've failed anyway because the input isn't Bikeshed. I've commented with how to fix the build.

However, as of a few months ago apparently, that same workflow, which did use to work in e.g. the minimum common API, no longer works. This is because the build step sent the Bikeshed input to a spec build server hosted by the CSS Working Group, which is no longer working. For Bikeshed specs, we could do the build locally in CI, but there's an alternative build server hosted by the W3C (https://www.w3.org/publications/spec-generator/) which we could use instead. I'll open PRs to the specs to fix the workflow to use that.