Hi Taher,
Prior to Gradle migration we were not using the 8080 port during tests. For instance we could have an OFBiz instance running, playing with its UI and
then run tests on another instance or vice-versa.
This is no longer possible because now the port 8080 (and others) are kept open while running tests. So far it was only a "small" annoyance, but it's
now blocking BuildBot because infra puppetized the BuildBot slaves https://s.apache.org/pWQD.
And, I don't know why and this could be a question to infra, for a reason there is always a Tomcat instance running on port 8080 these hosts
https://s.apache.org/iSaN
I thought we could bypass this issue by using portoffset with testIntegration task since it's now required. But I just tested locally and it seems to
not work. I'm not quite sure and will try a last thing directly "on" Buildbot. If it does not work we have to think about removing this need of open
ports while running tests, IOW to remove this regression introduced with Gradle.
Before anything else, I will though ask infra why Tomcat is always running on
these hosts...
Jacques
Le 27/01/2017 à 18:15, Taher Alkhateeb a écrit :
Why do we need to run the tests on portoffset?
On Fri, Jan 27, 2017 at 7:48 AM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
Ah, I forgot to say, that I have dropped BuildBot support for R12 and R13.
Also that the pre-Gradle versions don't need portoffset
Le 27/01/2017 à 05:29, Jacques Le Roux a écrit :
Le 27/01/2017 à 05:14, Jacques Le Roux a écrit :
But in the case of running integration tests with a portoffset we have
an issue which is blocking BuildBot now for trunk and
R16
Jacques
