-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
intltool race condition during parallel builds (sometimes) #211
Comments
J100 is a LOT of jobs at once. How many cores do you have? I've had no trouble with just "make -j" which gives unrestricted jobs with mate-utils, but an attempt on my same system (AMD Bulldozer 1st gen "8 core") to build kdenlive or GTK will fail unless the number of jobs is restricted, generally I use 8 for that, one per supported thread. |
Hi,
On Saturday, 12 January 2019, lukefromdc wrote:
J100 is a LOT of jobs at once. How many cores do you have? I've had no trouble with just "make -j" which gives unrestricted jobs with mate-utils, but an attempt on my same system (AMD Bulldozer 1st gen "8 core") to build kdenlive or GTK will fail unless the number of jobs is restricted, generally I use 8 for that, one per supported thread.
The -J100 is for stress testing parallel builds and intact internal build orders. Of course, you wouldn't do that on production build servers.
However, on the diverse Debian build archs, we see those failures here and there.
Mike
--
Sent from my Sailfish device
|
It's still an issue, see https://bugs.debian.org/919058 |
It doesn't have to use multicore. Going to the |
I just noticed that someone else is having problems with nondeterministic exceptions in itstool: |
If we don't use that anymore, we should close this as it should never be seen again |
I just got this (or something similar) on a new faster system (ryzen): parallel build with gettext enabled failed, but restarting the build finished it. Got this error:
Reopening but not sure if this is the same as #210 or this issue. Close it again if it is an instance of the former |
@lukefromdc |
Any way i filed out an report. |
I guess this can be closed again then, since that is a different issue? |
Expected behaviour
Builds always succeed on any supported architecture.
Actual behaviour
Builds sometimes fail, obviously a race condition.
See https://buildd.debian.org/status/package.php?p=mate-utils (the build sucesses might change with my next upload, which I will do once I have a fix for this issue).
Steps to reproduce the behaviour
Building the Debian package from Debian unstable on a Debian unstable system.
MATE general version
1.20
Package version
1.20.2
Linux Distribution
Debian testing/unstable
Some feedback from Jeremy Bicha (Debian GNOME Team and Ubuntu Developer):
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: