(original) (raw)

I wouldn't expect it to be the case in a CI environment but I believe a umask can be overridden if the filesystem is mounted and configured with acls set? (oh, hah, Ivan just said the same thing)

-gps

On Sat, Mar 30, 2019 at 9:05 AM Steve Dower <steve.dower@python.org> wrote:

On 29Mar.2019 1944, Steve Dower wrote:
\> On 29Mar.2019 1939, Cameron Simpson wrote:
\>> Can you get a branch into your pipeline? Then you could just hack the
\>> tarfile test with something quick and dirty like:
\>>
\>> pid = os.getpid()
\>> system("strace -p %d 2>/path/to/strace.out &" % pid)
\>> time.sleep(2) # get strace heaps of time to start
\>>
\>> just before the tarfile open. A ghastly hack but it would get you
\>> debugging info. You could even decide to remove the strace.out file if
\>> the umask issue doesn't show, if it is erratic (can't see why it would
\>> be though).
\>
\> Perfect, I'll give this a go. Thanks!

I set up a PR to collect this trace and the results are at:
https://github.com/python/cpython/pull/12625

However, I suspect it's a non-result:

umask(022) = 022
open("/home/vsts/work/1/s/build/test\_python\_5154/@test\_5154\_tmp-tardir/tmp.tar",
O\_WRONLY|O\_CREAT|O\_TRUNC|O\_CLOEXEC, 0666) = 3
write(3, "BZh91AY&SYY{\\270\\344\\0\\0\\24P\\0\\300\\0\\4\\0\\0\\10
\\0000\\314\\5)\\246"..., 46) = 46
close(3) = 0
stat("/home/vsts/work/1/s/build/test\_python\_5154/@test\_5154\_tmp-tardir/tmp.tar",
{st\_mode=S\_IFREG|0666, st\_size=46, ...}) = 0

Happy to take more suggestions if anyone has them.

Thanks,
Steve
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/greg%40krypto.org