Bug 267770 - Basic automated testing of key software
Summary: Basic automated testing of key software
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Testing & CI (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Jenkins Administrators
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-14 21:58 UTC by Yonas Yanfa
Modified: 2022-12-28 17:48 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yonas Yanfa 2022-11-14 21:58:44 UTC
This surprises me:

www/nginx: Fix nginx after lua-resty-core update

Update 3rd party module ngx_http_lua_module to 0.10.22 otherwise nginx
fails to start with the following error message:

nginx: [alert] failed to load the 'resty.core' module
(https://github.com/openresty/lua-resty-core); ensure you are using an
OpenResty release from https://openresty.org/en/download.html (reason:
/usr/local/share/lua/5.1/resty/core/base.lua:23: ngx_http_lua_module
0.10.22 required) in /usr/local/etc/nginx/nginx.conf:76

This has been broken for almost two weeks, use the
"Trivial and tested build and runtime fixes" blanket from 22.8.1 of the
committers guide to prevent more people from breaking their production
setups. nginx-devel already has version 0.10.22 of the module.

PR:		267418
-- 

We should create some simple automated tests that run as part of the package build process. For example, we should make sure `service $service enable` and `service $service start` both return zero exit codes, as well as something like `pgrep -lf $service` -- this should be open to customization for each port.


Port maintainers should be encouraged to create additional tests, such as:

- verify listening on correct interface and port via `sockstat`
- connecting to the server app works via `telnet`, even if you don't perform a full authentication
- memory allocation limits are respected (esp. in the Java world)