Native client concourse pipeline is failing
Hi everyone, I am trying to run the CI for geode-native, but I am observing some issues: * https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-rhel-7-debug/builds/307 * https://concourse.apachegeode-ci.info/teams/main/pipelines/geode-native-develop-pr/jobs/build-rhel-7-debug/builds/308 The error seems to be: Put "/volumes/8f996ea5-e894-4f0d-40ba-b61fbe0e2b7e/stream-out?path=.": context canceled And as my little experience goes with this, I'd say this seems to be related to the concourse system itself. Is there anyone that can look at it? Thanks, Mario!
Re: Concourse pipeline for geode-native RHEL-8 build failing
Hi again, After further looking into the issue, I've seen that since execution #218 a new image to build in RHEL-8 is used. Its timestamp is: 2021-05-12T13:07:24.644-07:00 However, the error appears at build #233 with execution timestamp 2021-05-21T20:57:04Z related to PR #805 (not yet merged). Its parent commit is 36c84e2ce8b9f72b5c520e233bd991f1ac8d8894<https://github.com/apache/geode-native/commit/36c84e2ce8b9f72b5c520e233bd991f1ac8d8894> Commit 36c84e2ce8b9f72b5c520e233bd991f1ac8d8894<https://github.com/apache/geode-native/commit/36c84e2ce8b9f72b5c520e233bd991f1ac8d8894> is related to PR #802, which was merged 2021-05-06T17:34:42Z. Consequently: * The error doesn't seem to be related to an image change, since the last image change was between builds #217 and #218 and the error did not appear until #233 * The error is not related to a commit being merged, since the parent commit (36c84e2ce8b9f72b5c520e233bd991f1ac8d8894<https://github.com/apache/geode-native/commit/36c84e2ce8b9f72b5c520e233bd991f1ac8d8894>) for the first failing execution was merged since a while ago: 2021-05-06T17:34:42Z So, TBH, I can't say what can't be happening there. Would it be possible to share the Gcloud RHEL-8 image so I can make some additional tests? Or maybe is there someone with access to the Gcloud project that can further look into this problem. There are 8 PR's blocked due to this issue, so any help would be welcomed. Thanks! Mario. From: Mario Salazar de Torres Sent: Monday, May 31, 2021 1:39 PM To: dev@geode.apache.org Subject: Concourse pipeline for geode-native RHEL-8 build failing Hi, I've seen that all RHEL 8 geode-native build jobs are failing since the last week. The kind of error reported is: Inconsistency detected by ld.so: dl-call-libc-early-init.c: 37: _dl_call_libc_early_init: Assertion `sym != NULL' failed! An example of such issue is: https://concourse.apachegeode-ci.info/builds/43747#L60706bff:4934 I've generated the gcloud image for RHEL-8 using packer, and executed several failing commits, but compilation was always successful. So, I was wondering if you have recently re-generated the RHEL8 gcloud image lately? I mention it because as I've read this kind of issue might be caused by glibc being corrupted. Thanks! Mario
Concourse pipeline for geode-native RHEL-8 build failing
Hi, I've seen that all RHEL 8 geode-native build jobs are failing since the last week. The kind of error reported is: Inconsistency detected by ld.so: dl-call-libc-early-init.c: 37: _dl_call_libc_early_init: Assertion `sym != NULL' failed! An example of such issue is: https://concourse.apachegeode-ci.info/builds/43747#L60706bff:4934 I've generated the gcloud image for RHEL-8 using packer, and executed several failing commits, but compilation was always successful. So, I was wondering if you have recently re-generated the RHEL8 gcloud image lately? I mention it because as I've read this kind of issue might be caused by glibc being corrupted. Thanks! Mario
Re: [Suspected Spam] Access to Geode concourse pipeline
Hi Sara. This got thrown into my junk list (thanks, Outlook). I’ll get on this. From: Sarah Abbey Date: Wednesday, September 30, 2020 at 9:07 AM To: dev@geode.apache.org Subject: [Suspected Spam] Access to Geode concourse pipeline Hello! I would like to request access to the Geode concourse pipeline<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fdata=02%7C01%7Crhoughton%40vmware.com%7C8675d716a76b46e1726408d8655ac2db%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637370788208211407sdata=5oEjEdICsy%2Bb4OxhaQs8XoWlFSUUYxwIa4gEEF%2FCuf4%3Dreserved=0>. Thank you, Sarah
Access to Geode concourse pipeline
Hello! I would like to request access to the Geode concourse pipeline<https://concourse.apachegeode-ci.info/>. Thank you, Sarah
Re: Concourse pipeline
Mail should be sent out only on failures, so I would hope they'd be less frequent than Travis. I think Travis also processes PRs which contributes to the noise. -S. On Fri, Dec 1, 2017 at 4:26 PM, Greg Chase <g...@gregchase.com> wrote: > I wonder - do we want a separate email alias for these messages if they are > going to be even more frequent than Travis? > > On Fri, Dec 1, 2017 at 3:24 PM, Sean Goller <sgol...@pivotal.io> wrote: > > > Hi everyone, > > If you haven't already heard, we have a new concourse pipeline > > infrastructure up and running at https://concourse.apachegeode-ci.info/ > . > > When these jobs fail, email will be sent to the dev list, so be aware! :) > > > > -Sean. > > >
Re: Concourse pipeline
I wonder - do we want a separate email alias for these messages if they are going to be even more frequent than Travis? On Fri, Dec 1, 2017 at 3:24 PM, Sean Goller <sgol...@pivotal.io> wrote: > Hi everyone, > If you haven't already heard, we have a new concourse pipeline > infrastructure up and running at https://concourse.apachegeode-ci.info/ . > When these jobs fail, email will be sent to the dev list, so be aware! :) > > -Sean. >
Concourse pipeline
Hi everyone, If you haven't already heard, we have a new concourse pipeline infrastructure up and running at https://concourse.apachegeode-ci.info/ . When these jobs fail, email will be sent to the dev list, so be aware! :) -Sean.
