Broken test suite in devel: version numbers
Originally created by @CyrilBrulebois on #17573 (Redmine)
I need to send a more detailed bug report / patch series for all
comments from the 4.5~rc1 release process, but it seems at least one
point needs to be addressed: custom.mdwn
has this:
### Else, if you just released a RC
[…]
* increment the version number in `devel`'s `debian/changelog` to
match the second next major release, so that images built from there
have the right version number:
cd "${RELEASE_CHECKOUT}" && \
git checkout devel && \
dch --newversion "${SECOND_NEXT_PLANNED_MAJOR_VERSION:?}" \
"Dummy entry for next release." && \
git commit debian/changelog \
-m "Add dummy changelog entry for ${SECOND_NEXT_PLANNED_MAJOR_VERSION:?}."
meaning devel
points at 4.11 now, but we don’t have any UDF files for
4.11 at the moment, meaning the test suite fails due to the upgrader’s
being unable to determine whether an upgrade is available.
intrigeri,
anonym, what do you think?
I imagine we could easily paper over the issue by pretending devel
is
about 4.5
, but I’m not sure we want to be hiding issues instead of
fixing them. OTOH, we might be wasting huge amounts of resources:
218 scenarios (73 failed, 145 passed)
1630 steps (73 failed, 415 skipped, 1142 passed)
688m30.952s