kernel/linux.git/tools/testing/ktest, branch v3.18.136

ktest: Fix child exit code processing

2017-04-18T05:55:49+00:00

commit 32677207dcc5e594254b7fb4fb2352b1755b1d5b upstream. The child_exit errno needs to be shifted by 8 bits to compare against the return values for the bisect variables. Fixes: c5dacb88f0a64 ("ktest: Allow overriding bisect test results") Signed-off-by: Steven Rostedt (VMware) Signed-off-by: Greg Kroah-Hartman

ktest: Fix make_min_config to handle new assign_configs call

2015-01-16T14:59:46+00:00

commit 9972fc0b859e7aaeb6d2d33bdb591959d9a436c0 upstream. Commit 6071c22e1755 "ktest: Rewrite the config-bisect to actually work" fixed the config-bisect to work nicely but in doing so it broke make_min_config by changing the way assign_configs works. The assign_configs function now adds the config to the hash even if it is disabled, but changes the hash value to be that of the line "# CONFIG_FOO is not set". Unfortunately, the make_min_config test only checks to see if the config is removed. It now needs to check if the config is in the hash and not set to be disabled. Signed-off-by: Steven Rostedt Signed-off-by: Greg Kroah-Hartman

ktest: Don't bother with bisect good or bad on replay

2014-10-07T20:34:25+00:00

If git bisect reply is being used in the bisect tests, don't bother doing the git bisect good or git bisect bad calls. The git bisect reply will override them anyway, and that's called immediately after the other two. Going the git bisect (good|bad) is just a waste of time. Signed-off-by: Steven Rostedt

ktest: Fix check for new kernel success on rebooting to good kernel

2014-10-07T20:31:07+00:00

The reboot function when rebooting back to a good kernel has a check to make sure that a new kernel was indeed booted. But that check uses a timeout value, which when calling the monitor will still return success if the timeout is hit (no bug was found). It should return an error to let the reboot code know that a new kernel was not reached. Only the reboot code checks the return value of the monitor. Signed-off-by: Steven Rostedt

ktest: add ability to skip during BISECT_MANUAL

2014-09-20T00:12:52+00:00

When doing a manual bisect, a build can fail or a test can be inconclusive. In these cases it would be helpful to be able to skip the test entirely. Link: http://lkml.kernel.org/r/1409164021-2136-1-git-send-email-chris.j.arges@canonical.com Reviewed-by: Satoru Takeuchi Signed-off-by: Chris J Arges Signed-off-by: Steven Rostedt

ktest: Add PATCHCHECK_CHERRY

2014-09-20T00:10:39+00:00

Add a way to run a patchcheck test on the commits that are in one branch but not in another. This uses git cherry to find a list of commits to test each one with. Signed-off-by: Steven Rostedt

ktest: Update documentation on config_bisect

2014-04-24T03:18:29+00:00

With the more robust config_bisect, the documentation is out of date and needs to be updated. The new rewrite allows for finding missing configs and such, and is much more robust to use. Signed-off-by: Steven Rostedt

ktest: Add the config bisect manual back

2014-04-24T03:18:26+00:00

After the rewrite of the config bisect, the bisect manual was removed. Add it back. Signed-off-by: Steven Rostedt

ktest: Remove unused functions

2014-04-24T03:18:25+00:00

After the rewrite of the config bisect, there were several unused functions that can be removed. One of the unused functions printed out the failed config nicer than what the rewrite did, so I kept that and used it to output the bad config. Signed-off-by: Steven Rostedt

ktest: Put back in the CONFIG_BISECT_CHECK

2014-04-24T03:18:20+00:00

The new rewrite left out the CONFIG_BISECT_CHECK, which allows the user to test that their "bad" config still is bad and their "good" config still is good. This is especially important as the configs are passed through a "make oldconfig" to update them with the lastest kernel. Things could change that causes a bad config to work, or a good config to break. The check is done after the configs have run through the oldconfig processing. Signed-off-by: Steven Rostedt