ngcp-panel

Commit Graph

Author	SHA1	Message	Date
Michael Prokop	968ed762e6	MT#15071 Docker setup for api-rest tests For usage instructions please look at the bottom of the Dockerfile, usage similar to what we already have for the docker selenium tests. Known problems: 1) In t/api-rest/api-journals.t there's a failure, though all the tests actually seem to run fine then: \| encountered object 'true', but neither allow_blessed nor convert_blessed settings are enabled at /usr/share/perl5/JSON.pm line 154. \| # Tests were run but no plan was declared and done_testing() was not seen. \| # Looks like your test exited with 255 just after 1130. \| [...] \| t/api-rest/api-journals.t (Wstat: 65280 Tests: 1130 Failed: 0) \| Non-zero exit status: 255 \| Parse errors: No plan found in TAP output \| Files=25, Tests=8363, 347 wallclock secs ( 1.14 usr 0.11 sys + 32.59 cusr 2.23 csys = 36.07 CPU) 2) Failures in t/api-rest/api-balanceintervals.t, might be caused by timing issues/rerunning them, needs investigation though: \| t/api-rest/api-balanceintervals.t (Wstat: 65024 Tests: 1875 Failed: 318) \| Failed tests: 51, 56-59, 62, 67, 70, 75-80, 83, 88, 108-109 \| [...] Change-Id: I5d697cab4a1a4c6697857fc63c03b8d3fd8965d2	10 years ago

Author

SHA1

Message

Date

Michael Prokop

968ed762e6

MT#15071 Docker setup for api-rest tests

For usage instructions please look at the bottom of the Dockerfile,
usage similar to what we already have for the docker selenium tests.

Known problems:

1) In t/api-rest/api-journals.t there's a failure, though all the tests
   actually seem to run fine then:

| encountered object 'true', but neither allow_blessed nor convert_blessed settings are enabled at /usr/share/perl5/JSON.pm line 154.
| # Tests were run but no plan was declared and done_testing() was not seen.
| # Looks like your test exited with 255 just after 1130.
| [...]
| t/api-rest/api-journals.t               (Wstat: 65280 Tests: 1130 Failed: 0)
|   Non-zero exit status: 255
|   Parse errors: No plan found in TAP output
| Files=25, Tests=8363, 347 wallclock secs ( 1.14 usr  0.11 sys + 32.59 cusr  2.23 csys = 36.07 CPU)

2) Failures in t/api-rest/api-balanceintervals.t, might be caused by
   timing issues/rerunning them, needs investigation though:

| t/api-rest/api-balanceintervals.t (Wstat: 65024 Tests: 1875 Failed: 318)
|   Failed tests:  51, 56-59, 62, 67, 70, 75-80, 83, 88, 108-109
|  [...]

Change-Id: I5d697cab4a1a4c6697857fc63c03b8d3fd8965d2

1 Commits (968ed762e65fbf9edab08e21c5adb9246994fadb)