> Could there be some automatic calculation of memory resources that makes
> the build fail on some servers and not on others?
>
maybe but
> Our CI servers have 28GiB of memory. Could Docker allocate an amount
> that is particularly suitable for our test suite?
>
the last memory error failure
Could there be some automatic calculation of memory resources that makes
the build fail on some servers and not on others?
Our CI servers have 28GiB of memory. Could Docker allocate an amount
that is particularly suitable for our test suite?
I know that I had some pain to reproduce a green
>
> My 2 cents trying to bring a little force in this nice project :)
>
Thanks Raphaël :)
All our old CI is open source, so you can just check the source, Luke:
> https://github.com/linagora/james-jenkins/blob/master/workflow-job#L643
thanks for the pointer, I had not looked for that one.
Hi Jean,
Thank you so much for delivering this awesome fight against the red CI.
In the past, such unstable builds have always been linked to some
resources leaks during tests.
At this point, we usually stopped implementing new things for a while
and focus in pluging leaks to bring back build
Hello Jean,
My 2 cents trying to bring a little force in this nice project :)
All our old CI is open source, so you can just check the source, Luke:
https://github.com/linagora/james-jenkins/blob/master/workflow-job#L643
This calls images.jamesCompile which is built here:
Happy new year fellow jamers !
In this thrilling new episode you might learn if 2021 will be the year the
james project gets a public ci rolling again !
CI wars
Episode 49e^55
The Memory errors strike back
The CI Resistance succeeded in configuring jenkins, fixed some tests,
exposed some bugs
Hi Benoit,
As someone operating another CI, I want to play even unstable test on
> every runs. Is there some adaptation needed to do this?
>
Yes you will have to change your CI,
> mvn -B -e -fae test
now only runs stable tests, to run unstable tests you need an additional
step
> mvn -B -e -fae
Hello Jean,
Nice work!
Le 28/12/2020 à 23:21, Jean Helou a écrit :
> Hello again jamers!
>
> It's time for a new irregular report on the CI effort on apache infra !
>
> Let's start with the good news : today I finally reached a successful build
>
Hello again jamers!
It's time for a new irregular report on the CI effort on apache infra !
Let's start with the good news : today I finally reached a successful build
https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-268/45/pipeline
(the first fully successful
I conclude that my effort to get CI working is cursed by the gods,
remember :
> > {"message":"No such image: quay.io/testcontainers/ryuk:0.2.3"}
>
> which repeats for most tests failures, this seems to be common enough that
> there is stack overflow for it
>
>
Le 11/12/2020 à 16:35, Jean Helou a écrit :
I'm in favor for opening a dedicated ticket and merge a disabled version
of this test in order to document the problem.
>>>
>>> it"s been busy and I haven't opened the ticket yet, nor have we managed
>> to
>>> fully fix the issue yet
> >> I'm in favor for opening a dedicated ticket and merge a disabled version
> >> of this test in order to document the problem.
> >>
> >
> > it"s been busy and I haven't opened the ticket yet, nor have we managed
> to
> > fully fix the issue yet
> >
>
> I can devote some of my time to support
Hello Jean,
Le 11/12/2020 à 15:47, Jean Helou a écrit :
> Hello again jamers!
>
> It's time for your irregular report on the CI effort on apache infra :)
\o/
>> I'm in favor for opening a dedicated ticket and merge a disabled version
>> of this test in order to document the problem.
>>
>
>
Hello again jamers!
It's time for your irregular report on the CI effort on apache infra :)
I'm in favor for opening a dedicated ticket and merge a disabled version
> of this test in order to document the problem.
>
it"s been busy and I haven't opened the ticket yet, nor have we managed to
Hi,
On Fri, 2020-12-04 at 14:59 +0700, btell...@linagora.com (OpenPaaS)
wrote:
[...]
> >
> > Here is what I would like to do at this stage :
> > - Isolate the unstable tests under with an unstable tag (akin to
> > "feature
> > tags")
> I'd advocate a @Disabled tag, referencing both a JIRA
Le 04/12/2020 à 03:21, Jean Helou a écrit :
> Hello fellow jamers !
>
> The Jenkinsfile in the PR works, up until the test suite fails, the tests
> failures are from seemingly "unstable" tests that fail because of timing
> issues. Benoit fixed the first one in
>
Hello fellow jamers !
The Jenkinsfile in the PR works, up until the test suite fails, the tests
failures are from seemingly "unstable" tests that fail because of timing
issues. Benoit fixed the first one in
https://github.com/apache/james-project/pull/267 by disabling read repairs
during
Hello everyone,
The current jenkins setup won't run builds on PRs from people who don't
have write access to the repository. This means that even though Benoit
fixed the cassandra-related flaky test[1] and I fixed a rabbitmq-related
flaky test[2] andI then rebased it all to account for Benoit's
Likely "unstable".
>
> I will have a look at this tomorrow.
>
Ok thanks
>
Likely "unstable".
I will have a look at this tomorrow.
Le 26/11/2020 à 17:22, Jean Helou a écrit :
> The good news is that docker does indeed work, the bad news is that the
> tests fail with an issue that's too involved for me :/
>
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
>
The good news is that docker does indeed work, the bad news is that the
tests fail with an issue that's too involved for me :/
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]
on a loosely related note : the test suite logs are scary to look at:
piles upon piles of stack traces and error logs but the tests actually pass
...
On Thu, Nov 26, 2020 at 10:50 AM Jean Helou wrote:
> Thanks benoit,
>
> Matthieu pointed me to numerous apache projects with jenkinsfiles which
>
Thanks benoit,
Matthieu pointed me to numerous apache projects with jenkinsfiles which
mention docker in
https://github.com/search?q=org%3Aapache++filename%3AJenkinsfile+docker=Code
so I'm trying out things based on that
the logs seem promising so far :
```
[INFO] Tests run: 3, Failures: 0,
Done
Le 26/11/2020 à 16:25, Jean Helou a écrit :
> hi all,
>
> As you know I started a PR to setup jenkins CI, the latest iteration sees
> the compilation of the project complete in 5 minutes ( thanks to T1C) but
> the tests fail to initialize docker containers with the disastrous
> consequences
hi all,
As you know I started a PR to setup jenkins CI, the latest iteration sees
the compilation of the project complete in 5 minutes ( thanks to T1C) but
the tests fail to initialize docker containers with the disastrous
consequences you can imagine :D
I opened
25 matches
Mail list logo
