When attempting to emerge python-3.12.9 with USE="pgo" I'm getting a sandbox violation: * ----------------------- SANDBOX ACCESS VIOLATION SUMMARY ----------------------- * LOG FILE: "/var/tmp/portage/dev-lang/python-3.12.9/temp/sandbox.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: open_wr S: deny P: /var/lib/libuuid/clock.txt A: /var/lib/libuuid/clock.txt R: /var/lib/libuuid/clock.txt C: /var/tmp/portage/dev-lang/python-3.12.9/work/Python-3.12.9/python -u -m test.libregrtest.worker {"tests": ["test_uuid"], "fail_fast": false, "fail_env_changed": false, "match_tests": [], "match_tests_dict": null, "rerun": false, "forever": false, "pgo": true, "pgo_extended": true, "output_on_failure": false, "timeout": 1200.0, "verbose": 0, "quiet": false, "hunt_refleak": null, "test_dir": null, "use_junit": false, "memory_limit": null, "gc_threshold": null, "use_resources": [], "python_cmd": null, "randomize": false, "random_seed": 158337264, "json_file": {"file": 8, "file_type": "UNIX_FD"}, "__runtests__": true} * -------------------------------------------------------------------------------- The relevant build.log snippet: 0:07:48 load avg: 4.09 [404/442] test_urlparse passed 0:07:48 load avg: 4.09 [405/442] test_unittest passed 0:07:49 load avg: 4.09 [406/442] test_utf8source passed 0:07:50 load avg: 4.08 [407/442] test_uu passed * ACCESS DENIED: open_wr: /var/lib/libuuid/clock.txt 0:07:51 load avg: 4.08 [408/442] test_uuid passed 0:07:51 load avg: 4.08 [409/442] test_utf8_mode passed 0:07:52 load avg: 4.08 [410/442] test_userstring passed 0:07:55 load avg: 3.91 [411/442] test_venv passed 0:07:57 load avg: 3.91 [412/442] test_wait3 passed This is most likely due to a new/updated test in the default test suite, which are executed during the build in order to generate the PGO feedback. Reproducible: Always Steps to Reproduce: 1. Enable "pgo" USE flag for dev-lang/python 2. Emerge python-3.12.9 Actual Results: Emerge fails due to sandbox violation Expected Results: Emerge succeeds
test_uuid, even. The full build.log and emerge --info is missing. Do you have sys-apps/util-linux[uuidd]?
Created attachment 924217 [details] emerge --info
Created attachment 924219 [details] build.log
(In reply to Sam James from comment #1) > test_uuid, even. The full build.log and emerge --info is missing. Missing logs attached. > Do you have sys-apps/util-linux[uuidd]? Yes, correct.
I don't think it makes sense to work around this in the Python ebuild. We could add a sandbox config in util-linux, or WONTFIX and leave this to the user to resolve.
Created attachment 924253 [details, diff] util-linux-uuidd-sandbox.patch This patch allows me to build python correctly.
