Skip to content

Automatically detect wrong bisection results due to flapping code #378

Description

@AlexDaniel

Currently, there's this check:

if $link-msg.ends-with: 07fecb52eb1fd07397659f19a5cf36dc61f84053 {
grumble The result looks a bit unrealistic. Most probably the output
~ is different on every commit (e.g. 「bisect: say rand」)

However, @lizmat++ and @Altai-man++ came up with an idea of doing this check automatically by comparing .moarvm files of the final commit and its parent.

I have a suspicion that rakudo in the past did not produce the same .moarvm file reproducibly, meaning that the check won't work on old commits. However, we can still do some checks, for example we can check if all changed files in the commit were to doc files.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bisectableIssues related to Bisectable botwhateverableIssues affecting the bot framework (and therefore all of the bots)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions