Quarkus: [CI] - Quickstarts Native Build + Quarkus master

Created on 16 Jan 2020  路  682Comments  路  Source: quarkusio/quarkus

This issue reports the _current_ status of the quickstart development branch against Quarkus master build. This build verifies the native compilation and also runs the native integration-tests.

Don't close this issue manually. This issue will be closed when the build gets fixed. It will be re-opened if it fails again later. You can subscribe to be notify of the status.

areinfra

All 682 comments

@cescoffier we need to make people aware of this issue and subscribe to it I think

Once the PR is merged I will send an email to the list.

Unfortunately, the build failed:

Actually I'm not able to reproduce this error locally.
Is there perhaps some library we need to install on the image to make this work?

@geoand could it be the changes @gwenneg did on the default GraalVM version. Not sure what the build is using.

@emmanuelbernard it shouldn't be that because I have those changes locally as well.
CI is using 19.2.1 which is what I used

Jenkins CI also passed the Quickstarts so there is probably something missing we need to install on the workers to make SSL work

I propose that for the time being we disable the rest-client test. Otherwise we'll get too accustomed to the CI failing

SSL doesn鈥檛 work when using Docker to build an image AFAIK. That鈥檚 why we don鈥檛 have any SSL test enabled on the Azure CI.

If we want to change that, we need to use plain GraalVM.

@gsmet Ah thanks! I'll open a PR to disable it

FTR the reason is that we can鈥檛 point to the SunEc library as it鈥檚 in the Docker image.

It might be fixed with GraalVM 19.3 if everything is statically linked.

FTR the reason is that we can鈥檛 point to the SunEc library as it鈥檚 in the Docker image.

It might be fixed with GraalVM 19.3 if everything is statically linked.

Hm.. we probably can pull it out of the image and place it one the file system. But that is something that would require some trial and error

I would rather have us downloading GraalVM.

But again I think this issue might be solved by 19.3. If it is, let鈥檚 not waste time.

Here is a PR that if merged will let us know if 19.3 takes care of it or not : https://github.com/quarkusio/quarkus-quickstarts/pull/429

The build is still failing with:

The latest failure was still with 19.2.1 and not 19.3.1 so let's see if the next run will work. If not I have a PR ready to go excluding the rest-client quickstart from CI

The build is still failing with:

The build is still failing with:

https://github.com/quarkusio/quarkus-quickstarts/pull/430 is also needed :)

The build is still failing with:

According to https://github.com/quarkusio/quarkus-quickstarts/actions the last CI run for successful, so maybe there is a bug in the report part of the script?

Let's see what happens during the next run

The build is still failing with:

The build is still failing with:

Failed by "capitalization"... Testing "success", value is "Success". But the Github Actions documentation says: "The current status of the job. Possible values are success, failure, or cancelled." We should ignore the case during the test.

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is passing but unfortunately a failure is still reported to this issue

The build is still failing with:

Going to add a trace in the script to check the passed status.

Done

Cool, thanks

The build is still failing with:

The build is still failing with:

@cescoffier looking at the commit hashes (and the pipeline definition), it seems like the periodic CI is running from the development branch.
So we need to cherry pick all your CI changes to that branch

hum... ok, I've cherry-picked the commits.

The build is still failing with:

hum... ok, I've cherry-picked the commits.

Are you sure? For example 52a75e0a is missing from development

The build is still failing with:

I just cherry-picked the last fix from master and pushed to development. I think it should fix the issue

Nevermind, push was rejected since @cescoffier did it first :)

At least we got configuration about the status in the last build: Success.

Yup, we are closing in on the problem :)

Build fixed with:

Unfortunately, the build failed:

The latest failure should be fixed by https://github.com/quarkusio/quarkus/pull/6681

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

I was able to reproduce the failure with the kafka-quickstart locally

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

I am just waiting for the Qute PR to pass CI and this should be fixed

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Seems like the RSS threshold was passed...

Build fixed with:

The RSS went from 25984 kB 9 hours ago to 20080 kB 3 hours ago. That's a surprisingly huge gap for a few commits difference.

Yeah, I would guess it's probably just a system issue.

Unfortunately, the build failed:

The RSS check tripped again. @johnaohara can you pehaps take a look and see if this is an actual problem is just a false positive?

@geoand sure, looking

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

@johnaohara the RSS gate seems to be tripping pretty often... Is this an actual problem or a false positive?

Build fixed with:

Unfortunately, the build failed:

@geoand how do you know this error is the RSS issue vs just quickstarts? Should we put this subject to the forefront, if it trips every day, that's no use.

Build fixed with:

@geoand how do you know this error is the RSS issue vs just quickstarts? Should we put this subject to the forefront, if it trips every day, that's no use.

I looked at the CI logs and the step that fails is the RSS check one.
What I really want to know if we are actually seeing a jump in the RSS numbers or if it's just a testing / system issue.
I agree that if it trips often it provides no value.

So I'll let John take a look when he has some time

Unfortunately, the build failed:

RSS tripped again...

@geoand just seen these messages, looking at the history, 25MB was as a high water threshold based on testing in our lab. I will make the rss more robust by constraining the number of threads etc as that has an impact om RSS size, and we don't know the underlying architecture of the CI machines

Thanks @johnaohara !

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The Hibernate Search Quickstart is failing:

2020-03-01T06:50:26.8182925Z [INFO] -------------------------------------------------------
2020-03-01T06:50:26.8183183Z [INFO]  T E S T S
2020-03-01T06:50:26.8183612Z [INFO] -------------------------------------------------------
2020-03-01T06:50:27.4546276Z [INFO] Running org.acme.hibernate.search.elasticsearch.service.LibraryResourceTest
2020-03-01T06:50:33.6721050Z 2020-03-01 06:50:33,661 ERROR [io.qua.application] (main) Failed to start application: javax.persistence.PersistenceException: [PersistenceUnit: default] Unable to build Hibernate SessionFactory
2020-03-01T06:50:33.6721630Z    at io.quarkus.hibernate.orm.runtime.boot.FastBootEntityManagerFactoryBuilder.persistenceException(FastBootEntityManagerFactoryBuilder.java:113)
2020-03-01T06:50:33.6722270Z    at io.quarkus.hibernate.orm.runtime.boot.FastBootEntityManagerFactoryBuilder.build(FastBootEntityManagerFactoryBuilder.java:67)
2020-03-01T06:50:33.6722638Z    at io.quarkus.hibernate.orm.runtime.FastBootHibernatePersistenceProvider.createEntityManagerFactory(FastBootHibernatePersistenceProvider.java:54)
2020-03-01T06:50:33.6722960Z    at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:80)

