Closed zenspider closed 2 years ago
@zenspider Thanks for the report! I'm actually aware of it and have been trying to triangulate the issue by "binary searching" through the commits, and then within a commit, to isolate the cause. This was needed because it only fails on the package index and is not locally reproducible, as mentioned in this issue. I had the luxury of employing this approach since I assumed nobody knew about this package yet, but I guess I was wrong 😄
Your timing couldn't be better though, because I seem to have isolated the precise change that causes this issue to manifest, and it's this one.
I am about to double check that reverting it will cause it to fail again. If it doesn't then it could be a nondeterministic error, but I have a feeling it is deterministic since the failures on individual commits at least seem to have been consistent during my testing (which is admittedly tough to say for sure since each time I change the commit it's a 24hr cycle on the package index to know whether it succeeded or not -- so there is only one data point per commit, and those have been consistent wrt success or failure and the idea there there is a single point / commit at which the transition happens).
I'm sure you find this narrative as riveting as I do, but, I'm mainly just documenting it here since you've provided a convenient place for it 😸
This doesn't appear to be an issue anymore since I added the workaround. I haven't seen any updates on the related Racket ticket, so I'm going to consider this workaround permanent.
All the above links are still broken...
@zenspider The package was renamed to qi
, so the links above are out of date. Try the new links in the README? E.g. https://docs.racket-lang.org/qi/index.html
In your readme, and via https://pkgs.racket-lang.org/package/ionic
https://pkg-build.racket-lang.org/#f shows the build failed during docs
https://pkg-build.racket-lang.org/server/built/fail/ionic.txt for details: