Open kiniry opened 4 years ago
Acknowledged. Since we don't have the deployment
option implemented yet, all we have is smoke testing. The unix ones are almost done, but FreeRTOS is a bit behind. I will update this ticket with how to
for running those tests as soon as they're merged to develop
(Which means they pass our reviews).
I suspect already well in hand, but just a note that smoke tests on FreeBSD will need to be compiled with LLVM and LLD (https://github.com/DARPA-SSITH-Demonstrators/SSITH-FETT-Target/issues/176) to ensure that we’re getting coverage of code as it will be deployed (as we know that LLVM exercises the hardware a bit differently, that there are different toolchain bugs, etc).
@rtadros-Galois you are assigned to this issue in GitKraken, and you were assigned on GitHub at one point in time, then you unassigned yourself. (1) Should you own this ticket? (2) How and why did you unassign? (3) Is there something fishy going on with GitKraken-GitHub sync, even for you, whose userids match?
@kiniry I haven't unassigned it. I am re-acknowledging the assignment :)
Github shows that I have unassigned it. I don't remember doing that. Assignees porting between gitkraken and github seems fishier than we first thought.
See my comment on #19. Will this be accomplished in this sprint?
Yes. This week, we'll have all our testing done. I am not aware of how cloudGFE will hook their CI to our testing mechanism.
JameyH at MIT, Bluespec performers, and DylanH would all love to have a smoketest for FreeBSD that is aligned with FETT tool requirements.
By smoketest I mean a FETT tool command that triggers some behavior that exercises all SoC devices: Ethernet, UART, block storage, and random number generation.
This issue is paralleled by sister issues for Linux (#17) and FreeRTOS (#15).
I'm assigning these issues initially to @rtadros-Galois for triage and assignment to Target team member(s).