On Wed, 9 Oct 2024 19:45:24 GMT, Kevin Walls wrote:
>> Sebastian Lövdahl has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Have EventGeneratorLoop end after a more predictable duration
>
> Yes OEL was Oracle Linux:
>
> Our CI tests with d
On Fri, 22 Nov 2024 21:56:40 GMT, Leonid Mesnik wrote:
>> Sebastian Lövdahl has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Have EventGeneratorLoop end after a more predictable duration
>
> Marked as reviewed by lmesnik (Reviewer).
Than
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Wed, 9 Oct 2024 19:45:24 GMT, Kevin Walls wrote:
>> Sebastian Lövdahl has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Have EventGeneratorLoop end after a more predictable duration
>
> Yes OEL was Oracle Linux:
>
> Our CI tests with d
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Wed, 9 Oct 2024 19:45:24 GMT, Kevin Walls wrote:
>> Sebastian Lövdahl has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Have EventGeneratorLoop end after a more predictable duration
>
> Yes OEL was Oracle Linux:
>
> Our CI tests with d
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Wed, 9 Oct 2024 11:11:24 GMT, Kevin Walls wrote:
>> Sebastian Lövdahl has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Have EventGeneratorLoop end after a more predictable duration
>
> Hmm, actually no I _can_ still get a failure.
>
>
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:50:46 GMT, Kevin Walls wrote:
>> Sebastian Lövdahl has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Have EventGeneratorLoop end after a more predictable duration
>
> Don't worry I'll close 8341518 as a duplicate.
@
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:37:51 GMT, Sebastian Lövdahl wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteratio
On Mon, 7 Oct 2024 19:20:38 GMT, Sebastian Lövdahl wrote:
> Interesting! What could possibly interrupt `EventGeneratorLoop`?
It's a good question, but I don't know exactly... We do see interrupted
exceptions in testing sometimes, and we might have various tests running on the
same system at t
> The fix is twofold.
>
> 1. Stop the main container after an iteration is done. The main container is
> started with its runtime defined as 120 seconds, which means that each
> iteration takes 120 seconds. In reality, one iteration takes a few seconds
> while 115 seconds is spent waiting on th
On Mon, 7 Oct 2024 11:57:39 GMT, Kevin Walls wrote:
>> The fix is twofold.
>>
>> 1. Stop the main container after an iteration is done. The main container is
>> started with its runtime defined as 120 seconds, which means that each
>> iteration takes 120 seconds. In reality, one iteration take
> The fix is twofold.
>
> 1. Stop the main container after an iteration is done. The main container is
> started with its runtime defined as 120 seconds, which means that each
> iteration takes 120 seconds. In reality, one iteration takes a few seconds
> while 115 seconds is spent waiting on th
On Thu, 3 Oct 2024 19:13:46 GMT, Sebastian Lövdahl wrote:
> The fix is twofold.
>
> 1. Stop the main container after an iteration is done. The main container is
> started with its runtime defined as 120 seconds, which means that each
> iteration takes 120 seconds. In reality, one iteration tak
On Thu, 3 Oct 2024 19:13:46 GMT, Sebastian Lövdahl wrote:
> The fix is twofold.
>
> 1. Stop the main container after an iteration is done. The main container is
> started with its runtime defined as 120 seconds, which means that each
> iteration takes 120 seconds. In reality, one iteration tak
23 matches
Mail list logo
