Ok it turns out I had done (syntax/loc stx #’template) instead of (syntax/loc stx template) and somehow that seems to have triggered some kind of infinite recursive loop or something.
But I fixed it and got another error that makes no sense at all. It seems like somehow a struct constructor is returning #f. raco setup: 0 making: <pkgs>/racket-test/tests/future struct-type/sc: broke its contract promised: static-contract? produced: #f in: the range of (-> any/c static-contract?) contract from: <pkgs>/typed-racket-lib/typed-racket/static-contracts/combinators/struct.rkt blaming: <pkgs>/typed-racket-lib/typed-racket/static-contracts/combinators/struct.rkt (assuming the contract is correct) at: <pkgs>/typed-racket-lib/typed-racket/static-contracts/combinators/struct.rkt:19.5 (lines 1217-1227 of https://travis-ci.org/AlexKnauth/racket/jobs/30418536) Where struct-type/sc is defined like this in <pkgs>/typed-racket-lib/typed-racket/static-contracts/combinators/struct.rkt: (struct struct-type/sc combinator () #:transparent #:property prop:combinator-name "struct-type/sc" #:methods gen:sc [(define (sc-map v f) (match v [(struct-type/sc args) (struct-type/sc (map (λ (a) (f a 'covariant)) args))])) (define (sc-traverse v f) (match v [(struct-type/sc args) (for-each (λ (a) (f a 'covariant)) args) (void)])) (define (sc->contract v f) (match v [(struct-type/sc args) #`(struct-type/c #f)])) (define (sc->constraints v f) (match v [(struct-type/sc args) (simple-contract-restrict 'chaperone)]))]) I have no idea what to do. On Jul 20, 2014, at 2:15 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: > "Killed" means that the OS terminated the `racket/racket3m` process > from the outside. For example, the process may have exceeded a > memory-use limit. > > At Sat, 19 Jul 2014 20:25:24 -0400, "Alexander D. Knauth" wrote: >> I made a fork of the racket repo and committed some changes in a topic >> branch, >> but I got this: >> make[8]: Leaving directory >> `/home/travis/build/AlexKnauth/racket/racket/src/build' >> make[7]: Leaving directory >> `/home/travis/build/AlexKnauth/racket/racket/src/build' >> make[6]: Leaving directory >> `/home/travis/build/AlexKnauth/racket/racket/src/build' >> racket/racket3m -X "/home/travis/build/AlexKnauth/racket/racket/collects" -G >> "/home/travis/build/AlexKnauth/racket/racket/etc" -G >> /home/travis/build/AlexKnauth/racket/build/config -N "raco" -l- setup >> --no-user -j 2 >> raco setup: bootstrapping from source... >> Killed >> make[5]: *** [install-3m] Error 137 >> make[5]: Leaving directory >> `/home/travis/build/AlexKnauth/racket/racket/src/build' >> make[4]: *** [install] Error 2 >> make[4]: Leaving directory >> `/home/travis/build/AlexKnauth/racket/racket/src/build' >> make[3]: *** [base] Error 2 >> make[3]: Leaving directory `/home/travis/build/AlexKnauth/racket' >> make[2]: *** [plain-in-place] Error 2 >> make[2]: Leaving directory `/home/travis/build/AlexKnauth/racket' >> make[1]: *** [cpus-in-place] Error 2 >> make[1]: Leaving directory `/home/travis/build/AlexKnauth/racket' >> make: *** [in-place] Error 2 >> The command "make CPUS="2" PKGS="racket-test db-test unstable-flonum-lib >> net-test"" exited with 2. >> (lines 812-830 of https://travis-ci.org/AlexKnauth/racket/jobs/30368892) >> >> What does this mean? >> >> What does the “Killed” mean? >> And what is error 137? >> >> _________________________ >> Racket Developers list: >> http://lists.racket-lang.org/dev
_________________________ Racket Developers list: http://lists.racket-lang.org/dev