On 15/07/2021 15:30, Shawn McKinney wrote:
On Jul 11, 2021, at 11:16 AM, Stefan Seelmann <[email protected]> wrote:
On 7/11/21 5:53 PM, Shawn McKinney wrote:
On Jul 11, 2021, at 9:42 AM, Emmanuel Lécharny <[email protected]> wrote:
I do think that we need some faster way to validate the packages. It took me
around 1h30 to do that last night, most of it being waiting for the tests to be
ran.
By tests you mean integration tests, i.e. junit?
If yes, that’s surprising. It runs in about 7 or 8 minutes for me.
The tests against ApacheDS are quite slow and also take more than one
hour for me. See also the Jenkins build [3] which most of the time only
runs the IT once and fails with some timing issues.
Yes, the tests are quite intense with many thousands of edits being sent.
Hopefully, with the changes to use its new DB (get finished), this will speed
up.
In the meantime, perhaps I should create an abbreviated test. One that can
finish in under 10 minutes.
I don't really mind if the tests are taking 10 mins or even 1 hour, my
problem is that there are many manual steps involved and I would like to
see iff we can just start a script that ends in, say, 1h and says=: "Ok,
builds done, sig verified, N&L checked, all is good" without having
anything to do but to have a good tea and enjoy a Dr House in the mean
time :-)
What test suite are you running?
Can we design a script that does all the steps automatically, including the
signature verifications and N&L checks?
Just getting back to this. What does the script need to do?
1. Build the packages
2. Run the core integration tests
3. Check the sigs.
4. N&L checks? How do we automate this?
N&L checks would mainly be checking that the packages contain them.
And, what should it be written in — Bash?
Yes, or whatever works.
--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
[email protected] https://www.busit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
