#techempower-fwbm

So if someone has know-how in that area feel free to attack those PRs

link one?

gh#1476 is a replacement for

Update to go: Use interpolateParams=true for MySQL, Closes #1353 as replacement: https://github.com/TechEmpower/FrameworkBenchma...

gh#1164

Go: Load balance between multiple connection pools: https://github.com/TechEmpower/FrameworkBenchma...

ugh

Then there’s discussion on gh#1472

start distinct Go process per 2 (virtual) cores.: https://github.com/TechEmpower/FrameworkBenchma...

I’m a noob with Go, so I’m staying out of it

same

I guess I figured (I think) methane knows what they're talking about, so I was just going to with what they said because I have no idea.. haha

hamiltont: thanks, i'll try that out.

methane usually knows what's going on in there

I removed the extra } on scruffy, but now I'm getting elasticsearch errors :(

LadyMozzarella: can you give a pointer to the change?

I'm going to set up vagrant again and re run it in case of fluke - I will get back to you on what happens :)

-bash: line 7: /opt/elasticsearch/elasticsearch: No such file or directory

is what I was getting

yes, that should only occur on CI and should be harmless.

Okay. Well I am vagranting up again.. so it may take a while, but I also pushed so that Travis can test it out... probably faster than me. So, I'm hoping that it all just works.

markoa: quick request fr the future - if the PR doesn’t yet pass travis on your own queue, try to avoid leaving the PR open while you push commits. Each new push on an open PR triggers a build on our travis queue

Hence the list here is saturated with “New test implementation” pushes - https://travis-ci.org/TechEmpower/FrameworkBenc...

Not a huge deal, but something to keep in mind

ok. i'll do that.

thanks

I have a dream of green dots as far as the eye can see, where red dots stand out and regressions are never missed

TE-msmith: other words, yesod is broken in master, not in the “apt-get upgrade” pull request

There was a regression somewhere along the way

yesod always breaks

because dependency managers which allow version ranges are broken by design

Yea, seems like nothin changed in our codebase so it’s something external

I'll see if steve can get them changed up to concrete versions

anyways, good to merge gh#1468

Do not apt-get upgrade: https://github.com/TechEmpower/FrameworkBenchma...

Whch will hopefully unblock gh#1354

remove need for sudo in setup.sh; and update ringojs runtime: https://github.com/TechEmpower/FrameworkBenchma...

[FrameworkBenchmarks] hamiltont pushed 2 new commits to master: http://git.io/veqVK

FrameworkBenchmarks/master b7688aa Hamilton Turner: Do not apt-get upgrade...

FrameworkBenchmarks/master bfd8af9 Hamilton Turner: Merge pull request #1468 from hamiltont/remove-apt-update...

[FrameworkBenchmarks] methane opened pull request #1483: go: Fix Content-Type (master...go-fix-content-type) http://git.io/veq98

hamiltont: steve says that yesod is JUST broken with mongodb

can you confirm?

can’t. My vagrant matches this travis run, where compilation fails - https://travis-ci.org/TechEmpower/FrameworkBenc...

Oddly, the latest travis run passes yesod fine - see https://travis-ci.org/TechEmpower/FrameworkBenc...

I can’t get a pass result at all in vagrant

hmm, very odd

regardless of memory size, master, etc

we haven't been testing with vagrant

Confusing

ya

sure. I don’t have a raw machine sitting around right now

you got a log where it fails?

i can get one, give me a bit

k thanks

[FrameworkBenchmarks] LadyMozzarella opened pull request #1484: Fix Scruffy errors from bad merge conflict resolution, Resolves #1481 (master...fix-merge-type-scala-scruffy) http://git.io/veqhr

TE-msmith: out.txt at http://sprunge.us/aUBY , err.txt at http://sprunge.us/KaBI , stdout at http://sprunge.us/ACCe . Used master branch, commit bfd8af990b59889c61de3dc8063560275b0b119d

thanks

xt http://blog.rust-lang.org/2015/04/03/Rust-1.0-b...

[FrameworkBenchmarks] LadyMozzarella pushed 2 new commits to master: http://git.io/vemT4

FrameworkBenchmarks/master 98730b4 INADA Naoki: go: Fix Content-Type

FrameworkBenchmarks/master 941f40c Brittany Mazza: Merge pull request #1483 from methane/go-fix-content-type...

[FrameworkBenchmarks] LadyMozzarella opened pull request #1485: Check header responses last, Make case insensitive, Closes #1475 as replacement (master...clean-up-header-check) http://git.io/vem2h

[FrameworkBenchmarks] zane-techempower opened pull request #1486: Add Golang Goji (#1452) (master...golang-goji) http://git.io/veYft

A Raspberry Pi 2B just arrived for testing.

hamiltont: As you would expect, we're going to thank you in the Round 10 blog entry. What should we link to? https://github.com/hamiltont ?

oh cool - that’s good

never did finish setting up my public blog :-P

[FrameworkBenchmarks] bhauer pushed 1 new commit to master: http://git.io/veOkL

FrameworkBenchmarks/master 8bc496b Brian Hauer: Corrected third clause to remove unwanted "of the"

ETA for public Round 10: ~April 7

Cool

OMG Milestone for windows - love it

so…most of the remaining issues are enhancements or new frameworks

very few bugs left

Woo. We're making progress!

definitely

I think there are only 43 actual bugs in the issues

Oh, can you search for that?

I tried label:"Bug: "

but it only does exact matches

I just look at the total counts on each bug label and add them up: https://github.com/TechEmpower/FrameworkBenchma...

haha

I was hoping we'd be able to filter just bug, but apparently that doesn't work.

Ha, I didn’t even think about adding them manually. Silly me - too much programming

Just got defeated when the filter didn’t work :-P

I understand completely