third_party
/
virglrenderer
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2633 Commits
1 Branch
0 Tags
6.6 MiB
Tag: Branch: Tree: c8b112f5f5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c8b112f5f5'
${ noResults }
virglrenderer/.gitlab-ci/expectations/virt/deqp-virgl-gl.toml

58 lines
1.7 KiB
Raw Normal View History Unescape

ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
[[deqp]]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
deqp = "/install/crosvm-runner.sh"
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
caselists = ["/deqp/mustpass/gles2-master.txt"]
deqp_args = [
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
"/deqp/modules/gles2/deqp-gles2",
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
"--deqp-surface-width=256",
"--deqp-surface-height=256",
"--deqp-surface-type=pbuffer",
"--deqp-gl-config-name=rgba8888d24s8ms0",
"--deqp-visibility=hidden"
]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
timeout = 360.0 # Starting 8 Crosvm instances simultaneously can take some time
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
version_check = "GL ES 3.2.*git"
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
renderer_check = "virgl.*llvmpipe"
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
[[deqp]]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
deqp = "/install/crosvm-runner.sh"
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
caselists = ["/deqp/mustpass/gles3-master.txt"]
deqp_args = [
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
"/deqp/modules/gles3/deqp-gles3",
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
"--deqp-surface-width=256",
"--deqp-surface-height=256",
"--deqp-surface-type=pbuffer",
"--deqp-gl-config-name=rgba8888d24s8ms0",
"--deqp-visibility=hidden"
]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
timeout = 360.0 # Starting 8 Crosvm instances simultaneously can take some time
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
[[deqp]]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
deqp = "/install/crosvm-runner.sh"
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
caselists = ["/deqp/mustpass/gles31-master.txt"]
deqp_args = [
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
"/deqp/modules/gles31/deqp-gles31",
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
"--deqp-surface-width=256",
"--deqp-surface-height=256",
"--deqp-surface-type=pbuffer",
"--deqp-gl-config-name=rgba8888d24s8ms0",
"--deqp-visibility=hidden"
]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
timeout = 360.0 # Starting 8 Crosvm instances simultaneously can take some time
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
[[deqp]]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
deqp = "/install/crosvm-runner.sh"
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
caselists = [
"/deqp/mustpass/gl30-master.txt",
"/deqp/mustpass/gl31-master.txt",
"/deqp/mustpass/gl32-master.txt",
]
deqp_args = [
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
"/deqp/external/openglcts/modules/glcts",
ci: Rework CI setup based on Mesa CI infrastructure Add initial support for reusing the Mesa CI infrastructure. Note this doesn't conflict with the old CI since it doesn't share the 'ci/' folder, but instead uses '.gitlab-ci/', which makes the new setup consistent with Mesa CI. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Tomeu Vizoso <tomeu.vizoso@collabora.com> Reviewed-by: Rohan Garg <rohan.garg@intel.com>
3 years ago
"--deqp-surface-width=256",
"--deqp-surface-height=256",
"--deqp-surface-type=pbuffer",
"--deqp-gl-config-name=rgba8888d24s8ms0",
"--deqp-visibility=hidden"
]
ci: Optimize virtio-gpu jobs execution Since crosvm is not able to properly handle parallel tests due to a concurrency bottleneck, it's necessary to ensuring scaling at the host system level by increasing the number of active crosvm instances. For dEQP testing this can be easily accomplished by using the Deqp Suite support in deqp-runner and adding the crosvm wrapper script in the related '*.toml' files. For piglit this is currently not supported in piglit-runner, but something similar could be added later. For the moment we use an increased number of parallel jobs to speed-up the execution. Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> Reviewed-by: Guilherme Gallo <guilherme.gallo@collabora.com> Acked-by: Daniel Stone <daniels@collabora.com>
3 years ago
timeout = 360.0 # Starting 8 Crosvm instances simultaneously can take some time