1
79%
master: 79%

Ran 30 Mar 2017 03:26PM UTC

Files 25

Run time 1s

Badge

Embed ▾

Committed 30 Mar 2017 03:19PM UTC coverage: 78.717% (-0.007%) from 78.724%

Job # 106.1

Build Type

Pull #59

travis-ci

Committed by

web-flow

Commit Message

bootman: Never match last_booted to running kernel

While an update currently performs just fine with clr-boot-manager, a
subsequent call to clr-boot-manager update, from a rebooted, updated system,
using tip & current, will result in the last kernel being garbage collected.

This is because last_good == running == tip, thus anything else is now
considered for garbage collection. With this simple change, we ensure that
last_running never matches our currently running kernel, as it is OK for
the last running kernel to be unknown. If it is known, then it truly is the
"newest" last kernel that isn't the one we're on now.

Signed-off-by: Ikey Doherty <michael.i.doherty@intel.com>

Pull Request Pull Request #59: Legacy fixes

Run Details

1583 of 2011 relevant lines covered (78.72%)

224.87 hits per line

ikeydoherty / clr-boot-manager / 106 / 1
79%
master: 79%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 106.1

ikeydoherty / clr-boot-manager / 106 / 1 79% master: 79%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 106.1

ikeydoherty / clr-boot-manager / 106 / 1
79%
master: 79%

README BADGES
x