pkg-build.racket-lang.org

[Neil Van Dyke]

When will "https://pkg-build.racket-lang.org/" next be updated?

And how frequently is it updated after that?

(I just 'uploaded' my first 3 packages: progedit, overeasy, mcfly. I
need to know whether the way they're packaged works fully with the
package server setup, before I manually convert ~20 more packages on
Sunday afternoon.)

[Alexis King]

Builds are run daily for all packages that have been updated since the
previous build (it would be nice if any updates immediately kicked off a
build, but right now they just get run at 6:00 EST(?) every day). If all
goes well, the pkg-build service should pick up your changes in a few
hours.

> --
> You received this message because you are subscribed to the Google Groups "Racket Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to racket-dev+...@googlegroups.com.
> To post to this group, send email to racke...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/56C97385.1060001%40neilvandyke.org.
> For more options, visit https://groups.google.com/d/optout.

[Matthew Flatt]

Yes, except that it's currently 6:00am MT.

It looks like there was an issue with the "mcfly" package registration
that is now fixed, so I started another run. It will probably complete
in 15-30 minutes.

> https://groups.google.com/d/msgid/racket-dev/1B2B1C59-AD1C-4898-A08D-B6E5379FE3
> E1%40gmail.com.

[Robby Findler]

I've started another build for the pkgs that build against the
snapshots, too. When it is done, the results will be here:

http://plt.eecs.northwestern.edu/pkg-build/

Robby

> To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/56c9c419.8796420a.4a81c.09a6SMTPIN_ADDED_MISSING%40gmr-mx.google.com.

[Neil Van Dyke]

Matthew Flatt wrote on 02/21/2016 09:05 AM:
> It looks like there was an issue with the "mcfly" package registration
> that is now fixed, so I started another run. It will probably complete
> in 15-30 minutes.
>

Thanks, Matthew. (Possible cause: Sat night, when I first went to add
the first package, "mcfly", I just typed the URL in the "upload" form of
the Web interface, and dismissed the dialog. I think this was what
created a catalog entry with no name that I couldn't edit or delete. I
again tried to add "mcfly" with the "upload" form, and this time I added
both the URL and the name to the form. This left me with 2 catalog
entries with the same URL: "mcfly" and a blank name. I'm just guessing
that the no-name one sharing a URL with "mcfly" caused "mcfly" to
disappear from the catalog, while the other two packages I added,
"overeasy" and "progedit", did not disappear.)

Neil V.

[Neil Van Dyke]

Is there a way that I can cause another build to happen immediately (to
see how it handles my "csv-reading" package)?
*Or* could someone please confirm that the below way my unit tests work
should be OK with the build servers?

* My packages use `(module+ test (require overeasy) ...)` in the main
implementation file for all the tests.
* Any test that fails raises an `exn:fail?` (unless test was annotated
in code as expected to fail).
* Normally the tests send verbose logging to the Racket logger as
`debug@overeasy`. Examples:
overeasy: Start Test Section [comment-chars]
overeasy: Test Passed [comment-chars
read-str-without-pound-as-comment-char]
* The tests don't do any logger output above `debug` level, unless tests
fail.

Thanks,
Neil V.

[Matthew Flatt]

At Sun, 21 Feb 2016 17:02:17 -0500, Neil Van Dyke wrote:
> Is there a way that I can cause another build to happen immediately (to
> see how it handles my "csv-reading" package)?

I can run the package-build service at about 7:30 MST. (The machine is
about to start a daily task that works best without other builds
running.)

> *Or* could someone please confirm that the below way my unit tests work
> should be OK with the build servers?
>
> * My packages use `(module+ test (require overeasy) ...)` in the main
> implementation file for all the tests.
> * Any test that fails raises an `exn:fail?` (unless test was annotated
> in code as expected to fail).
> * Normally the tests send verbose logging to the Racket logger as
> `debug@overeasy`. Examples:
> overeasy: Start Test Section [comment-chars]
> overeasy: Test Passed [comment-chars
> read-str-without-pound-as-comment-char]
> * The tests don't do any logger output above `debug` level, unless tests
> fail.

The package-build service runs tests as

raco test --drdr --package <package-name>

and defines success as a 0 status code. The details above look
consistent with that.