Open cescoffier opened 4 years ago
@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:
Quarkus commit: 62c47bb17712f31f90fc8fa834544b6f06ef7adb
Quickstarts commit: 5de86089c12d09c6b059c7e311260bc31309450e
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
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’t work when using Docker to build an image AFAIK. That’s why we don’t 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’t point to the SunEc library as it’s in the Docker image.
It might be fixed with GraalVM 19.3 if everything is statically linked.
FTR the reason is that we can’t point to the SunEc library as it’s 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’s 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:
Quarkus commit: 373ce14d08ce4fa6075b3c6c68d5e49b4cc3936d
Quickstarts commit: 42451e92089316c304f9514d330725a8797e77ac
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
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:
Quarkus commit: fd73233b491e6658bc2501ba8fc3096e8cbf7837
Quickstarts commit: 42451e92089316c304f9514d330725a8797e77ac
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The build is still failing with:
Quarkus commit: fd73233b491e6658bc2501ba8fc3096e8cbf7837
Quickstarts commit: 42451e92089316c304f9514d330725a8797e77ac
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
https://github.com/quarkusio/quarkus-quickstarts/pull/430 is also needed :)
The build is still failing with:
Quarkus commit: fd73233b491e6658bc2501ba8fc3096e8cbf7837
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
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:
Quarkus commit: fd73233b491e6658bc2501ba8fc3096e8cbf7837
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The build is still failing with:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
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:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The build is still failing with:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The build is still failing with:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The build is passing but unfortunately a failure is still reported to this issue
The build is still failing with:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
Going to add a trace in the script to check the passed status.
@geoand can you approve https://github.com/quarkusio/quarkus-quickstarts/pull/432?
Done
I've triggered https://github.com/quarkusio/quarkus-quickstarts/commit/dbefe831e917d7dabf3bcb2b033098ebaf45146a/checks?check_suite_id=409450089 that should display the traces.
Cool, thanks
The build is still failing with:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The build is still failing with:
Quarkus commit: 2532cfb6ce0b03918efe66d3c22240169c158e76
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
@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:
Quarkus commit: d1b5456454370076a8ec32872f5e100f18bda0d0
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
hum... ok, I've cherry-picked the commits.
Are you sure? For example 52a75e0a
is missing from development
The build is still failing with:
Quarkus commit: d1b5456454370076a8ec32872f5e100f18bda0d0
Quickstarts commit: 4985db39034ff05309fc17227daaa8f8fab27e70
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
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:
Quarkus commit: 1a4e95afa61b40a7de4c6ed36edc58f1eb087bca
Quickstarts commit: 3a36b88a860a40bfbae45b2840aff59c5cf11392
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
Unfortunately, the build failed:
Quarkus commit: 1ac29b83dcc2eaa9ba0d61b17350cd4619770d0d
Quickstarts commit: 3a36b88a860a40bfbae45b2840aff59c5cf11392
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
The latest failure should be fixed by https://github.com/quarkusio/quarkus/pull/6681
The build is still failing with:
Quarkus commit: 3398d3663dbd2e88322e5ae488505ec436e9e4a8
Quickstarts commit: 3a36b88a860a40bfbae45b2840aff59c5cf11392
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
Build fixed with:
Quarkus commit: 689b862f3eb947641de0e355071e5a6d92a19c36
Quickstarts commit: 977da1a210701469ef6e714311d6aa7b58efd448
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
Unfortunately, the build failed:
Quarkus commit: 1cbf650267660b597638de0b87ef88ce384b844c
Quickstarts commit: 977da1a210701469ef6e714311d6aa7b58efd448
Link to build: https://github.com/quarkusio/quarkus-quickstarts/actions
This issue reports the current status of the quickstart
development
branch against Quarkusmaster
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.