P. S. And if after the build I just manually run /opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests/VidaliaTestSuite – Vidalia client starts, all tests pass, no errors:
. . . 250 OK QDEBUG : TorrcTestSuite::testRunningTor() torcontrol: Control Command: GETCONF UseMicrodescriptors QDEBUG : TorrcTestSuite::testRunningTor() torcontrol: Control Reply: 250 UseMicrodescriptors=auto QDEBUG : TorrcTestSuite::testRunningTor() torcontrol: Control Command: GETCONF FetchUselessDescriptors QDEBUG : TorrcTestSuite::testRunningTor() torcontrol: Control Reply: 250 FetchUselessDescriptors=0 QDEBUG : TorrcTestSuite::testRunningTor() torcontrol: Control Command: GETCONF UseMicrodescriptors QSYSTEM: TorrcTestSuite::testRunningTor() Maximum amount of warnings exceeded. Use -maxwarnings to override. PASS : TorrcTestSuite::testRunningTor() PASS : TorrcTestSuite::cleanupTestCase() Totals: 6 passed, 0 failed, 0 skipped, 0 blacklisted, 12273ms ********* Finished testing of TorrcTestSuite ********* On Sun, Feb 25, 2024 at 12:06 AM Sergey Fedorov <vital....@gmail.com> wrote: > Thank you. > > This branch adds a version with Qt5 for aarch64 and tests support: > https://github.com/barracuda156/macports-ports/tree/vidalia > > If running via sudo port test, I get this: > > ---> Testing Vidalia > > Executing: cd > "/opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests" > && ./VidaliaTestSuite > > ********* Start testing of TorrcTestSuite ********* > > Config: Using QtTest library 5.15.12, Qt 5.15.12 (arm64-little_endian-lp64 > shared (dynamic) release build; by Clang 15.0.0 (clang-1500.1.0.2.5) > (Apple)), osx 14.3 > > PASS : TorrcTestSuite::initTestCase() > > PASS : TorrcTestSuite::testTorrcLine() > > PASS : TorrcTestSuite::testTorrcParser() > > PASS : TorrcTestSuite::testTorrc() > > QWARN : TorrcTestSuite::testRunningTor() libpng warning: iCCP: known > incorrect sRGB profile > > sh: line 1: 72551 Trace/BPT trap: 5 ./VidaliaTestSuite > > Command failed: cd > "/opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests" > && ./VidaliaTestSuite > > Exit code: 133 > > Error: Failed to test Vidalia: command execution failed > > On Sat, Feb 24, 2024 at 11:56 PM Ken Cunningham < > ken.cunningham.web...@gmail.com> wrote: > >> Oh, OK…. That’s different then, for sure. >> >> Let me see if I get the same result. >> >> K >> >> On Feb 24, 2024, at 08:32, Sergey Fedorov <vital....@gmail.com> wrote: >> >> >> Ken, you are right about 10.6-ppc, of course, but in this particular case >> I am having an issue with Sonoma. >> Specifically, I cannot get Vidalia tests run with *sudo port test*. At >> the same time, they run fine if I launch the test binary manually without >> sudo. >> >> What fails: >> 1. sudo port test vidalia >> 2. sudo >> /opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests/VidaliaTestSuite >> 3. sudo -u macports >> /opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests/VidaliaTestSuite >> >> What works fine: >> 1. >> /opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests/VidaliaTestSuite >> 2. sudo -u svacchanda >> /opt/local/var/macports/build/_opt_svacchanda_SonomaPorts_security_Vidalia/Vidalia/work/vidalia-8240540188062a168a66b25ca61b852cc89140ad/src/tests/VidaliaTestSuite >> (that is, from a current non-root user). >> >> (Portfile in the master has no support for tests, as of now, so running >> it gonna fail anyway.) >> >> On Sat, Feb 24, 2024 at 11:24 PM Ken Cunningham < >> ken.cunningham.web...@gmail.com> wrote: >> >>> Some of your macports installations are installed as the root user, >>> instead of the macports user. >>> >>> This happened because there is no installer for 10.6-ppc to >>> automatically create the macports user. You have an open ticket about this >>> too, where I pointed to the commands to be run to generate the macports >>> user. >>> >>> Sooner or later you will probably have to fix this. >> >>