I'll take a look eitheri tonight or tomorrow morning if no one beats me to it

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The broken Hibernate Search quickstart should be fixed by #7504

The build is still failing with:

The build is still failing with:

@geoand @emmanuelbernard I have opened a PR for the RSS regression test: https://github.com/quarkusio/quarkus-quickstarts/pull/477

This PR stores the pmap output between builds, in an IBM cloud storage bucket (GH does not provide an api to retrieve artefacts from previous builds). It fails if the RSS has grown by more than 10% (we can revisit this if there is too much variance), or if it is over 40MB. The 40MB upper limit is to stop unbounded growth of the process over time.

The PR also limits the number of threads used for the application, so should be more stable in terms of RSS usage.

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

The neo4j quickstart is now failing:

2020-03-03T19:39:59.8947523Z Executing [/home/runner/work/quarkus-quickstarts/quarkus-quickstarts/neo4j-quickstart/target/neo4j-quickstart-1.0-SNAPSHOT-runner, -Dquarkus.http.port=8081, -Dtest.url=http://localhost:8081, -Dquarkus.log.file.path=target/quarkus.log]
2020-03-03T19:39:59.9102005Z 2020-03-03 19:39:59,905 INFO  [Driver] (main) Direct driver instance 106551035 created for server address localhost:7687
2020-03-03T19:39:59.9170839Z 2020-03-03 19:39:59,914 INFO  [io.quarkus] (main) neo4j-quickstart 1.0-SNAPSHOT (running on Quarkus 999-SNAPSHOT) started in 0.016s. Listening on: http://0.0.0.0:8081
2020-03-03T19:39:59.9171621Z 2020-03-03 19:39:59,914 INFO  [io.quarkus] (main) Profile prod activated. 
2020-03-03T19:39:59.9172183Z 2020-03-03 19:39:59,914 INFO  [io.quarkus] (main) Installed features: [cdi, mutiny, neo4j, resteasy, resteasy-jsonb, resteasy-mutiny]
2020-03-03T19:40:01.0400286Z 2020-03-03 19:40:01,038 WARN  [RetryLogic] (Neo4jDriverIO-3-4) Async transaction failed and is scheduled to retry in 1008ms: org.neo4j.driver.exceptions.ServiceUnavailableException: Unable to connect to localhost:7687, ensure the database is running and that there is a working network connection to it.
2020-03-03T19:40:01.0421231Z    at org.neo4j.driver.internal.async.connection.ChannelConnectedListener.databaseUnavailableError(ChannelConnectedListener.java:76)
2020-03-03T19:40:01.0421843Z    at org.neo4j.driver.internal.async.connection.ChannelConnectedListener.operationComplete(ChannelConnectedListener.java:70)
2020-03-03T19:40:01.0422251Z    at org.neo4j.driver.internal.async.connection.ChannelConnectedListener.operationComplete(ChannelConnectedListener.java:37)
2020-03-03T19:40:01.0422457Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:577)
2020-03-03T19:40:01.0422619Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:570)
2020-03-03T19:40:01.0422847Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:549)
2020-03-03T19:40:01.0423007Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:490)
2020-03-03T19:40:01.0423163Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:615)
2020-03-03T19:40:01.0423320Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:608)
2020-03-03T19:40:01.0423472Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
2020-03-03T19:40:01.0423623Z    at org.neo4j.driver.internal.shaded.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:321)
2020-03-03T19:40:01.0423793Z    at org.neo4j.driver.internal.shaded.io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:337)
2020-03-03T19:40:01.0424121Z    at org.neo4j.driver.internal.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:688)
2020-03-03T19:40:01.0424276Z    at org.neo4j.driver.internal.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:635)
2020-03-03T19:40:01.0424431Z    at org.neo4j.driver.internal.shaded.io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:552)
2020-03-03T19:40:01.0424583Z    at org.neo4j.driver.internal.shaded.io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:514)
2020-03-03T19:40:01.0424853Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1044)
2020-03-03T19:40:01.0428013Z    at org.neo4j.driver.internal.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
2020-03-03T19:40:01.0429591Z    at org.neo4j.driver.internal.shaded.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
2020-03-03T19:40:01.0452508Z    at java.lang.Thread.run(Thread.java:748)
2020-03-03T19:40:01.0452856Z    at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:497)
2020-03-03T19:40:01.0453116Z    at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193)
2020-03-03T19:40:01.0453385Z Caused by: org.neo4j.driver.internal.shaded.io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: localhost/127.0.0.1:7687

The issue seems to have to do with some changes in the quickstart itself (its test code), not Quarkus itself. PR to revert the changes is here

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

RSS check tripped

Build fixed with:

Looked at the RSS trip. Master is using the old workflow, not the new check. What we need to do is patch the master branch with the new workflow. Although the test checks out the development branch, it runs the workflow from the master branch. What is the process for updating master? or we need to see if we can configure just workflow to run from the development branch

We can just cherry pick the RSS commit from development to master. I don't think I have the karma to push to master on the quickstarts, so @cescoffier can you please do that?

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

RSS tripped again

We're still running the old check, need to get the new check into master

@johnaohara do you have the karma to cherry-pick it into master, or do we need @cescoffier to do that?

i'll take a look

The build is still failing with:

Can we make sure that the RSS consumption is secured for 1.3 e.g. before
Thursday evening?

Thanks!

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

@johnaohara the master branch of the quickstarts has been updated with the RSS change but the check seems to consistently trip. Can you take a look when you have some time?

Thanks

@geoand sure it is failing to upload the new pmap file, I will look at why it is failing

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

@geoand PR open to fix the failing RSS check: https://github.com/quarkusio/quarkus-quickstarts/pull/507

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

@johnaohara It seem that after a couple of green runs, the RSS is now red. Here is the output:

Downloading file from storage: pmap.out to local: pmap.old.out
Old RSS: 20796
New RSS: 22896
Regression: true
Uploading new pmap file to storage: pmap.out from local: pmap.old.out
##[error]Process completed with exit code 1.

So this now looks like a genuine failure?

@geoand Yes, this is a genuine failure, although it was only just larger than the 10%, I am thinking we might want to run a number of times and take an average to remove variances in RSS

I think that is a good idea

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

It's OpenTracing failing, will open an issue.

Was going to check out why it failed in the morning

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

security-openid-connect-web-authentication-quickstart failed with

2020-04-16T08:37:55.9336790Z [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.347 s <<< FAILURE! - in org.acme.security.openid.connect.web.authentication.NativeCodeFlowIT
2020-04-16T08:37:55.9345953Z [ERROR] org.acme.security.openid.connect.web.authentication.NativeCodeFlowIT  Time elapsed: 2.347 s  <<< FAILURE!
2020-04-16T08:37:55.9351233Z java.lang.AssertionError: Docker environment should have more than 2GB free disk space

@cescoffier I assume this is something you have seen before?

@geoand Yes.

I would recommend a run a few prune command before the test:

docker volume prune
docker image prune
docker network prune

It may not be enough, but it should reclaim some spaces.

The issue is that the "agents" are running out of space (on the main partition). I also had the issue with AMQP (that requires at least 20% of disk space by default).

Thanks @cescoffier, I'll see to it to add these commands before the test maven build starts.

@geoand There command requires confirmation. Use them with yes.

Yup, I will add -f :)

Unfortunately, the build failed:

The build is still failing with:

@sberyozkin Same issue as our Jenkins is seeing:

2020-04-17T02:12:21.7885769Z [INFO] Running org.acme.security.jwt.TokenSecuredResourceTest
2020-04-17T02:12:25.9237682Z 2020-04-17 02:12:23,988 WARN  [io.qua.dep.QuarkusAugmentor] (main) Using Java versions older than 11 to build Quarkus applications is deprecated and will be disallowed in a future release!
2020-04-17T02:12:26.2565264Z 2020-04-17 02:12:26,255 INFO  [io.quarkus] (main) Quarkus 999-SNAPSHOT started in 2.350s. Listening on: http://0.0.0.0:8081
2020-04-17T02:12:26.2569007Z 2020-04-17 02:12:26,256 INFO  [io.quarkus] (main) Profile test activated. 
2020-04-17T02:12:26.2569780Z 2020-04-17 02:12:26,256 INFO  [io.quarkus] (main) Installed features: [cdi, mutiny, resteasy, resteasy-jsonb, security, smallrye-jwt, vertx, vertx-web]
2020-04-17T02:12:28.3243267Z [ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.531 s <<< FAILURE! - in org.acme.security.jwt.TokenSecuredResourceTest
2020-04-17T02:12:28.3247800Z [ERROR] testHelloEndpoint  Time elapsed: 0.095 s  <<< FAILURE!
2020-04-17T02:12:28.3249887Z java.lang.AssertionError: 
2020-04-17T02:12:28.3251647Z 1 expectation failed.
2020-04-17T02:12:28.3254536Z Response body doesn't match expectation.
2020-04-17T02:12:28.3260097Z Expected: a string containing "hello + anonymous, isSecure: false, authScheme: null, hasJWT: false"
2020-04-17T02:12:28.3264149Z   Actual: hello + , isSecure: false, authScheme: null, hasJWT: false
2020-04-17T02:12:28.3264843Z 
2020-04-17T02:12:28.3270710Z    at org.acme.security.jwt.TokenSecuredResourceTest.testHelloEndpoint(TokenSecuredResourceTest.java:47)
2020-04-17T02:12:28.3271414Z 

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

@sberyozkin It seems like CI is failing when testing the development branch of the Quickstarts. The failure is:

2020-04-21T02:27:46.6973746Z [ERROR] Failures: 
2020-04-21T02:27:46.6976231Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testHelloDenyAll:69 expected: <403> but was: <401>
2020-04-21T02:27:46.6977503Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testHelloRolesAllowed:58 1 expectation failed.
2020-04-21T02:27:46.6977978Z Expected status code <200> but was <401>.
2020-04-21T02:27:46.6978426Z 
2020-04-21T02:27:46.6979237Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testWinners:79 expected: <false> but was: <true>
2020-04-21T02:27:46.6980667Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testWinnersWithBirthdate:89 expected: <200> but was: <401>
2020-04-21T02:27:46.6981078Z [INFO] 
2020-04-21T02:27:46.6981728Z [ERROR] Tests run: 6, Failures: 4, Errors: 0, Skipped: 1
2020-04-21T02:27:46.6982027Z [INFO] 
2020-04-21T02:27:46.7019643Z [INFO] 
2020-04-21T02:27:46.7026028Z [INFO] --- maven-failsafe-plugin:2.22.1:verify (default) @ security-jwt-quickstart ---

Can you please take a look?

Thanks!

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

@pedroigor @sberyozkin a couple of the openid quickstarts are still failing:

2020-04-22T03:23:28.0801991Z [INFO] security-openid-connect-web-authentication-quickstart FAILURE [04:44 min]
2020-04-22T03:23:28.0802717Z [INFO] security-openid-connect-multi-tenancy-quickstart ... FAILURE [  3.026 s]

can you please take a look?

The build is still failing with:

The build is still failing with:

@cescoffier CI is reporting an issue with Kafka:

2020-04-22T13:14:38.8063941Z Error: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Invoke with MethodHandle argument could not be reduced to at most a single call or single field access. The method handle must be a compile time constant, e.g., be loaded from a `static final` field. Method that contains the method handle invocation: java.lang.invoke.LambdaForm$MH/1297919118.invokeExact_MT(Object, Object, Object)
2020-04-22T13:14:38.8064720Z To diagnose the issue, you can add the option --report-unsupported-elements-at-runtime. The error is then reported at run time when the invoke is executed.
2020-04-22T13:14:38.8065068Z Detailed message:
2020-04-22T13:14:38.8065221Z Trace: 
2020-04-22T13:14:38.8065368Z    at parsing org.apache.kafka.common.utils.ByteBufferUnmapper.unmap(ByteBufferUnmapper.java:81)
2020-04-22T13:14:38.8065699Z Call path from entry point to org.apache.kafka.common.utils.ByteBufferUnmapper.unmap(String, ByteBuffer): 
2020-04-22T13:14:38.8065864Z    at org.apache.kafka.common.utils.ByteBufferUnmapper.unmap(ByteBufferUnmapper.java:75)
2020-04-22T13:14:38.8066033Z    at org.apache.kafka.common.network.SslTransportLayer.close(SslTransportLayer.java:206)
2020-04-22T13:14:38.8066190Z    at java.io.FileDescriptor.closeAll(FileDescriptor.java:202)
2020-04-22T13:14:38.8066351Z    at java.io.FileInputStream.close(FileInputStream.java:334)
2020-04-22T13:14:38.8066500Z    at sun.nio.ch.FileChannelImpl.implCloseChannel(FileChannelImpl.java:139)
2020-04-22T13:14:38.8066667Z    at java.nio.channels.spi.AbstractInterruptibleChannel$1.interrupt(AbstractInterruptibleChannel.java:165)
2020-04-22T13:14:38.8066820Z    at java.lang.Thread.interrupt(Thread.java:922)
2020-04-22T13:14:38.8066970Z    at java.io.PrintStream.newLine(PrintStream.java:552)
2020-04-22T13:14:38.8067112Z    at java.io.PrintStream.println(PrintStream.java:807)
2020-04-22T13:14:38.8067263Z    at com.oracle.svm.jni.functions.JNIFunctions.ExceptionDescribe(JNIFunctions.java:750)
2020-04-22T13:14:38.8067442Z    at com.oracle.svm.core.code.IsolateEnterStub.JNIFunctions_ExceptionDescribe_b5412f7570bccae90b000bc37855f00408b2ad73(generated:0)

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Seems like the vert-x quickstart no longer compiles:

2020-04-23T14:57:55.0158196Z [ERROR] /home/runner/work/quarkus-quickstarts/quarkus-quickstarts/vertx-quickstart/src/main/java/org/acme/vertx/Fruit.java:[70,22] no suitable method found for preparedQuery(java.lang.String,io.vertx.mutiny.sqlclient.Tuple)
2020-04-23T14:57:55.0160876Z     method io.vertx.mutiny.sqlclient.SqlClient.preparedQuery(java.lang.String) is not applicable
2020-04-23T14:57:55.0161791Z       (actual and formal argument lists differ in length)
2020-04-23T14:57:55.0162012Z     method io.vertx.mutiny.sqlclient.Pool.preparedQuery(java.lang.String) is not applicable
2020-04-23T14:57:55.0164441Z       (actual and formal argument lists differ in length)

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

@sberyozkin can you take a look at the latest failure:

2020-04-27T08:35:48.2895965Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testHelloDenyAll:69 expected: <403> but was: <401>
2020-04-27T08:35:48.2896701Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testHelloRolesAllowed:58 1 expectation failed.
2020-04-27T08:35:48.2897263Z Expected status code <200> but was <401>.
2020-04-27T08:35:48.2897555Z 
2020-04-27T08:35:48.2899000Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testWinners:79 expected: <false> but was: <true>
2020-04-27T08:35:48.2901199Z [ERROR]   TokenSecuredResourceIT>TokenSecuredResourceTest.testWinnersWithBirthdate:89 expected: <200> but was: <401>

Thanks

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Is that still the security test failing ? We have decided to disable it temporarily.

The latest failure is because of limited disk space. https://github.com/quarkusio/quarkus-quickstarts/pull/549 should take care of it

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

I reproduced the latest failure, https://github.com/quarkusio/quarkus-quickstarts/pull/555 should fix it

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

This was a tripped RSS check, will look to see if it is a genuine regression. I have asked @barreiro to improve the regression testing by averaging over a number of startups to reduce the number of false +ves. Also looking at adding some simple load testing to catch early throughput/response time regressions as well.

Thanks for checking @johnaohara

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

@cescoffier seems like the vertx quickstart is now failing:

io.vertx.ext.web.handler.sockjs.BridgeOptions cannot be applied to given types;
2020-05-25T15:55:01.1939562Z [ERROR]   required: io.vertx.core.json.JsonObject
2020-05-25T15:55:01.1940948Z [ERROR]   found: no arguments
2020-05-25T15:55:01.1942547Z [ERROR]   reason: actual and formal argument lists differ in length

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

@patriot1burke @matejvasek the funqy-amazon-lambda-http-quickstart quickstart (in the development branch) seems to be failing:

2020-05-27T07:03:32.1668546Z 2020-05-27 07:03:31,995 ERROR [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread) Failed to run lambda: java.net.UnknownHostException: null
2020-05-27T07:03:32.1668834Z    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
2020-05-27T07:03:32.1672014Z    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
2020-05-27T07:03:32.1672281Z    at java.net.Socket.connect(Socket.java:607)
2020-05-27T07:03:32.1672500Z    at java.net.Socket.connect(Socket.java:556)
2020-05-27T07:03:32.1672732Z    at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
2020-05-27T07:03:32.1675576Z    at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
2020-05-27T07:03:32.1675846Z    at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
2020-05-27T07:03:32.1676075Z    at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
2020-05-27T07:03:32.1676308Z    at sun.net.www.http.HttpClient.New(HttpClient.java:339)
2020-05-27T07:03:32.1678877Z    at sun.net.www.http.HttpClient.New(HttpClient.java:357)
2020-05-27T07:03:32.1679072Z    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
2020-05-27T07:03:32.1679270Z    at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
2020-05-27T07:03:32.1679463Z    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
2020-05-27T07:03:32.1682271Z    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
2020-05-27T07:03:32.1682474Z    at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570)
2020-05-27T07:03:32.1682795Z    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1498)
2020-05-27T07:03:32.1686723Z    at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:3061)
2020-05-27T07:03:32.1686971Z    at io.quarkus.amazon.lambda.runtime.AbstractLambdaPollLoop$1.run(AbstractLambdaPollLoop.java:50)
2020-05-27T07:03:32.1687161Z    at java.lang.Thread.run(Thread.java:748)
2020-05-27T07:03:32.1687352Z    at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:497)
2020-05-27T07:03:32.1690792Z    at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193)
2020-05-27T07:03:32.1690967Z 
2020-05-27T07:03:32.1691599Z 2020-05-27 07:03:31,997 ERROR [io.qua.ama.lam.run.AbstractLambdaPollLoop] (Lambda Thread) Error running lambda: java.net.UnknownHostException: null
2020-05-27T07:03:32.1691825Z    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
2020-05-27T07:03:32.1695549Z    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
2020-05-27T07:03:32.1695886Z    at java.net.Socket.connect(Socket.java:607)
2020-05-27T07:03:32.1696076Z    at java.net.Socket.connect(Socket.java:556)
2020-05-27T07:03:32.1696266Z    at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
2020-05-27T07:03:32.1700230Z    at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
2020-05-27T07:03:32.1700521Z    at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
2020-05-27T07:03:32.1700719Z    at sun.net.www.http.HttpClient.<init>(HttpClient.java:242)
2020-05-27T07:03:32.1700910Z    at sun.net.www.http.HttpClient.New(HttpClient.java:339)
2020-05-27T07:03:32.1703927Z    at sun.net.www.http.HttpClient.New(HttpClient.java:357)
2020-05-27T07:03:32.1704141Z    at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1226)
2020-05-27T07:03:32.1704358Z    at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162)
2020-05-27T07:03:32.1704570Z    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056)
2020-05-27T07:03:32.1708651Z    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:990)
2020-05-27T07:03:32.1708866Z    at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1340)
2020-05-27T07:03:32.1709089Z    at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1315)
2020-05-27T07:03:32.1709316Z    at io.quarkus.amazon.lambda.runtime.AbstractLambdaPollLoop.postError(AbstractLambdaPollLoop.java:164)
2020-05-27T07:03:32.1712823Z    at io.quarkus.amazon.lambda.runtime.AbstractLambdaPollLoop$1.run(AbstractLambdaPollLoop.java:75)
2020-05-27T07:03:32.1713026Z    at java.lang.Thread.run(Thread.java:748)
2020-05-27T07:03:32.1713226Z    at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:497)
2020-05-27T07:03:32.1715918Z    at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193)

