Bug 37128 - Failing mirror test: 83mirror-many
Failing mirror test: 83mirror-many
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: Updater
unspecified
Other Linux
: P5 normal (vote)
: UCS 5.0
Assigned To: Jürn Brodersen
Philipp Hahn
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-01 13:54 CET by Philipp Hahn
Modified: 2020-10-04 18:23 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2014-12-01 13:54:11 CET
*** BEGIN *** ['/bin/bash', '83mirror-many'] ***
*** 09_updater/83mirror-many *** Mirror localhost minimum
1. Create minimum mirror with 101 minor updates, using hard-links
2. Check if updater aborts on 99 and 999 ***
*** START TIME: 2014-11-29 00:00:48 ***
6759 blocks
gpg: keyring `/root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
OK
Creating patchlevel... minor... major... done.
Stopping periodic command scheduler: cron.
Checking /etc/apt/mirror.list for 294 required entries...
Failed '^deb http://localhost\(:80\)\?/univention-repository/'
set base_path    /tmp/tmp.r7GMdunkS9/mirror
set nthreads     10
set recreate_packages no
**************** Test failed above this line ****************
ERROR 83mirror-many:511 0
ERROR return 1
=== RESULT: 121 ===
*** END TIME: 2014-11-29 00:01:04 ***
*** TEST DURATION (H:MM:SS.ms): 0:00:16.582905 ***
*** END *** 121 ***
Comment 1 Jürn Brodersen univentionstaff 2020-09-28 12:40:46 CEST
The test in its current state does not check the abort at 99 due to the naming schema conflicts for release > 9.

Since discovering releases is now done through the releases.json this isn't really necessary anymore.

I still think having a dedicated test that checks mirroring a few more releases is useful, though.
Comment 2 Philipp Hahn univentionstaff 2020-10-04 18:23:18 CEST
OK, nothing to release.