Re: [racket-users] Module not updating on the package server?

2019-05-01 Thread David Storrs
On Wed, May 1, 2019 at 4:53 PM Greg Hendershott wrote: > > Sure. But I'm not looking for the package server to do tests for me, I'm > > looking for it to not discourage people from using my package because > > there's a red 'fails' next to the name when there shouldn't be. > Especially > > when

Re: [racket-users] Module not updating on the package server?

2019-05-01 Thread Matthew Butterick
> On Apr 30, 2019, at 12:18 PM, David Storrs 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 > sec

Re: [racket-users] Module not updating on the package server?

2019-05-01 Thread Greg Hendershott
> Sure. But I'm not looking for the package server to do tests for me, I'm > looking for it to not discourage people from using my package because > there's a red 'fails' next to the name when there shouldn't be. Especially > when it hasn't tried to rebuild the package for two weeks. Probably th

Re: [racket-users] Module not updating on the package server?

2019-05-01 Thread David Storrs
Sure. But I'm not looking for the package server to do tests for me, I'm looking for it to not discourage people from using my package because there's a red 'fails' next to the name when there shouldn't be. Especially when it hasn't tried to rebuild the package for two weeks. On Tue, Apr 30, 201

Re: [racket-users] Module not updating on the package server?

2019-04-30 Thread Greg Hendershott
Not to speak for Jay, but I think the package server's primary role is to be a catalog server -- "given a package name, I'd like to cash that in for some code". For projects hosted at Git{Hub Lab}, that means the package server needs to know the project URL and the commit digest. It refreshes the l

Re: [racket-users] Module not updating on the package server?

2019-04-30 Thread David Storrs
Huh. Okay, I guess I misunderstood. Thanks for clarifying. On Tue, Apr 30, 2019 at 4:29 PM Jay McCarthy wrote: > Rescanning never did that. It just re-downloads from Github (or > wherever) and updates the record that the build server queries > nightly. > > -- > Jay McCarthy > Associate Profess

Re: [racket-users] Module not updating on the package server?

2019-04-30 Thread Jay McCarthy
Rescanning never did that. It just re-downloads from Github (or wherever) and updates the record that the build server queries nightly. -- Jay McCarthy Associate Professor @ CS @ UMass Lowell http://jeapostrophe.github.io Vincit qui se vincit. On Tue, Apr 30, 2019 at 3:59 PM David Storrs wrote:

Re: [racket-users] Module not updating on the package server?

2019-04-30 Thread David Storrs
On Tue, Apr 30, 2019 at 3:23 PM Sam Tobin-Hochstadt wrote: > The pkg-build server runs only once a day, so it will pick up your > changes in the next run. > ?? When I've done "rescan all my packages" in the past it's rebuilt the package. Did something change or am I just clueless? > Sam > >

Re: [racket-users] Module not updating on the package server?

2019-04-30 Thread Sam Tobin-Hochstadt
The pkg-build server runs only once a day, so it will pick up your changes in the next run. Sam On Tue, Apr 30, 2019 at 3:16 PM David Storrs wrote: > > Hi all, > > 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,

[racket-users] Module not updating on the package server?

2019-04-30 Thread David Storrs
Hi all, 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 ther