errtracker: report if snapd did re-execute itself #3425

Merged
merged 1 commit into from Jun 1, 2017

Conversation

Projects
None yet
2 participants
Contributor

zyga commented Jun 1, 2017

Re-execution affects which internal tools and which snapd is used.
while the current error report shows us hashes of both distribution
and core snapd we always need to guess which one is being used
by inspecting the version string. This makes it more obvious.

Signed-off-by: Zygmunt Krynicki zygmunt.krynicki@canonical.com

errtracker: report if snapd did re-execute itself
Re-execution affects which internal tools and which snapd is used.
while the current error report shows us hashes of both distribution
and core snapd we always need to guess which one is being used
by inspecting the version string. This makes it more obvious.

Signed-off-by: Zygmunt Krynicki <zygmunt.krynicki@canonical.com>

@mvo5 mvo5 merged commit e8e0780 into snapcore:release/2.26 Jun 1, 2017

0 of 7 checks passed

artful-amd64 autopkgtest running
Details
continuous-integration/travis-ci/pr The Travis CI build is in progress
Details
xenial-amd64 autopkgtest running
Details
xenial-i386 autopkgtest running
Details
xenial-ppc64el autopkgtest running
Details
yakkety-amd64 autopkgtest running
Details
zesty-amd64 autopkgtest running
Details

@zyga zyga deleted the zyga:backport/2.26/detect-re-exec branch Aug 22, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment