<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">
<title>
GitLab
</title>
<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.com/dueno">Daiki Ueno</a>
commented on a
<a href="https://gitlab.com/gnutls/gnutls/-/merge_requests/1337#note_419791566">discussion</a>:
</p>
<div style="">
<p dir="auto">Looks like this is caused by an inherent race condition in the scripts. If I change the concurrency to 1, it doesn't happen.</p>
<p dir="auto">The problem is that, between the timings when a free port is detected and when the port is actually used, other scripts can use the detected port if tests are run in parallel.</p>
<p dir="auto">One idea to solve it is to create a temporary file as a lock, and synchronize the logic. Another idea is to extend gnutls-serv to use ephemeral port something like <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1555554" rel="nofollow noreferrer noopener" target="_blank">NSS bug</a>, though that would require more effort.</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #666;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/-/merge_requests/1337#note_419791566">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/-/sent_notifications/dc4ccb62990717bbc2ece323170c8551/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/-/merge_requests/1337#note_419791566"}}</script>
</p>
</div>
</body>
</html>