[tor-bugs] #23758 [Core Tor/Tor]: test config/include_no_permission fails when run as root (was: test config/include_no_permission fails on gitlab.com CI because Docker?)

[Tor Bug Tracker & Wiki]

#23758: test config/include_no_permission fails when run as root
------------------------------+------------------------------------
 Reporter:  catalyst          |          Owner:  catalyst
     Type:  defect            |         Status:  accepted
 Priority:  Medium            |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor      |        Version:
 Severity:  Normal            |     Resolution:
 Keywords:  tor-ci tor-tests  |  Actual Points:
Parent ID:                    |         Points:
 Reviewer:                    |        Sponsor:
------------------------------+------------------------------------
Description changed by catalyst:

Old description:

> I managed to get the gitlab.com CI running using the `.gitlab-ci.yml` on
> master.  (There are other issues with that CI configuration; see #23755
> and #23756.)  It fails with
> {{{
> config/include_no_permission:
>   FAIL src/test/test_config.c:4975:
> assert(config_get_lines_include(torrc_contents, &result, 0,&include_used)
> OP_EQ -1): 0 vs -1
>   [include_no_permission FAILED]
> }}}
>
> As far as I can tell, this can only happen if `opendir()` can succeed on
> a mode `0100` directory.  Maybe this strange thing can happen in the
> Docker environment that runs gitlab.com CI jobs?  I don't know enough
> about Docker to say how plausible that explanation is.

New description:

 I managed to get the gitlab.com CI running using the `.gitlab-ci.yml` on
 master.  (There are other issues with that CI configuration; see #23755
 and #23756.)  It fails with
 {{{
 config/include_no_permission:
   FAIL src/test/test_config.c:4975:
 assert(config_get_lines_include(torrc_contents, &result, 0,&include_used)
 OP_EQ -1): 0 vs -1
   [include_no_permission FAILED]
 }}}

 As far as I can tell, this can only happen if `opendir()` can succeed on a
 mode `0100` directory.  Maybe this strange thing can happen in the Docker
 environment that runs gitlab.com CI jobs?  I don't know enough about
 Docker to say how plausible that explanation is.

 Edit: This seems to be because the gitlab.com CI runs as root.

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23758#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online