I am going to look at it.

Thanks

  1. The reason why native test is failing and JVM is not, is that the failing code in not enabled in JVM mode. That can be change by setting property quarkus.lambda.enable-polling-jvm-mode=true.
  2. The reason why it is throwing UnknownHostException is that the aws lambda environment emulation is not set up. That can be changed by adding dep. to pom:
        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-test-amazon-lambda</artifactId>
            <scope>test</scope>
        </dependency>
  1. @patriot1burke I really don't know how the example is supposed to work. To me it looks like that the funqy-amazon-lambda-http-quickstart mixes up two different run-times.

The build is still failing with:

The build is still failing with:

@geoand If you just need to fix build I think that adding the dependency should do the job. But I don't know if there is some other issue.

I think the native test needs to be removed. I don't think we have a test harness for HTTP amazon native mode.

The build is still failing with:

@matejvasek @patriot1burke I'm fine with adding a dependency and disabling the test in native. @matejvasek would you please prepare a PR against the developement branch?

The build is still failing with:

@geoand @matejvasek Have to remove the native test as we do not support aws lambda HTTP native testing:

https://github.com/quarkusio/quarkus-quickstarts/pull/588

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The JMS quickstart might be a little flaky @cescoffier

-06-02T07:51:23.3509508Z 2020-06-02 07:51:23,164 INFO  [org.apa.act.art.cor.server] (main) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.11.0 [localhost, nodeID=da3e0cf2-a4a5-11ea-b790-000d3a1f67e1] 
2020-06-02T07:51:23.4660918Z 2020-06-02 07:51:23,461 INFO  [io.quarkus] (main) Quarkus 999-SNAPSHOT on JVM started in 2.612s. Listening on: http://0.0.0.0:8081
2020-06-02T07:51:23.4661727Z 2020-06-02 07:51:23,461 INFO  [io.quarkus] (main) Profile test activated. 
2020-06-02T07:51:23.4662263Z 2020-06-02 07:51:23,461 INFO  [io.quarkus] (main) Installed features: [artemis-jms, cdi, resteasy]
2020-06-02T07:51:24.7606794Z [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.978 s <<< FAILURE! - in org.acme.jms.PriceTest
2020-06-02T07:51:24.7607425Z [ERROR] testLastPrice  Time elapsed: 1.258 s  <<< FAILURE!
2020-06-02T07:51:24.7608284Z java.lang.AssertionError: 
2020-06-02T07:51:24.7609119Z 1 expectation failed.
2020-06-02T07:51:24.7610234Z Expected status code <200> but was <204>.
2020-06-02T07:51:24.7610572Z 
2020-06-02T07:51:24.7612394Z    at org.acme.jms.PriceTest.testLastPrice(PriceTest.java:21)

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

The build is still failing with:

@cescoffier you will definitely like this failure:

2020-06-04T02:08:35.2136119Z 2020-06-04 02:08:35,210 INFO  [io.qua.grp.run.GrpcSslUtils] (main) Disabling gRPC plain-text as the SSL certificate is configured
2020-06-04T02:08:35.2149660Z 2020-06-04 02:08:35,213 INFO  [io.qua.grp.run.GrpcServerRecorder] (main) Registering gRPC reflection service
2020-06-04T02:08:35.2155917Z 2020-06-04 02:08:35,214 ERROR [io.qua.application] (main) Failed to start application: io.vertx.core.VertxException: ALPN not available for JDK SSL/TLS engine
2020-06-04T02:08:35.2161001Z    at io.vertx.core.net.impl.SSLHelper.resolveEngineOptions(SSLHelper.java:88)
2020-06-04T02:08:35.2164396Z    at io.vertx.core.net.impl.SSLHelper.<init>(SSLHelper.java:155)
2020-06-04T02:08:35.2167194Z    at io.vertx.grpc.VertxServer$ActualServer.<init>(VertxServer.java:59)
2020-06-04T02:08:35.2167621Z    at io.vertx.grpc.VertxServer$ActualServer.<init>(VertxServer.java:41)
2020-06-04T02:08:35.2170946Z    at io.vertx.grpc.VertxServer.lambda$start$1(VertxServer.java:160)
2020-06-04T02:08:35.2174642Z    at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1660)
2020-06-04T02:08:35.2174872Z    at io.vertx.grpc.VertxServer.start(VertxServer.java:160)
2020-06-04T02:08:35.2182460Z    at io.quarkus.grpc.runtime.GrpcServerRecorder.initializeGrpcServer(GrpcServerRecorder.java:118)
2020-06-04T02:08:35.2192511Z    at io.quarkus.deployment.steps.GrpcServerProcessor$build215158828.deploy_0(GrpcServerProcessor$build215158828.zig:90)
2020-06-04T02:08:35.2195625Z    at io.quarkus.deployment.steps.GrpcServerProcessor$build215158828.deploy(GrpcServerProcessor$build215158828.zig:36)
2020-06-04T02:08:35.2198611Z    at io.quarkus.runner.ApplicationImpl.doStart(ApplicationImpl.zig:354)
2020-06-04T02:08:35.2207772Z    at io.quarkus.runtime.Application.start(Application.java:90)
2020-06-04T02:08:35.2213940Z    at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:91)
2020-06-04T02:08:35.2219506Z    at io.quarkus.runtime.Quarkus.run(Quarkus.java:61)
2020-06-04T02:08:35.2223866Z    at io.quarkus.runtime.Quarkus.run(Quarkus.java:38)
2020-06-04T02:08:35.2228369Z    at io.quarkus.runtime.Quarkus.run(Quarkus.java:106)
2020-06-04T02:08:35.2236512Z    at io.quarkus.runner.GeneratedMain.main(GeneratedMain.zig:29)

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

