-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] Add test capture #163
Conversation
There are lots of things missing due to how azure works, here is what it should look like probably: pr:
branches:
include:
- "*"
- job: sca_capture
displayName: "Capture SCA traces"
timeoutInMinutes: 30
dependsOn: checkout
pool: FPGA SCA
steps:
- checkout: self
- bash: |
python3 -m pip install --user -r python-requirements.txt
displayName: "Install python dependencies"
- bash: |
apt install ... # if any
displayName: "Install system dependencies"
- bash: |
pushd ci
./ci_capture_aes_fvsr.sh
popd
displayName: "Capture traces"
# here migth want to add more steps to publish the traces, e.g.
- publish: path/to/file
artifact: traces
displayName: "Upload traces" |
also it might need to setup git-lfs if you use it for the tests |
Based on the getting-started guide, I think this should be |
2bb4cf0
to
74578c6
Compare
1fb06df
to
5ad326d
Compare
Is the directory definitely called |
cdc4f85
to
865e28f
Compare
This commit adds the first FPGA test to the CI. The test captures and publishes 1000 traces using aes-fvsr-key-batch command.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for iterating on this with us @vrozic. Artifacts are available in the Azure interface for each job, e.g. this run as a link in the logs:
which links to this artifact. Not the easiest to discover, I know. |
Test PR adds the first FPGA test to the CI.
The test runs
aes-fvsr-key-batch
command, collects 1000 measurements on CW310 and publishes the collected traces.