Community
Participate
Working Groups
Its a mystery as to why, but the the main build directories under "drops4" and "drops" are not being created with right permissions. under "drops4" they are missing the group w, under drops, they are missing that, plus the groups GUID bit. "updates" (for eclipse 4I builds) seem right: drwxrwsr-x+ 5 e4Build eclipse.platform.releng 4K 2012-05-13 15:22 I20120513-1300/ I'm going to add umask 0002 to "masterBuild" just to make sure it is what we think it is (that should be the default, but, just to make sure).
Well, still a mystery as to why, but explicitly setting umask seems to have fixed this (judging from 7 PM build that just stated: drwxrwsr-x+ 2 e4Build eclipse.platform.releng 4096 2012-05-13 19:02 I20120513-1900 Even though build as a whole was canceled, I'm fairly sure this was the reason for the fix, since, the the script I put in in 'masterBuild' prints out this: umask explicitly set to 0002, old value was 0022 Which is odd, since just logging in to e4Build has the value set to 0002. Ah, I guess "from a cron job" does have a different environment (e.g. no path, no bashrc ran) so ... guess "the system" has a default of 022, even though a "user default" is 002. But ... this doesn't really explain why it's correct in some places and wrong it others ... but ... setting the umask is obviously required, so will count this bug as fixed, and open others if other things are also wrong. For the reference, the script I added was: oldumask=`umask` umask 0002 echo "umask explicitly set to 0002, old value was $oldumask"
While I'd not call this the "cause" (obviously many interactions) this might be part of the complication of bug 378708.
