Skip to content

Score tests#288

Merged
yusefnapora merged 15 commits intomasterfrom
test/score-test
Apr 23, 2020
Merged

Score tests#288
yusefnapora merged 15 commits intomasterfrom
test/score-test

Conversation

@dirkmc
Copy link
Contributor

@dirkmc dirkmc commented Apr 20, 2020

Part of #287

  • Time in mesh
  • First message deliveries
  • Mesh message deliveries
  • Mesh failure penalty
  • Invalid message deliveries
  • App specific score
  • IP colocation factor

@yusefnapora yusefnapora force-pushed the test/score-test branch 3 times, most recently from aa66573 to 4e47188 Compare April 23, 2020 14:46
@yusefnapora
Copy link
Contributor

reading through, I just realized I'm using the withinVariance helper in places where I don't really need to... we should be able to do exact comparisons for the scores that aren't based on time.

@vyzo
Copy link
Collaborator

vyzo commented Apr 23, 2020

good point.

@vyzo
Copy link
Collaborator

vyzo commented Apr 23, 2020

failure in TimeInMesh:

=== RUN   TestScoreTimeInMesh

    TestScoreTimeInMesh: score_test.go:47: Score: 35.000000. Expected 20.000000 ± 10.000000

we seem to take longer to collect the score on travis,
which causes the score to be outside the expected bounds.
hopefully a longer wait time will give us more wiggle room.
@vyzo vyzo marked this pull request as ready for review April 23, 2020 16:51
Copy link
Collaborator

@vyzo vyzo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great!

@yusefnapora yusefnapora merged commit b2de9a5 into master Apr 23, 2020
vyzo pushed a commit that referenced this pull request Apr 23, 2020
* test: score time in mesh

* add TestScoreFirstMessageDeliveries

* rm redundant initialization to zero

* add TestScoreFirstMessageDeliveriesCap

* add TestScoreFirstMessageDeliveriesDecay

* fix comment

* add TestScoreMeshMessageDeliveries

* comments

* add TestScoreMeshFailurePenalty

* add TestScoreInvalidMessageDeliveries

also, TestScoreInvalidMessageDeliveriesDecay

* add TestScoreApplicationScore

* add TestScoreIPColocation

* add TestScoreMeshMessageDeliveriesDecay

* add TestScoreRetention

* try longer interval for TimeInMesh test

we seem to take longer to collect the score on travis,
which causes the score to be outside the expected bounds.
hopefully a longer wait time will give us more wiggle room.

Co-authored-by: Yusef Napora <yusef@protocol.ai>
@Stebalien Stebalien mentioned this pull request May 26, 2020
77 tasks
@vyzo vyzo deleted the test/score-test branch April 1, 2021 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants