Israel Fruchter

> > > @amnonh @fruch > > > I suppose this fix broke some Manager tests: > > > ``` > > > 13:01:34 ----- LAST ERROR EVENT ------------------------------------------------------- >...

@yaronkaikov I don't know what got it started But it's the Jenkins client code failing, which means you'll need your team to help figure it out...

> @yaronkaikov > > I don't know what got it started > > But it's the Jenkins client code failing, which means you'll need your team to help figure it...

for now seems to be happening more often in artifact pipeline: https://jenkins.scylladb.com/job/enterprise-2024.2/job/artifacts/job/artifacts-ami-arm-test/38/

@vponomaryov The builder probably got killed, the question is why, and by whom.

looking in AWS `CloudTrail -> Event history` the build was stopped after the error occurred in your job | Event name |User name | Event source |Resource type|Resource name |--------|--------|--------|--------|--------|...

> Just saw the same error today in https://jenkins.scylladb.com/job/releng-testing/job/artifacts/job/artifacts-docker-test/13/ that was triggered by scylla-ci-docker > > ``` > 08:36:28 ERROR: Checkout failed > 08:36:28 java.io.StreamCorruptedException: invalid stream header: 636F7272 >...

@Annamikhlin base on our differences in version and the ones reported in stackoverflow I can bet this change might be the cause: - https://www.oracle.com/java/technologies/javase/21-0-5-relnotes.html#JDK-8328286 - https://www.oracle.com/java/technologies/javase/17-0-13-relnotes.html#JDK-8328286 can we downgrade the...

> > [@Annamikhlin](https://github.com/Annamikhlin) > > base on our differences in version and the ones reported in stackoverflow > > I can bet this change might be the cause: > >...

> > > > [@Annamikhlin](https://github.com/Annamikhlin) > > > > base on our differences in version and the ones reported in stackoverflow > > > > I can bet this change...