Build fixed with:

Unfortunately, the build failed:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing with:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

@michalszynkiewicz this is failing with:

2020-08-25T06:14:00.7919765Z [ERROR] Failed to execute goal org.xolstice.maven.plugins:protobuf-maven-plugin:0.6.1:compile (compile) on project grpc-plain-text-quickstart: Unable to resolve artifact: Unable to get dependency information for com.google.protobuf:protoc:exe:linux-x86_64:3.11.4: Failed to retrieve POM for com.google.protobuf:protoc:exe:linux-x86_64:3.11.4: Could not transfer artifact com.google.protobuf:protoc:pom:3.11.4 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/com/google/protobuf/protoc/3.11.4/protoc-3.11.4.pom

Can you take a look please?

@geoand thanks for mentioning me.
The URL for th epom file works well for me. Is the CI job executed behind some proxy?

Not that I know of. It's just a cron job running on GH Actions

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

@cescoffier it seems like the JMS quickstart is failing:

2020-08-30T20:36:05.4519222Z [ERROR] Failures: 
2020-08-30T20:36:05.4519664Z [ERROR]   PriceTestIT>PriceTest.testLastPrice:21 1 expectation failed.
2020-08-30T20:36:05.4523602Z Expected status code <200> but was <204>.

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The jms-quickstart seems to be flaky @cescoffier

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

