search

bloom-lang / bud

Prototype Bud runtime (Bloom Under Development)
http://bloom-lang.net
Other
854 stars 60 forks source link

fixes issue #245 #247

Closed michaelficarra closed 12 years ago

michaelficarra commented 12 years ago

BudCollection#cols replaces BudCollection#schema and BudCollection#schema becomes useful as schema specification when defining new collections.

As before, I'm unable to run the tests, but this should at least get you 90% there.

neilconway commented 12 years ago

Thanks, I'll take a look.

BTW, what is the issue running the tests? They should run out of the box -- let me know if there's an issue on our end we can fix.

michaelficarra commented 12 years ago

Just wanted to note here: I haven't forgotten about getting back to you about why the test suite fails for me, I've just been busy. Short description: a lot of tests pass, a few intermittent tests fail, then all of a sudden it eats up all of my available memory (quickly!) and usually takes down the system before I can kill it. I'll post more information once I can get some time to really debug it. Worst case scenario, I can disable tests until it no longer brings the whole system down.

neilconway commented 12 years ago

Weird. The forkdeploy and threaddeploy tests might be the culprit (they spawn a lot of processes). Perhaps try disabling those, and/or running all the tests one at a time?

michaelficarra commented 12 years ago

Sure, I will try both of those approaches when I get home. I've been running the tests on a machine with 6gb of memory and at least 3gb free at all times. Do those tests intentionally use 3gb+ memory in just a few seconds? I'd be very surprised if that was expected behaviour.