letsencrypt / boulder

63%

master: 66%

LAST BUILD ON BRANCH test-cpu-multiva-test-flake-fix-2

branch: test-cpu-multiva-test-flake-fix-2

CHANGE BRANCH

x

Reset

• test-cpu-multiva-test-flake-fix-2
• certificate_not_null_travis
• master
• test-vendorvendorvendor2
• test-integration-quiet
• staging
• test-fix-go-generate
• test-docker-maria101
• test-godep-simpler
• release
• test-goveralls
• test-simple-testing
• test-va-tests
• test-update-certbot-tests
• test-one-six
• test-tag
• test-cpu-idn-psl
• test-cpu-missing-scts-reward-if-found
• test-improvements
• test-expiration-mailer-fix
• test-https-confuse
• test-ewf
• test-fancy-errors
• test-gorp-2
• test-gorp-22
• test-rm-amqp
• test-race-speed
• test-cpu-godeps-whyyyyy
• test-multi-va
• test-bump-version
• test-godep-restore-delete
• test-godep-fixup
• test-sa-parallelism
• test-less-ports
• test-travis-docker-pull
• test-codeowners
• test-clearer
• test-v2-both-auto
• test-parallel
• test-embedscts
• HEAD
• test-update-grpc-stuff
• test-cpu-go-1.11
• test-travis-fold
• test-cpu-rm-old-v2-keyrollover
• test-broken-branch
• test-cpu-flake-chase-1
• test-cpu-flake-chase-2
• test-cpu-flake-chase-3
• test-cpu-flake-chase-4
• test-cpu-flake-chase-5
• test-cpu-flake-chase-7
• test-cpu-flake-chase-6
• test-cpu-flake-chase-9
• test-cpu-flake-chase-8
• test-cpu-flake-chase-10
• test-cpu-fix-ra-va-flake-1
• test-cpu-fix-ra-va-flake-2
• test-cpu-fix-ra-va-flake-3
• test-cpu-fix-ra-va-flake-4
• test-cpu-fix-ra-va-flake-5
• test-cpu-fix-ra-va-flake-6
• test-cpu-fix-ra-va-flake-7
• test-cpu-fix-ra-va-flake-8
• test-cpu-multiva-test-flake-1
• test-cpu-multiva-test-flake-4
• test-cpu-multiva-test-flake-5
• test-cpu-multiva-test-flake-6
• test-cpu-multiva-test-flake-7
• test-cpu-multiva-test-flake-9
• test-cpu-multiva-test-flake-8
• test-cpu-multiva-test-flake-3
• test-cpu-multiva-test-flake-2
• test-cpu-multiva-test-flake-10
• test-cpu-multiva-test-flake-fix-1
• test-cpu-multiva-test-flake-fix-4
• test-cpu-multiva-test-flake-fix-6
• test-cpu-multiva-test-flake-fix-7
• test-cpu-multiva-test-flake-fix-8
• test-cpu-multiva-test-flake-fix-3
• test-cpu-multiva-test-flake-fix-5
• test-cpu-multiva-test-flake-fix-9
• test-cpu-multiva-test-flake-fix-10
• test-authz2-purger
• test-instant-verify
• test-cleanup
• test-disableauthz2orders
• main
• test-runner-improvements

Build # 10461

Build Type

push

travis-ci

Committed by cpu

Commit Message

tests: rework multi-va integration tests.

Rather than having a middle server bounce/redirect requests based on how
many had arrived it would be more reliable to follow the way we did this
in unit tests and decide based on the request UA. By setting different
UAs for the remote VAs its possible to more precisely define how many
requests from each VA should be redirected to the real key
authorization.

I believe using the count was flaky because occasionally with
a configuration that allowed 2 requests to test that 1 of the 2 remote
VAs failing was an overall success would fail if the 2 remote VAs made
their requests before the primary VA. The primary VA always trumps the
remotes and so if the remotes consume the redirect quota the primary VA
will get the fail result and the overall validation will fail.

Run Details

11003 of 17460 relevant lines covered (63.02%)

0.7 hits per line