@machi1990 it seems like the redis-quickstart is failing:

2020-09-18T03:38:27.0425662Z [INFO] Running org.acme.redis.IncrementResourceTest
2020-09-18T03:38:31.3071002Z 2020-09-18 03:38:31,298 DEBUG [io.net.uti.int.PlatformDependent] (Thread-69) -Dio.netty.maxDirectMemory: -1 bytes
2020-09-18T03:38:31.5565977Z 2020-09-18 03:38:31,552 INFO  [io.quarkus] (main) Quarkus 999-SNAPSHOT on JVM started in 2.171s. Listening on: http://0.0.0.0:8081
2020-09-18T03:38:31.5566905Z 2020-09-18 03:38:31,552 INFO  [io.quarkus] (main) Profile test activated. 
2020-09-18T03:38:31.5568176Z 2020-09-18 03:38:31,552 INFO  [io.quarkus] (main) Installed features: [cdi, mutiny, redis-client, resteasy, resteasy-jsonb, resteasy-mutiny, smallrye-context-propagation, vertx]
2020-09-18T03:38:32.8352800Z 2020-09-18 03:38:32,826 ERROR [org.jbo.res.res.i18n] (executor-thread-1) RESTEASY002020: Unhandled asynchronous exception, sending back 500: java.lang.IllegalArgumentException: Unsupported Redis connection string scheme [localhost]
2020-09-18T03:38:32.8354705Z    at io.vertx.redis.client.impl.RedisURI.<init>(RedisURI.java:89)

Can you please take a look?

@geoand thanks for mentioning this. Can you take a look at https://github.com/quarkusio/quarkus-quickstarts/pull/659? Thanks. I'll update the docs in quarkus side too.

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

@marcinczeczko it seems like the KMS extension is failing. Can you please take a look?

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

Unfortunately, the build failed:

Anyone has any clue at why I'm flagged as having closed this?

All I did was to synch my personal fork (of the quickstarts) with upstream.

Weird... I've actually seen that happen before but I can't remember the circumstances

The build is still failing:

The build is still failing:

The build is still failing:

i bet the auto closer don't have a check in place its actually run in the rigt repo.

The build is still failing:

The build is still failing:

The build is still failing:

@DavideD it seems that the Hibernate Reactive quickstart no longer compiles:

