mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #67262
[Bug 1988840] Re: minaccept test fails on 2110_STABLE (21.10.04)
the old value in lib/version.php and new value in lib/version.php should
only be increased by the count of one
eg for 21.19_STABLE if the old value was 2021080209 then the check
expects the new value to be 2021080210 for the commit it is checking
When committing a patch to reviews - which uses the minaccept test
Your output shows it increasing by 11
During a release it should bump it by 2 - but this process does not use
the minaccept test as it's an automated process.
If I'm understanding your output correctly the minaccept thinks there
are a bunch of patches between your local HEAD point and the commits it
wants to test. Is this correct?
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: mahara-contributors
https://bugs.launchpad.net/bugs/1988840
Title:
minaccept test fails on 2110_STABLE (21.10.04)
Status in Mahara:
Incomplete
Bug description:
make: *** [minaccept] Error 1
Looks like minaccept found some issues:
Array
(
[0] => Running minimum acceptance test...
[1] => Bumping htdocs/lib/version.php...
[2] => Old version: 2021080209
[3] => New version: 2021080220
[4] => New htdocs/lib/db/upgrade.php: 2021080211
[5] => New htdocs/lib/db/upgrade.php: 2021080212
[6] => New htdocs/lib/db/upgrade.php: 2021080213
[7] => New htdocs/lib/db/upgrade.php: 2021080214
[8] => New htdocs/lib/db/upgrade.php: 2021080215
[9] => ERROR: Version in htdocs/lib/version.php should match version of last new section in htdocs/lib/db/upgrade.php
)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1988840/+subscriptions
References