bneradt commented on issue #8799:
URL: https://github.com/apache/trafficserver/issues/8799#issuecomment-1130267748
> I believe this was due to an environmental issue. My local dev environment
had symlinks pointing to the Linux binaries, not MacOS, and that seems to have
been the culprit. When the symlinks point to the binaries in the `mac-os`
directory, AuTest runs as expected.
Cool. Thank you for the follow up @randall and @elsloo.
Just to follow up with my own experiments: I now have an M1 Mac for work.
(Thanks, in large part, to this ticket. :tada:.) I was able to build
proxy-verifier locally without any modification to the source code or
Sconstruct lines.
Also, using the verifier-server and verifier-client binaries, obtained from
bintray automatically via the autest.sh script, autest is able to use those
verifier binaries (i.e., not the locally built binaries referenced previously):
```
$ uname -m
arm64
$ ./autest.sh --sandbox /tmp/sb --clean=none --ats-bin
~/project_not_synced/build/ts_os/bin/ -f dns_down_nameserver
Python 3.6 or newer detected!
python3-dev/devel detected!
pipenv detected!
Using the pre-existing virtual environment.
Environment config finished. Running AuTest...
Running Test dns_down_nameserver:........ Passed
Generating Report: --------------
Total of 1 test
Unknown: 0
Exception: 0
Failed: 0
Warning: 0
Skipped: 0
Passed: 1
```
Closing the ticket because it looks like we're all in good shape here. Thank
you @elsloo for recording your observations here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
