The test (purposely) failed in the pipeline, but there seemed to be no notification via FMN.
Some analysis work by @pingou suggests that it might be a filter issue. He has set up a new filter, so a retry in a short while should let us know more.
Metadata Update from @dperpeet: - Issue assigned to pingou
I added an empty commit on the f26 branch to trigger the CI pipeline: https://src.fedoraproject.org/rpms/cockpit/commits/f26
Test running at: https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/jenkins/continuous-infra-ci-pipeline-f26/detail/continuous-infra-ci-pipeline-f26/397/pipeline
Let's see how it does notification wise :)
Hm, it looks like the tests passed:
{ "i": 1, "timestamp": 1506503165, "msg_id": "2017-aa56f375-5022-4d19-aaeb-488c04077f7a", "crypto": "x509", "topic": "org.centos.prod.ci.pipeline.integration.complete", "msgJson": "{\"CI_NAME\":\"continuous-infra-ci-pipeline-f26\",\"CI_TYPE\":\"custom\",\"branch\":\"f26\",\"build_id\":\"397\",\"build_url\":\"https://jenkins-continuous-infra.apps.ci.centos.org/job/continuous-infra-ci-pipeline-f26/397/\",\"compose_rev\":\"91cced035cfc5f21cf01ffbb33e984cffe07ae8bfae007549954030e8a37e3fb\",\"message-content\":\"\",\"namespace\":\"rpms\",\"nvr\":\"cockpit-151-2.172.d5fa023.fc26.x86_64\",\"original_spec_nvr\":\"cockpit-151-2.f26\",\"ref\":\"fedora/f26/x86_64/atomic-host\",\"repo\":\"cockpit\",\"rev\":\"d5fa023bbc2106511ddca7ff7274f592931f346c\",\"status\":\"SUCCESS\",\"test_guidance\":\"''\",\"topic\":\"org.centos.prod.ci.pipeline.integration.complete\",\"username\":\"fedora-atomic\"}", "msg": { "CI_TYPE": "custom", "build_id": "397", "original_spec_nvr": "cockpit-151-2.f26", "username": "fedora-atomic", "nvr": "cockpit-151-2.172.d5fa023.fc26.x86_64", "rev": "d5fa023bbc2106511ddca7ff7274f592931f346c", "message-content": "", "build_url": "https://jenkins-continuous-infra.apps.ci.centos.org/job/continuous-infra-ci-pipeline-f26/397/", "namespace": "rpms", "CI_NAME": "continuous-infra-ci-pipeline-f26", "repo": "cockpit", "compose_rev": "91cced035cfc5f21cf01ffbb33e984cffe07ae8bfae007549954030e8a37e3fb", "topic": "org.centos.prod.ci.pipeline.integration.complete", "status": "SUCCESS", "branch": "f26", "test_guidance": "''", "ref": "fedora/f26/x86_64/atomic-host" } } { "i": 1, "timestamp": 1506503170, "msg_id": "2017-63ba5554-0e27-4a2f-b400-58d0f5c17e90", "crypto": "x509", "topic": "org.centos.prod.ci.pipeline.complete", "msgJson": "{\"CI_NAME\":\"continuous-infra-ci-pipeline-f26\",\"CI_TYPE\":\"custom\",\"branch\":\"f26\",\"build_id\":\"397\",\"build_url\":\"https://jenkins-continuous-infra.apps.ci.centos.org/job/continuous-infra-ci-pipeline-f26/397/\",\"compose_rev\":\"91cced035cfc5f21cf01ffbb33e984cffe07ae8bfae007549954030e8a37e3fb\",\"message-content\":\"\",\"namespace\":\"rpms\",\"nvr\":\"cockpit-151-2.172.d5fa023.fc26.x86_64\",\"original_spec_nvr\":\"cockpit-151-2.f26\",\"ref\":\"fedora/f26/x86_64/atomic-host\",\"repo\":\"cockpit\",\"rev\":\"d5fa023bbc2106511ddca7ff7274f592931f346c\",\"status\":\"SUCCESS\",\"test_guidance\":\"''\",\"topic\":\"org.centos.prod.ci.pipeline.complete\",\"username\":\"fedora-atomic\"}", "msg": { "CI_TYPE": "custom", "build_id": "397", "original_spec_nvr": "cockpit-151-2.f26", "username": "fedora-atomic", "nvr": "cockpit-151-2.172.d5fa023.fc26.x86_64", "rev": "d5fa023bbc2106511ddca7ff7274f592931f346c", "message-content": "", "build_url": "https://jenkins-continuous-infra.apps.ci.centos.org/job/continuous-infra-ci-pipeline-f26/397/", "namespace": "rpms", "CI_NAME": "continuous-infra-ci-pipeline-f26", "repo": "cockpit", "compose_rev": "91cced035cfc5f21cf01ffbb33e984cffe07ae8bfae007549954030e8a37e3fb", "topic": "org.centos.prod.ci.pipeline.complete", "status": "SUCCESS", "branch": "f26", "test_guidance": "''", "ref": "fedora/f26/x86_64/atomic-host" } }
While this doesn't explain the underlying issue (of missing notifications), I'd like to point out that the commit 2563d0 that added the broken test, failed the CI pipeline due to an error in the pipeline itself not due to its tests.
I believe this error was caused by a short outage we had on the infrastructure at that time (we had to reboot the box as something had got messed up)
Closing.
If appears again - let's deal with it in the issues in fedora-ci/general project
Metadata Update from @bookwar: - Issue close_status updated to: Insufficient Data - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.