| 1 |
Am 17.05.2016 um 09:37 schrieb Pallav Agarwal: |
| 2 |
> For normal users we wouldn't. But currently, arch-testers need to make a |
| 3 |
> judgement call on what to test when a stable-req bug is filed. Tests run in |
| 4 |
> src_test are provided by upstream, and does not guarantee that a package |
| 5 |
> that has been merged will actually run on the system. |
| 6 |
> If the maintainer could add a couple small scripts to check basic |
| 7 |
> functionality |
| 8 |
> of the merged package, it would make testing for arch testers much easier |
| 9 |
> and reliable. |
| 10 |
> Let me give an example. Let's say |
| 11 |
> app-misc/screenfetch-2.7.7 is the current stable package for screenfetch in |
| 12 |
> the portage tree. |
| 13 |
> However, on running, it produces an error on the top, along with the proper |
| 14 |
> output. |
| 15 |
> If screenfetch-3.0.0 happens to fix that error, maintainer can add a simple |
| 16 |
> script |
| 17 |
> |
| 18 |
> if [ "$(screenfetch 2>&1 1>/dev/null)" != "" ] then |
| 19 |
> eerror "Still producing error" |
| 20 |
> fi |
| 21 |
> |
| 22 |
> To make sure the build is properly updating the screenfetch version, and |
| 23 |
> that |
| 24 |
> the bug has in fact been fixed. This is the only way I can see to reliabily |
| 25 |
> and automatically test packages that have been merged successfully. |
| 26 |
> |
| 27 |
> ------- |
| 28 |
> Regards, |
| 29 |
> Pallav |
| 30 |
> |
| 31 |
> On Mon, May 16, 2016 at 10:08 PM, Luis Ressel <aranea@×××××.de> wrote: |
| 32 |
> |
| 33 |
>> On Mon, 16 May 2016 18:13:33 +0530 |
| 34 |
>> Pallav Agarwal <pallavagarwal07@×××××.com> wrote: |
| 35 |
>> |
| 36 |
>>> What I'm suggesting is to add a new function post_install_test. The |
| 37 |
>>> function will run only if the build is being run for stabilization |
| 38 |
>>> (either as a part of automated stabilization, or manual) which can be |
| 39 |
>>> controlled by a USE flag. The function would also require independent |
| 40 |
>>> dependencies in case it uses external applications to test the one |
| 41 |
>>> being built. |
| 42 |
>> |
| 43 |
>> Could you please elaborate on this? We already have src_test() for |
| 44 |
>> automated tests. Why would we want to run additional tests after the |
| 45 |
>> package has been merged? |
| 46 |
>> |
| 47 |
>> -- |
| 48 |
>> Regards, |
| 49 |
>> Luis Ressel |
| 50 |
>> |
| 51 |
>> Luis Ressel <aranea@×××××.de> |
| 52 |
>> GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD |
| 53 |
>> |
| 54 |
> |
| 55 |
|
| 56 |
Good afternoon, |
| 57 |
|
| 58 |
facilities for running post-install (pre-merge) QA-checks are in place. |
| 59 |
Please have a look at portage's misc-functions.sh, install_qa_check() |
| 60 |
will reveal the locations where you can find the installed checks, along |
| 61 |
with a place for local overrides. Perhaps you can design something |
| 62 |
around this? |
| 63 |
|
| 64 |
With kind regards, |
| 65 |
tomboy64 |
Archives