[
https://ovirt-jira.atlassian.net/browse/OVIRT-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-2252:
--------------------------------
Description: "One of the tests of the CI mirrors python package is starting
up an HTTP server on a fixed port number.\r\n\r\nThis can cause an issue if the
same test is running in parallel on the same machine. This typically cannot be
an issue on the CI infra because it never runs more then one STDCI thread at a
time on a given slave.\r\n\r\nThis issue does arise specifically on the s390x
slave because there the same slave is used both by the staging and the
production CI systems. In that case the two systems might be trying to run the
same test at the same time, so this can lead to port allocation
exceptions.\r\n\r\n\r\n" (was: One of the tests of the CI mirrors python
package is starting up an HTTP server on a fixed port number.
This can cause an issue if the same test is running in parallel on the same
machine. This typically cannot be an issue on the CI infra because it never
runs more then one STDCI thread at a time on a given slave.
This issue does arise specifically on the s390x slave because there the same
slave is used both by the staging and the production CI systems. In that case
the two systems might be trying to run the same test at the same time, so this
can lead to port allocation exceptions.)
> Rece condition in python tests in jenkins repo on s390x
> -------------------------------------------------------
>
> Key: OVIRT-2252
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2252
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: CI Mirrors
> Reporter: Barak Korren
> Assignee: infra
>
> One of the tests of the CI mirrors python package is starting up an HTTP
> server on a fixed port number.
> This can cause an issue if the same test is running in parallel on the same
> machine. This typically cannot be an issue on the CI infra because it never
> runs more then one STDCI thread at a time on a given slave.
> This issue does arise specifically on the s390x slave because there the same
> slave is used both by the staging and the production CI systems. In that case
> the two systems might be trying to run the same test at the same time, so
> this can lead to port allocation exceptions.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/ZTJAJV3TZ44UBUVEXILFCOWKV7OVU4BQ/
