On Thu, Jan 18, 2018 at 10:37 PM, Jeff King <peff@xxxxxxxx> wrote: > On Thu, Jan 18, 2018 at 10:00:14PM +0700, Duy Nguyen wrote: > >> The test suite was run as root, no wonder why my removing write access >> has no effect. I got the test to pass with this, but then it fails >> with >> >> Can't write .prove (Permission denied) at /usr/share/perl/5.22/App/Prove.pm line 542. >> >> Some more chown'ing or chmod'ing is required.... This is the fallout of running the tests as root in the past. With your patch 'prove' is run as a non-root user, but the prove state is loaded from Travis CI's cache, where it has been written as root the last time around, so now we don't have permissions to (over)write it. I have patches in the works to address this as well. >> Subject: [PATCH] ci: don't accidentally run the test suite as root >> >> This script assigns and adds a user named "ci" in a subshell so the >> outer CI_USER is not affected. For some reason, CI_USER is actually >> empty on Travis linux32 builds. This makes the following "su" useless >> and the test suite is run as root. > > Are we sure this was the problem on Travis, and it wasn't just an issue > with how I reproduced via docker? Yes, we are. Gábor
