qemu-devel
[
Top
][
All Lists
]
Advanced
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
When create a new qemu fork, can not run pipeline, what I need to do?
From
:
Yonggang Luo
Subject
:
When create a new qemu fork, can not run pipeline, what I need to do?
Date
:
Wed, 27 Jul 2022 19:20:51 +0800
···
Pipeline cannot be run.
No stages / jobs for this pipeline.
The form contains the following warning:
121 warnings found: showing first 25
jobs:amd64-centos8-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:amd64-fedora-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:amd64-debian10-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:alpha-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:amd64-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:amd64-debian-user-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:arm64-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:armel-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:armhf-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:hexagon-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:hppa-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:m68k-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:mips64-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:mips64el-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:mips-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:mipsel-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:powerpc-test-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:ppc64el-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:riscv64-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:riscv64-debian-test-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:s390x-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:sh4-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:sparc64-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:tricore-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
jobs:xtensa-debian-cross-container may allow multiple pipelines to run for a single action due to `rules:when` clause with no `workflow:rules` - read more:
https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings
Run for branch name or tag
master
Variables
Specify variable values to be used in this run. The values specified in CI/CD settings will be used by default.
Run pipelineCancel
···
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
reply via email to
[Prev in Thread]
Current Thread
[
Next in Thread
]
When create a new qemu fork, can not run pipeline, what I need to do?
,
Yonggang Luo
<=
Re: When create a new qemu fork, can not run pipeline, what I need to do?
,
Philippe Mathieu-Daudé
,
2022/07/27
Re: When create a new qemu fork, can not run pipeline, what I need to do?
,
Daniel P . Berrangé
,
2022/07/28
Re: When create a new qemu fork, can not run pipeline, what I need to do?
,
Yonggang Luo
,
2022/07/28
Re: When create a new qemu fork, can not run pipeline, what I need to do?
,
Philippe Mathieu-Daudé
,
2022/07/28
Prev by Date:
Re: updates for designware pci-host
Next by Date:
Re: [PATCH 0/5] Enable unix socket support on Windows
Previous by thread:
virtio: why no full reset on virtio_set_status 0 ?
Next by thread:
Re: When create a new qemu fork, can not run pipeline, what I need to do?
Index(es):
Date
Thread