On 7/19/23 03:26, Calvin Buckley wrote:
Lack of easily available CI environments for i is by far the biggest
pain point. I’ve been poking the IBM people I know to improve the
situation.
(The annoying thing it's harder to have a disposable environment, for
reproducibility/security's sake. Even "just a box" is better than the
current status though though.)
WRT what Timothe said, I don’t think native Perl is useful (it’s highly
unmaintained AFAIK, and platform differences will probably make porting
the test runner annoying) , but you could use the AIX Perl to run tests
against the ILE curl. But even then, once you have a CI box, you can at
least run compile smoke tests.
If you think you can do it, please act! As I said before, I personally
gave up trying to adapt the test environment after a long investigation
and building up a CI from scratch is out of my skills.
There are many points you should know though:
- PASE perl usage is problematic: see one of my previous mail in this
thread.
- The curl cli tool is not ported to ILE. The main reasons are: 1)
EBCDIC (could be a QADRT program, yes), 2) Too many options to be
supported in a *CMD (the primary goal was not a qshell usage).
- gskit uses a certificate store rather than PEM files, thus specifying
crypto objects to it differs from other backends. standard TLS test
cases won't then be compatible.
- A libtest makefile that compiles C test programs exists from the very
early days of the OS400 port, but is now disabled (and unmaintained) for
years. The idea behind it was to have what you call "smoke tests" and a
first step to the (later abandoned) test environment implementation.
- Remember we are currently targetting gskit, not only OS400 and/or
compilation: as this backend is not available for other platforms, we
cannot rely on cross test results for it.
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
