[Buildroot] [PATCH/next 2/3] support/testing; add prosody test
ricardo.martincoski at gmail.com
Wed Nov 28 02:13:43 UTC 2018
On Tue, Nov 27, 2018 at 02:52 AM, François Perrad wrote:
> Le mar. 27 nov. 2018 à 03:43, Ricardo Martincoski <
> ricardo.martincoski at gmail.com> a écrit :
>> On Sat, Nov 24, 2018 at 07:07 AM, Francois Perrad wrote:
>> > + def prosody_test(self):
>> > + # prosody was launched as service
>> > + cmd = "prosodyctl status"
>> > + output, exit_code = self.emulator.run(cmd)
>> > + self.assertEqual(exit_code, 0)
>> > + self.assertIn("Prosody is running", output)
>> I get an error message before the expected string:
>> # prosodyctl status
>> certmanager error SSL/TLS: Error initialising for
>> client_https port 0: unknown elliptic curve in "X25519:P-384:P-256:P-521"
>> Prosody is running with PID 727
>> I don't know if this message is expected in this minimal config or not.
>> If it is expected, we could add a comment and run something like this:
>> self.assertIn("Prosody is running", output)
>> Any ideas?
> We use the same "minimal" config.
> We have a reproductibility issue.
> I run test_prosody on my local box : "Prosody is running" is in output
> You run the same test in Gitlab CI : "Prosody is running" is in output
> Could you try to run the test locally ?
Calling run-tests locally (based on next branch 06a2d67c) also generates the
same error message and displays "Prosody is running" is in output
But then I rebased the tests to the master branch (1209eb2d) and called
No error message and "Prosody is running" is in output
And the same good result (based on master) on the GitLab CI
So it looks something related to the next branch.
Finally I merged master to next+tests and the test case passes.
So it looks something already fixed on master branch.
And I can add my tags to your patches (not today due to the lack of time).
Sorry for the noise.
More information about the buildroot