Hi, Any updates on this ?
Tnx, Tuc On Tue, Apr 9, 2024 at 6:24 PM Scott Ellentuch <tuct...@gmail.com> wrote: > Hi, > > Yes, as ec2-user running the make and then make test ends up failing. > There are no issues with the port as a previous tcpdump has shown, it > transfers data back and forth. It gets through some of the tests and then > it sends a RST. Amazon only goes as far as spamassassin-3.4.3 in Amazon > Linux 2 and they removed it in Amazon Linux 2023. > > Test Summary Report > ------------------- > t/spamd_client.t (Wstat: 26624 Tests: 4 Failed: 0) > Non-zero exit status: 104 > Parse errors: Bad plan. You planned 52 tests but ran 4. > Files=217, Tests=3765, 940 wallclock secs ( 1.24 usr 0.22 sys + 280.71 > cusr 26.08 csys = 308.25 CPU) > Result: FAIL > Failed 1/217 test programs. 0/3765 subtests failed. > make: *** [test_dynamic] Error 255 > > Tuc > > > > On Tue, Apr 9, 2024 at 4:03 PM Sidney Markowitz <sid...@sidney.com> wrote: > >> Scott Ellentuch wrote on 10/04/24 5:15 am: >> > Apologies, but I don't understand. >> > >> > I am running "make test" as the AWS user "ec2-user" when getting these >> > errors. Are you saying that its an acceptable error right now, and I >> can >> > just do the "sudo make install"? >> > >> >> If you ran "make test" as user "ec2-user", not "sudo make test" then I >> misread this thread and looked at the wrong thing. The bug I found is an >> unexpected problem when running the test as root even when home >> directory permissions are relaxed. >> >> Unless what happened was that you ran "sudo make test" and then tried >> "make test" without deleting the files in the t/log directory that were >> created owned by root by the "sudo make test", which would then cause >> failures in the "make test". >> >> To be clear: On a clean system that has everything needed by >> SpamAssassin installed, running as user "ec2-user", you should be able >> to run >> >> perl Makefile.PL < /dev/null >> make >> make test >> >> see no errors in the tests, and then run >> >> sudo make install >> >> If you are getting errors in spamd tests when running make test as >> ec2-user then that might be indicating that something about the >> configuration on aws regarding the network and access to ports is >> getting in the way. >> >> I don't know if there are any gotchas like that about setting up on aws, >> but if there are, there are probably people on this mailing list who are >> more familiar with any complexities in making a virtual machine on aws >> properly configured to run SpamAssassin. >> >>
