Lines Matching +full:test +full:- +full:docs
1 .. SPDX-License-Identifier: (GPL-2.0+ OR CC-BY-4.0)
9 change that broke something -- for example when some functionality stopped
13 kernel, better follow Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
17 care about the result -- for example, because the problem happens after the
29 a fully reliable and straight-forward way to reproduce the regression, too.*
38 Instead of Git tags like 'v6.0' and 'v6.1' you can specify commit-ids, too.
68 test after this (roughly 10 steps)'. In that case go back to step 1.
75 mentioning the culprit's commit-id.
85 git bisect log > ~/bisection-log
86 cp .config ~/bisection-config-culprit
95 to revert the change by specifying its commit-id::
97 git revert --no-edit cafec0cacaca0
101 the culprit on its own because later changes depend on it -- at least unless
105 If a revert succeeds, build and test another kernel to check if reverting
109 Documentation/admin-guide/reporting-issues.rst.
111 Bisecting linux-next
112 --------------------
114 If you face a problem only happening in linux-next, bisect between the
115 linux-next branches 'stable' and 'master'. The following commands will start
116 the process for a linux-next tree you added as a remote called 'next'::
122 The 'stable' branch refers to the state of linux-mainline that the current
123 linux-next release (found in the 'master' branch) is based on -- the former
124 thus should be free of any problems that show up in -next, but not in Linus'
128 used in earlier linux-next releases without problems. Sadly there is no simple
129 way to avoid checking them: bisecting from one linux-next release to a later
130 one (say between 'next-20241020' and 'next-20241021') is impossible, as they
134 ---------------------------
136 * The `man page for 'git bisect' <https://git-scm.com/docs/git-bisect>`_ and
137 `fighting regressions with 'git bisect' <https://git-scm.com/docs/git-bisect-lk2009.html>`_
139 * `Working with git bisect <https://nathanchance.dev/posts/working-with-git-bisect/>`_
145 end-of-content
150 want to contribute changes to the text -- but for copyright reasons please CC
151 linux-doc@vger.kernel.org and 'sign-off' your contribution as
152 Documentation/process/submitting-patches.rst explains in the section 'Sign
153 your work - the Developer's Certificate of Origin'.
155 This text is available under GPL-2.0+ or CC-BY-4.0, as stated at the top
156 of the file. If you want to distribute this text under CC-BY-4.0 only,
159 …rnel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/Documentation/admin-guide/bug-bisect.rst
163 is available under CC-BY-4.0, as versions of this text that were processed