Project

General

Profile

Actions

Feature #3555

closed

debian-repo-install-test: check if binaries report UNKNOWN as version string

Added by osmith over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
09/14/2018
Due date:
% Done:

100%

Spec Reference:

Description

In #3176 a new Jenkins job is created, that checks if the packages from the Debian repository can be installed on a plain Debian image that did not have Osmocom packages before. To make sure that all binaries can be started, we are calling them with --version in the test.

laforge commented:

[...] in the past we also had the problem that some packages would generate UNKNOWN as version string. So as we're calling all binaries with --version anyway, it might be a good idea to also check that there's no UNKNOWN string present in the output?
I guess the best would be to add the above new test as a new function, so the test output (ends up in jenkins console log) would clearly state what failed.

And indeed, as I was developing the test, I saw that many programs did output UNKNOWN as version string.

This can be worked on as soon as #3176 is finished.


Related issues

Related to Cellular Network Infrastructure - Bug #3176: osmocom debian packages are not install / upgrade testedResolvedosmith04/16/2018

Actions
Related to Cellular Network Infrastructure - Bug #3449: network:osmocom:nightly packages have VERSION="UNKNOWN"Resolvedlaforge08/06/2018

Actions
Related to Cellular Network Infrastructure - Bug #3661: latest stable packages report "UNKNOWN" as version string in --versionResolvedosmith10/17/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)