> On Apr 30, 2019, at 12:18 PM, David Storrs <david.sto...@gmail.com> wrote: > > I just pushed an update to the test-more module. On the package server it > was marked as 'New!' and was up to the latest commit, but the build status > was 'fails'. The compilation report is from April 18. I thought I'd take a > second chance, so I pushed another update, but no joy. Is there any way for > me to make this update or could one of our wonderful maintainers kick the > server for me? >
Patience is a virtue. Across the months and years I have noticed increasingly longer lag times (now measured in hours) between when the daily build occurs for a package and when the build report has propagated to the `pkg-build` server & documentation has propagated to the `docs` server. (Even though, as others have pointed out, the record on `pkgs` itself usually notices commits within a few minutes.) I don't know for sure, but I take this to be a consequence of the overall daily build taking longer than it used to, because there are more packages. Which is a good thing. I don't know if `pkgs.racket-lang.org <http://pkgs.racket-lang.org/>` was meant to be a package-discovery tool for end users. I imagine not, because we have the beautiful Scribble documentation system, which is where the worthwhile user-facing information about a package lives. Whereas the package server has records largely of interest to package developers and other machines. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
