# mozregression - new way for handling merges

DevFeed: [mozregression - new way for handling merges](<https://devfeed.tech/articles/mozregression-new-way-for-handling-merges-20298.md>)

Original publisher: [Read original article](<https://parkouss.wordpress.com/2015/11/14/mozregression-new-way-for-handling-merges/>)

Author: parkouss

Published: 2015-11-14T09:42:48Z

Content type: article

Language: en

Sources: [Mozilla Automation](<https://devfeed.tech/sources/mozilla-automation.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Mozilla](<https://devfeed.tech/topics/mozilla.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [contribution](<https://devfeed.tech/tags/contribution.md>), [integration](<https://devfeed.tech/tags/integration.md>), [mozilla](<https://devfeed.tech/tags/mozilla.md>), [mozregression](<https://devfeed.tech/tags/mozregression.md>), [python](<https://devfeed.tech/tags/python.md>), [regression](<https://devfeed.tech/tags/regression.md>), [taskcluster](<https://devfeed.tech/tags/taskcluster.md>), [test](<https://devfeed.tech/tags/test.md>)

## AI overview

This article proposes improving mozregression's handling of merge commits during regression bisection. The approach uses Taskcluster builds to narrow the range, identifies the branch containing the merged commits, and bisects that push range.

## Source excerpt

I am currently investigating how we can make mozregression smarter to handle merges, and I will explain how in this post. Problem While bisecting builds with mozregression on mozilla-central, we often end up with a merge commit. These commits often incorporate many individual changes, consider for example this url for a merge commit. A regression ... Continue reading mozregression - new way for handling merges