Bug #515

avatar

Parallel build tends to fail and cause sharing violation

Added by Pacho Ramos 5191 days ago. Updated 4780 days ago.

Status:Closed Start:10/05/2010
Priority:Normal Due date:
Assigned to:avatarMirco Bauer % Done:

100%
Category:Other
Target version:0.8.9
Complexity:

Medium

 Found in Version:
Votes: 0

Description

When trying to bump to 0.8 smuxi ebuild (for Gentoo users), I noticed build failed from time to time when toggling "debug" configure option but, later, I saw that the problem didn't occur when forcing its compilation disabling parallel build.

The error I was seeing is the following:

: error CS0016: Could not write to file `/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/obj/Debug/Twitterizer2.dll', cause: Sharing violation on
path /var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/obj/Debug/Twitterizer2.dll
Task "Csc" execution -- FAILED
Done building target "CoreCompile" in project "/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib/Twitterizer/Twitterizer2/Twitterizer2.csproj".--
FAILED

Target _GetCompileOutputsForClean:
Target _RecordCleanFile:

Done building project "/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib/Twitterizer/Twitterizer2/Twitterizer2.csproj".-- FAILED

Build FAILED.
Errors:

/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib/Twitterizer/Twitterizer2/Twitterizer2.csproj (default targets) ->
/usr/lib64/mono/3.5/Microsoft.CSharp.targets (CoreCompile target) ->

: error CS0016: Could not write to file `/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/obj/Debug/Twitterizer2.dll', cause: Sharing violation on path /var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/obj/Debug/Twitterizer2.dll
0 Warning(s)

1 Error(s)

Time Elapsed 00:00:05.4733280
make2: *** [../bin/debug/Twitterizer2.dll] Error 1
make2: *** Waiting for unfinished jobs....

Target GetCopyToOutputDirectoryItems:

        Project "/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib/Newtonsoft.Json/Src/Newtonsoft.Json/Newtonsoft.Json.csproj" (GetCopyToOutputDirectoryItems target(s)):
Done building project "/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib/Newtonsoft.Json/Src/Newtonsoft.Json/Newtonsoft.Json.csproj".
Target DeployOutputFiles:

        Copying file from '/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/obj/Debug/Twitterizer2.dll.mdb' to '/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/Twitterizer2.dll.mdb'

        Copying file from '/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/obj/Debug/Twitterizer2.dll' to '/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/bin/debug/Twitterizer2.dll'
Target _GetCompileOutputsForClean:
Target _RecordCleanFile:

Done building project "/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib/Twitterizer/Twitterizer2/Twitterizer2.csproj".

Build succeeded.
0 Warning(s)
0 Error(s)

Time Elapsed 00:00:05.6182230
make2: Leaving directory `/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib'
make1: *** [all-recursive] Error 1
make1: Leaving directory `/var/tmp/portage/net-irc/smuxi-0.8/work/smuxi-0.8/lib'
make: *** [all-recursive] Error 1

Attached is full build.log

build.log - build.log (139 KB) Pacho Ramos, 10/05/2010 08:25 PM

Related issues

duplicates Smuxi - Bug #492 smuxi-0.8 fails to build with --enable-debug is no smuxi is already installed in system Closed 09/13/2010

Associated revisions

Revision 12cedb7290f6b6fe2765432c0b5bf73c25a94922
Added by Mirco Bauer 4780 days ago

Forcely disable parallel builds (closes: #515)

History

Updated by Mirco Bauer 5191 days ago

avatar
  • Category changed from Common to Other
  • Target version changed from 0.8 to 0.8.9
Is it acceptable for you if I override make's setting to suppress -j > 0? The build will then no longer fail but will also not take advantage of parallel builds. As Smuxi builds in less than 30 seconds using -j1 I don't think it's worth it to add support for parallel builds:
make[1]: Leaving directory `/home/meebey/data/projects/c-sharp/smuxi/git'
real    0m18.039s
user    0m17.053s
sys    0m1.212s

Updated by Mirco Bauer 5191 days ago

avatar

Thank you very much for finding out what the cause of #492 is, I wasn't able to reproduce it. (as I am not using make -j > 0).

Updated by Pacho Ramos 5191 days ago

avatar

From my point of view, if it's too hard to fix, would be better to force "-j1" but, of course, would be better to try to solve it since probably people owning machines with multiple cores would get it built much faster :-)

Updated by Mirco Bauer 4780 days ago

avatar
  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF