Greetings.test Failure: Difference between revisions
(Created page with ">> @emil.gautier @techielauren just wanted to call your attention to our attempts to get `greetings.test` up and running in our test environment? @coffeemaw let me know that the test run detailed in `d0cb775ce8cd462f9432bd77d7aee1e4.logs` is failing on all tests. Is there something we're failing to understand? Maybe something is misconfigured? >> @techielauren Reading over the logs and then checking the code in `greetings.test`, I have to remind EVERYONE (@team-cloud-qa...") |
No edit summary |
||
Line 25: | Line 25: | ||
>> @emil.gautier | >> @emil.gautier | ||
OK, just wanna make sure we're on track for review. | OK, just wanna make sure we're on track for review. | ||
[[Sprint 1]] |
Revision as of 19:23, 10 October 2024
>> @emil.gautier @techielauren just wanted to call your attention to our attempts to get `greetings.test` up and running in our test environment? @coffeemaw let me know that the test run detailed in `d0cb775ce8cd462f9432bd77d7aee1e4.logs` is failing on all tests. Is there something we're failing to understand? Maybe something is misconfigured?
>> @techielauren Reading over the logs and then checking the code in `greetings.test`, I have to remind EVERYONE (@team-cloud-qa) that ALL motion vector and motor kinematics permissions ARE DENIED for this project.
We can't expect motion safety in our final production environment. So we don't get any here.
>> @emil.gautier We're only trying to deliver a proof of concept though. This is just the basic queueing management system and that won't be in production either right?
>> @coffeemaw Right. My bad Lauren. Looks like we'll have to go back to the drawing board for these tests.
>> @emil.gautier @coffeemaw we aren't sure if we need to redo the test concepts yet. Let's all get on the same page before we keep moving.
>> @techielauren @coffeemaw Sounds good. Honestly you could probably just make the bots say the alphabet and check that that works. Start from something super basic.
>> @coffeemaw Will do. @emil.gautier I just forgot we can't have any of the drones move during the tests. @techielauren is right. It won't take more than thirty minutes to an hour to write up the test anyways.
>> @emil.gautier OK, just wanna make sure we're on track for review.