2020-09-22T23:09:08.3653008Z [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project hibernate-reactive-quickstart: Compilation failure: Compilation failure: 
2020-09-22T23:09:08.3663902Z [ERROR] /home/runner/work/quarkus-quickstarts/quarkus-quickstarts/hibernate-reactive-quickstart/src/main/java/org/acme/hibernate/reactive/FruitMutinyResource.java:[81,25] no suitable method found for transformToUni(java.util.function.Function<org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<javax.ws.rs.core.Response>>)
2020-09-22T23:09:08.3672500Z [ERROR]     method io.smallrye.mutiny.groups.UniOnNotNull.<R>transformToUni(java.util.function.Function<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<? extends R>>) is not applicable
2020-09-22T23:09:08.3678064Z [ERROR]       (cannot infer type-variable(s) R
2020-09-22T23:09:08.3687038Z [ERROR]         (argument mismatch; java.util.function.Function<org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<javax.ws.rs.core.Response>> cannot be converted to java.util.function.Function<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<? extends R>>))
2020-09-22T23:09:08.3696752Z [ERROR]     method io.smallrye.mutiny.groups.UniOnNotNull.<R>transformToUni(java.util.function.BiConsumer<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.subscription.UniEmitter<? super R>>) is not applicable
2020-09-22T23:09:08.3701420Z [ERROR]       (cannot infer type-variable(s) R
2020-09-22T23:09:08.3711842Z [ERROR]         (argument mismatch; java.util.function.Function<org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<javax.ws.rs.core.Response>> cannot be converted to java.util.function.BiConsumer<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.subscription.UniEmitter<? super R>>))
2020-09-22T23:09:08.3726183Z [ERROR] /home/runner/work/quarkus-quickstarts/quarkus-quickstarts/hibernate-reactive-quickstart/src/main/java/org/acme/hibernate/reactive/FruitMutinyResource.java:[99,25] no suitable method found for transformToUni(java.util.function.Function<org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<javax.ws.rs.core.Response>>)
2020-09-22T23:09:08.3734651Z [ERROR]     method io.smallrye.mutiny.groups.UniOnNotNull.<R>transformToUni(java.util.function.Function<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<? extends R>>) is not applicable
2020-09-22T23:09:08.3738946Z [ERROR]       (cannot infer type-variable(s) R
2020-09-22T23:09:08.3748295Z [ERROR]         (argument mismatch; java.util.function.Function<org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<javax.ws.rs.core.Response>> cannot be converted to java.util.function.Function<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<? extends R>>))
2020-09-22T23:09:08.3758699Z [ERROR]     method io.smallrye.mutiny.groups.UniOnNotNull.<R>transformToUni(java.util.function.BiConsumer<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.subscription.UniEmitter<? super R>>) is not applicable
2020-09-22T23:09:08.3763590Z [ERROR]       (cannot infer type-variable(s) R
2020-09-22T23:09:08.3773859Z [ERROR]         (argument mismatch; java.util.function.Function<org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.Uni<javax.ws.rs.core.Response>> cannot be converted to java.util.function.BiConsumer<? super org.acme.hibernate.reactive.Fruit,io.smallrye.mutiny.subscription.UniEmitter<? super R>>))
2020-09-22T23:09:08.3779122Z [ERROR] -> [Help 1]
2020-09-22T23:09:08.3780620Z [ERROR] 
2020-09-22T23:09:08.3784590Z [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2020-09-22T23:09:08.3793320Z [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2020-09-22T23:09:08.3796878Z [ERROR] 
2020-09-22T23:09:08.3801189Z [ERROR] For more information about the errors and possible solutions, please read the following articles:
2020-09-22T23:09:08.3820400Z [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

Can you have a look please?

@cescoffier Could this be a problem with quarkus-resteasy-mutiny? In the code I'm using .ifNotNull().transformToUni(...). I don't see this error on my machine. I'm not sure what could be different.

The build is still failing:

The build is still failing:

Thanks @Sanne

The build is still failing:

I am seeing:

Error:  Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 46.741 s <<< FAILURE! - in org.acme.kms.NativeKmsResourcesIT
Error:  org.acme.kms.NativeKmsResourcesIT.testResource(String)[2]  Time elapsed: 30.039 s  <<< ERROR!
java.net.SocketTimeoutException: Read timed out

2020-09-23 18:43:59,587 ERROR [org.jbo.res.res.i18n] (aws-java-sdk-NettyEventLoop-2-2) RESTEASY002020: Unhandled asynchronous exception, sending back 500: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: The channel was closed. This may have been done by the client (e.g. because the request was aborted), by the service (e.g. because the request took too long or the client tried to write on a read-only socket), or by an intermediary party (e.g. because the channel was idle for too long).

in KMS quickstart

The build is still failing:

@geoand yes, and I've seen the same in JVM mode.

Unfortunately I have no idea what the problem is since I've never touched the Amazon stuff...

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

@cescoffier the jms quickstart seems to be misbehaving

Again? Hum... at some point we may have to drop it completely.

Hum, it seems that the broker is no more running in native...

It does not seem to be the case. I've opened https://github.com/quarkusio/quarkus-quickstarts/pull/669, but definitely not sure it will fix it. Obviously, no problems on my machine.

The build is still failing:

The build is still failing:

My attempt to fix KMS tests failing: quarkusio/quarkus-quickstarts#674

The build is still failing:

The build is still failing:

The build is still failing:

Another JMS (204) issue...

The build is still failing:

@DavideD the hibernate-reactive-routes-quickstart is failing. Can you have look please?

The build is still failing:

Unfortunately, the build failed:

Unfortunately, the build failed:

Unfortunately, the build failed:

The build is still failing:

Seems like the job is failing when trying to install JDK 11

The build is still failing:

Unfortunately, the build failed:

The build is still failing:

The build is still failing:

The build is still failing:

@ge0ffrey the OptaPlanner quickstart is failing:

2020-11-30T05:01:42.6099773Z [INFO] Running org.acme.optaplanner.rest.TimeslotResourceIT
2020-11-30T05:01:43.2692947Z [INFO] H2 database started in TCP server mode; server status: TCP server running at tcp://10.1.0.4:9092 (only local connections)
2020-11-30T05:01:43.2697345Z Executing [/home/runner/work/quarkus-quickstarts/quarkus-quickstarts/optaplanner-quickstart/target/optaplanner-quickstart-1.0-SNAPSHOT-runner, -Dquarkus.http.port=8081, -Dquarkus.http.ssl-port=8444, -Dtest.url=http://localhost:8081, -Dquarkus.log.file.path=target/target/quarkus.log]
2020-11-30T05:01:43.2702328Z __  ____  __  _____   ___  __ ____  ______ 
2020-11-30T05:01:43.2703619Z  --/ __ \/ / / / _ | / _ \/ //_/ / / / __/ 
2020-11-30T05:01:43.2705328Z  -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \   
2020-11-30T05:01:43.2706600Z --\___\_\____/_/ |_/_/|_/_/|_|\____/___/   
2020-11-30T05:01:43.2710769Z 2020-11-30 05:01:43,167 WARN  [io.agr.pool] (agroal-11) Datasource '<default>': General error: "java.lang.UnsupportedOperationException: H2 database compiled into a native-image is only functional as a client: can't create an Embedded Database Session" [50000-197]
2020-11-30T05:01:43.2716820Z 2020-11-30 05:01:43,168 WARN  [org.hib.eng.jdb.env.int.JdbcEnvironmentInitiator] (main) HHH000342: Could not obtain connection to query metadata: org.h2.jdbc.JdbcSQLException: General error: "java.lang.UnsupportedOperationException: H2 database compiled into a native-image is only functional as a client: can't create an Embedded Database Session" [50000-197]
2020-11-30T05:01:43.2725004Z    at org.h2.message.TraceObject.logAndConvert(TraceObject.java:357)
2020-11-30T05:01:43.2730569Z    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:140)
2020-11-30T05:01:43.2731841Z    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:103)
2020-11-30T05:01:43.2733189Z    at org.h2.Driver.connect(Driver.java:69)
2020-11-30T05:01:43.2735403Z    at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:200)
2020-11-30T05:01:43.2743219Z    at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:452)
2020-11-30T05:01:43.2744975Z    at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:434)
2020-11-30T05:01:43.2749810Z    at java.util.concurrent.FutureTask.run(FutureTask.java:264)
2020-11-30T05:01:43.2759444Z    at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:65)
2020-11-30T05:01:43.2761994Z    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1126)
2020-11-30T05:01:43.2763960Z    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2020-11-30T05:01:43.2777534Z    at java.lang.Thread.run(Thread.java:834)
2020-11-30T05:01:43.2783827Z    at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:517)
2020-11-30T05:01:43.2787560Z    at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193)
2020-11-30T05:01:43.2793890Z Caused by: java.lang.UnsupportedOperationException: H2 database compiled into a native-image is only functional as a client: can't create an Embedded Database Session
2020-11-30T05:01:43.2799110Z    at org.h2.engine.ConnectionInfo.isRemote(ConnectionInfo.java:20)
2020-11-30T05:01:43.2803219Z    at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:331)
2020-11-30T05:01:43.2807713Z    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:124)
2020-11-30T05:01:43.2816446Z    ... 12 more
2020-11-30T05:01:43.2816742Z 
2020-11-30T05:01:43.2829528Z 2020-11-30 05:01:43,174 WARN  [io.agr.pool] (agroal-11) Datasource '<default>': General error: "java.lang.UnsupportedOperationException: H2 database compiled into a native-image is only functional as a client: can't create an Embedded Database Session" [50000-197]
2020-11-30T05:01:43.2835069Z 2020-11-30 05:01:43,174 WARN  [org.hib.eng.jdb.spi.SqlExceptionHelper] (main) SQL Error: 50000, SQLState: HY000
2020-11-30T05:01:43.2849842Z 2020-11-30 05:01:43,174 ERROR [org.hib.eng.jdb.spi.SqlExceptionHelper] (main) General error: "java.lang.UnsupportedOperationException: H2 database compiled into a native-image is only functional as a client: can't create an Embedded Database Session" [50000-197]
2020-11-30T05:01:43.2860183Z 2020-11-30 05:01:43,175 ERROR [io.qua.run.Application] (main) Failed to start application (with profile prod): java.lang.UnsupportedOperationException: H2 database compiled into a native-image is only functional as a client: can't create an Embedded Database Session
2020-11-30T05:01:43.2862472Z    at org.h2.engine.ConnectionInfo.isRemote(ConnectionInfo.java:20)
2020-11-30T05:01:43.2867669Z    at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:331)
2020-11-30T05:01:43.2871827Z    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:124)
2020-11-30T05:01:43.2873532Z    at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:103)
2020-11-30T05:01:43.2874514Z    at org.h2.Driver.connect(Driver.java:69)
2020-11-30T05:01:43.2879942Z    at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:200)
2020-11-30T05:01:43.2882945Z    at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:452)
2020-11-30T05:01:43.2887948Z    at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:434)
2020-11-30T05:01:43.2889719Z    at java.util.concurrent.FutureTask.run(FutureTask.java:264)
2020-11-30T05:01:43.2892568Z    at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:65)
2020-11-30T05:01:43.2895867Z    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1126)
2020-11-30T05:01:43.2898369Z    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2020-11-30T05:01:43.2899963Z    at java.lang.Thread.run(Thread.java:834)
2020-11-30T05:01:43.2901519Z    at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:517)
2020-11-30T05:01:43.2904655Z    at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:193)
2020-11-30T05:01:43.2906803Z 
2020-11-30T05:01:43.3441230Z [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.665 s <<< FAILURE! - in org.acme.optaplanner.rest.TimeslotResourceIT
2020-11-30T05:01:43.3443278Z [ERROR] org.acme.optaplanner.rest.TimeslotResourceIT  Time elapsed: 0.665 s  <<< ERROR!
2020-11-30T05:01:43.3445408Z org.junit.platform.commons.JUnitException: Quarkus native image start failed, original cause: java.lang.RuntimeException: Failed to start native image, process has exited
2020-11-30T05:01:43.3447270Z Caused by: java.lang.RuntimeException: Failed to start native image, process has exited

Can you please take a look?

The build is still failing:

Taking a look, thanks for letting me know @geoand

Is it possible that this CI job doesn't do the normal -Dnative for native jobs?

Because it looks like our quarkus profile native isn't activated:
https://github.com/quarkusio/quarkus-quickstarts/blob/master/optaplanner-quickstart/pom.xml#L184
And it doesn't pick up this line in application.properties:
https://github.com/quarkusio/quarkus-quickstarts/blob/master/optaplanner-quickstart/src/main/resources/application.properties#L50

It fails locally too, somehow this slipped through on my end. Working on it.

Related conversation: https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/-Dnative.20ignores.20my.20quarkus.2Eprofile

Ah, I realize what is causing this.
Basically, until https://github.com/quarkusio/quarkus/issues/13341 is fixed, the user has to add -Dquarkus.profile=native on the command line too. Obviously that's not ok for the CI here, so I 'll revert my changes that switched to this approach (and deviate from how we do it on optaplanner itself). Fix PR coming soon.

@geoand Here's the fix: https://github.com/quarkusio/quarkus-quickstarts/pull/722
My apologies for the disruption

@ge0ffrey thanks for the fix!

Not a problem at all :)

