TryBugHunt
goLogic errorMedium

Runner-up score is the same as the winning score

BugFind the bug and fix the code

What it should do

runnerUpScore(scores) returns the second-highest distinct score in a list with at least two different scores. runnerUpScore([3, 8, 5]) returns 5.

What happens instead

runnerUpScore([3, 8, 5]) returns 8, which is the winning score.

package main

import "math"

func runnerUpScore(scores []int) int {
    first, second := math.MinInt64, math.MinInt64
    for _, s := range scores {
        if s > first {
            first = s
            second = first
        } else if s > second && s != first {
            second = s
        }
    }
    return second
}

Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).

⏱️0:00
Hints
🏆 0 hints = Flawless Solve
Think & Test Cooldown
2:00 remaining

Take a moment to read the bug symptom and trace the code with Run & Check before unlocking Hint 1.

Hint 2
Unlocks after Hint 1
Hint 3
Unlocks after Hint 2

This bug belongs to the logic errors pattern

The wrong operator, an inverted condition, a formula the right way round but backwards.

What you'll practise

A medium Go debugging exercise about logic errors: the wrong operator, an inverted condition, a formula the right way round but backwards.

The checks your fix must pass

Signs of this kind of bug

Spoiler: why this bug happens(try it first; the hints get warmer one at a time)

When a new top score arrives, the old top score must move down to second place before it is overwritten. The broken code overwrites first and then copies it, so second just becomes the new top score as well. After that no score can ever be greater than second without also being the new first, so the result is always the maximum. Order matters whenever you shift values along a chain: save or move the old value before you replace it.

The pattern behind it: logic errors.

More logic errors to practise

Embed this challenge on your site

Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.

<iframe src="https://trybughunt.com/embed/bbe13330-5b4d-4f51-a506-1de1c86b1749" title="Debugging challenge: Runner-up score is the same as the winning score" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/bbe13330-5b4d-4f51-a506-1de1c86b1749">TryBugHunt</a></p>