[
https://issues.apache.org/jira/browse/JAMES-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280179#comment-17280179
]
ASF GitHub Bot commented on JAMES-3225:
---------------------------------------
jeantil commented on pull request #264:
URL: https://github.com/apache/james-project/pull/264#issuecomment-774474432
We finally got a green run :
https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/51/pipeline
to get there we had to drop all attempts at parallelisation: no
surefire-forks, no running jobs in parallel and be lucky not to be hit by the
[copy on write
issue](https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/49/tests)
(see the detailed logs for org.apache.james.smtp.SmtpRandomStoringTest and
you will find the signature null pointer exception ```
15:53:44.340 [ERROR] o.a.j.t.m.d.MailDispatcher - Error While storing mail.
java.lang.NullPointerException: null
at
org.apache.james.server.core.MimeMessageInputStream.<init>(MimeMessageInputStream.java:63)
```
or by timeouts as in
https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/50/tests
build 52 where I attempted to run test suites in parallel again failed with
a linshare container initialization failure which had been [encountered
before](https://builds.apache.org/blue/organizations/jenkins/james%2FApacheJames/detail/PR-264/41/tests):
```
java.lang.ExceptionInInitializerError
at
org.apache.james.webadmin.integration.memory.vault.MemoryLinshareBlobExportMechanismIntegrationTest.<clinit>(MemoryLinshareBlobExportMechanismIntegrationTest.java:34)
Caused by: org.testcontainers.containers.ContainerLaunchException: Container
startup failed
at
org.apache.james.webadmin.integration.memory.vault.MemoryLinshareBlobExportMechanismIntegrationTest.<clinit>(MemoryLinshareBlobExportMechanismIntegrationTest.java:34)
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit
with exception
at
org.apache.james.webadmin.integration.memory.vault.MemoryLinshareBlobExportMechanismIntegrationTest.<clinit>(MemoryLinshareBlobExportMechanismIntegrationTest.java:34)
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not
create/start container
```
I started archiving the test-run.log on failure and logging as much test
container related stuff as possible to have more details on such failures: it
looks like the container fails to coordinate internally or maybe is killed
during initialization by a timeout that is a bit too optimistic for the CI
plateform ... (the database receives a fast-shutdown command while it is apply
migrations and the backend which is starting fails to connect)
```
03:59:52.056 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> COMMIT
03:59:52.105 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.155 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.222 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.271 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.345 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.397 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.455 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> CREATE VIEW
03:59:52.456 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database>
03:59:52.462 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> LOG: received fast shutdown request
03:59:52.462 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> waiting for server to shut down...LOG: aborting any active
transactions
03:59:52.462 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> .LOG: autovacuum launcher shutting down
03:59:52.466 [DEBUG] org.apache.james.linshare.Linshare -
<linshare-database> LOG: shutting down
03:59:52.706 [DEBUG] org.apache.james.linshare.Linshare - <linshare-backend>
[WARN]:localhost-startStop-1:20210206.035952:org.hibernate.orm.cache:createCache:HHH90001006:
Missing cache[default-update-timestamps-region] was created on-the-fly. The
created cache will use a provider-specific default configuration: make sure you
defined one. You can disable this warning by setting
'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
03:59:52.706 [DEBUG] o.t.c.output.WaitingConsumer - STDOUT:
[WARN]:localhost-startStop-1:20210206.035952:org.hibernate.orm.cache:createCache:HHH90001006:
Missing cache[default-update-timestamps-region] was created on-the-fly. The
created cache will use a provider-specific default configuration: make sure you
defined one. You can disable this warning by setting
'hibernate.cache.ehcache.missing_cache_strategy' to
'create'.efault-query-results-region] was created on-the-fly. The created cache
will use a provider-specific default configuration: make sure you defined one.
You can disable this warning by setting
'hibernate.cache.ehcache.missing_cache_strategy' to 'create'.
03:59:52.737 [DEBUG] o.t.c.output.WaitingConsumer - STDOUT:
[WARN]:localhost-startStop-1:20210206.035952:org.hibernate.orm.cache:createCache:HHH90001006:
Missing cache[default-query-results-region] was created on-the-fly. The
created cache will use a provider-specific default configuration: make sure you
defined one. You can disable this warning by setting
'hibernate.cache.ehcache.missing_cache_strategy' to
'create'..ehcache.missing_cache_strategy' to 'create'.
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare - <linshare-backend>
06-Feb-2021 03:59:56.291 WARNING [localhost-startStop-1]
org.postgresql.core.v3.ConnectionFactoryImpl.log ConnectException occurred
while connecting to linshare_database:5432
03:59:56.296 [DEBUG] o.t.c.output.WaitingConsumer - STDERR:
java.net.ConnectException: Connection refused (Connection refused)
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare - <linshare-backend>
java.net.ConnectException: Connection refused (Connection refused)
03:59:56.296 [DEBUG] o.t.c.output.WaitingConsumer - STDERR: at
org.hibernate.tool.schema.internal.exec.ImprovedExtractionContextImpl.getJdbcConnection(ImprovedExtractionContextImpl.java:60)
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare - <linshare-backend>
at java.net.PlainSocketImpl.socketConnect(Native Method)
03:59:56.296 [DEBUG] org.apache.james.linshare.Linshare - <linshare-backend>
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Provide automated builds for Apache James - (restore builds.apache.org ?)
> --------------------------------------------------------------------------
>
> Key: JAMES-3225
> URL: https://issues.apache.org/jira/browse/JAMES-3225
> Project: James Server
> Issue Type: Task
> Reporter: Ioan Eugen Stan
> Assignee: Ioan Eugen Stan
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For a long time we had builds that ran on the Apache Infrastructure
> https://builds.apache.org/view/All/job/james-mailet/ .
> The build infrastructure is not running for ~ 3 years now.
> I believe it is important for us to have automated builds.
> This ticket should gather the work needed to make this a reality.
> There are lots of things to take into consideration.
> My ( [~ieugen] ) opinions on how to handle this.
> * builds should run automatically
> * builds should run fast < 10 min
> * there are several things they should do (not exhaustive)
> ** verify the source code
> ** compile the source code
> ** run the unit tests
> ** run the integration tests
> ** publish SNAPSHOTS (only from master or develop ?!)
> ** run code analytics
> ** publish reports relating to build
> ** provide build status for other services
> For smaller projects this is a no-brainer.
> For the current state of Apache James this is a challange, especially in the
> context of
> - multiple git branches and PR's
> - the distributed integration tests which take a long time
> Given the limited resources available for us on the Apache infrastructure we
> will have to be selective of what we do.
> Personally I don't see how we can run the current (40mni +) integration suite
> on each push / build. I'm pretty sure we will get banned :) or throttled.
> So a discussion should be in order on how to solve these issues but some
> options regarding what we can do:
> - make integration tests OPT-IN
> - run (distributed) integration tests once a day or once every 6h / 12h
> - have build profiles that build a common subset all the time and run
> The nuclear option: prune some of the components we have in James and we
> don't want to support or move them out of the common project.
> This is something we should consider especially for buggy components or for
> components that don't have a maintainer.
> We have limited time and resources.
> We can't maintain everything for everybody.
> We should be mindful of this.
> We can take inspiration from the OFBiz project
> https://builds.apache.org/view/All/job/Apache%20OFBiz/ .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