Unfortunately, the build failed:

"Error: Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M5:verify (default) on project kafka-streams-quickstart-aggregator: There are test failures."

Unfortunately, the build failed:

@loicmathieu seems like the latest failure is tailored made for you :)

2020-12-11T05:10:40.5932429Z [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 22.326 s <<< FAILURE! - in org.acme.mongodb.panache.PersonResourceTest
2020-12-11T05:10:40.5934971Z [ERROR] org.acme.mongodb.panache.PersonResourceTest.test  Time elapsed: 1.375 s  <<< FAILURE!
2020-12-11T05:10:40.5936714Z org.opentest4j.AssertionFailedError: 
2020-12-11T05:10:40.5937536Z 
2020-12-11T05:10:40.5938116Z Expecting:
2020-12-11T05:10:40.5938912Z  <"lo茂c">
2020-12-11T05:10:40.5939540Z to be equal to:
2020-12-11T05:10:40.5940281Z  <"LO脧C">
2020-12-11T05:10:40.5940855Z but was not.
2020-12-11T05:10:40.5942336Z    at org.acme.mongodb.panache.PersonResourceTest.test(PersonResourceTest.java:100)

@geoand the assertion si false, this is due to the accessor rewritting PR merged yesterday by @evanchooly, the test assertion should be updated because person.name is rewritten to person.getName() now so the lowercase is done on the name.

I'll send a PR later today to fix this.

Thanks!

The build is still failing:

The build is still failing:

The build is still failing:

The build is still failing:

@evanchooly MongoDB quickstart is still failing because its behaviour in native is not the same as in JVM mode.
In JVM mode, the accessor is used so when you do person.name the getter is used (and there is a lowercase in the getter).
But in native, when you do the same the accessor is not used so person.name return the name in uppercase.

There should be something missing somewhere on the accessor rewritting code.

Didn't @evanchooly just fix a bug related to this in mongodb-panache?

@FroMage not sure, I fixed an issue, but related to the test itself that had a wrong assert. But now the assert works in JVM mode and not in native, meaning the getter is used in JVM mode but not in native

But @evanchooly added a PR recently that enabled getters being called. Isn't that related?

Yes, after this release the test triggers an assertions (because the getter do a lowerCase and the setter an upperCase), this assertions was fixed on JVM mode, but the same assertion that is OK in JVM mode is in failure in native. So the getter appears not to be used in native mode.

That's precisely my point: the fix doesn't appear to work for native, and yet I thought we had tests for this.

I'll take a look today. I don't know why it wouldn't work for naive since it takes the bytecode in the runner jar.

The build is still failing:

The build is still failing:

The build is still failing:

Was this page helpful?
0 / 5 - 0 ratings