-
Notifications
You must be signed in to change notification settings - Fork 14
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
Release rockpi-4b-rk3399 to production with only automated tests #129
Comments
@acostach sorry for all the pings, but this week I'm trying to go through each of the devices and see whats blocking them - I've just tried to run tests on the rockpi testbot, and the DUT supposedly isn't powering on:
This is either because:
|
[acostach] @rcooke-warwick checking now, the device has the green light on, which means it's powered, but the ethernet LEDs are off, so it's not booting. could be due to the mux/sd-card. Can I remove it from the testbot and try boot it with the already flashed sd-card in the mux? |
@rcooke-warwick looks like it might be because of the voltage, I will make a PR to increase it from 5 to 12. On Radxa website they say that it works with 5V but may cause stability issues once the load rises, and this is what I see locally now, it powers off during flashing with 5V but not with 12V. |
nice find @acostach sounds like a good idea to increase it |
[acostach] done, I will merge balena-io-hardware/testbot-sdk-sw#48 once checks pass and then update leviathan worker, after that we can test again. |
@rcooke-warwick I updated the testbotsdk to increase the voltage and also leviathan-worker, where I merged balena-os/leviathan-worker#26 |
[acostach] 1) Is answered, the rig app updated already |
@acostach nice one, the rig did update a while back and I retried the rockpi job, its flashing at the moment, will report back here with the result |
@acostach update, unfortunately it hasn't worked - 12v is coming out of the tesbot but we're still getting: |
[rcooke-warwick] now I'm wondering if there's something going wrong with the detection of if the DUT is on/off ... |
[rcooke-warwick] does the rockpi have ethernet? |
[rcooke-warwick] (I remember the rockpi flashing has worked before, but maybe I'm remembering wrong) |
@rcooke-warwick I plugged and unplugged the cable, it should flash the device once again |
[acostach] I recall we did run tests on this DT before and they were running, provisioning worked |
[acostach] it's not powering off, is the test running normally? |
[rcooke-warwick] which cable did you unplug/replug? |
[acostach] ethernet and usbc |
usb-c is the power cable |
[rcooke-warwick] hmm its just staying "on" now |
@acostach yep, the device names cross wires - I did realize and eventually created and linked a new ticket. Sorry for the noise. |
want me to plug and unplug the power cable @rcooke-warwick ? That would trigger the re-flashing IF the sd-card is switched to DUT |
I already turned the DUT off then on again to try to achieve that @acostach |
[rcooke-warwick] the DUT remained to stay on forever - so for some reason it isn't internally flashing the DUT |
[rcooke-warwick] the device is currently in this state, the test job is still running |
[rcooke-warwick] retrying with fresh slate |
[acostach] ok. if it still doesn't work let me know and I'll hook up the serial cable from my PC to the device and kick the suite, see where it hangs |
@acostach rockpi seems to be flashing now: https://jenkins.product-os.io/job/leviathan-v2-template/4673/console - I've flashed it 3 times from a local test job in a row, and now this jenkins one is running - maybe there was just something loose that got fixed when you unplugged and replugged |
very possible @rcooke-warwick , good thing it's working now, thanks for letting me know as I was just going to connect the serial and restart it |
[rcooke-warwick] @acostach it has been consistently flashing every time last night and this morning. Now we move on to the problem of tests failing. First roadblock is the test here: https://github.com/balena-os/meta-balena/blob/master/tests/suites/os/tests/chrony/index.js#L157 Which has failed both times I've tried it. This test I;m not that familiar with, but here's what I get from it:
just running it again now to get the journal logs to see why that might be happening. |
[rcooke-warwick] furstratingly, that test has now passed... I think it is linked to this issue: balena-os/meta-balena#2758 From what I've seen, in the case of failure, chronyc is started with some sort of wrong permissions:
In the case of the test passing, I never see that message about a disabled command socket |
[rcooke-warwick] on a side note, does anyone know if the rockpi led flashing works? I saw this issue: #10 and also I checked |
@rcooke-warwick the LED is not implemented for the radxa-zero nor rockpi4b so this test can be skipped |
@rcooke-warwick do we have a mechanism to mark a test as not mandatory on a per DT basis? |
@acostach the test runs because in the contract for the rockpi , it is set to LED: true - should I make the PR for the contract to set this to |
@rcooke-warwick yes, let's set it to false. Related thread https://jel.ly.fish/issue-release-rockpi-4b-rk3399-production-automated-tests-6594ff9 |
I pushed the PR and it should merge soon @rcooke-warwick balena-io/contracts#326 |
done, it's merged in the contracts @rcooke-warwick |
thanks @acostach I'll now bump contracts in leviathan - which will autobump in meta balena--- eventually it will reach the rockpi repo ;P |
@acostach @alexgg looks like rockpi4b can now pass the entire test suite: https://jenkins.product-os.io/job/leviathan-v2-template/5140/ Although it looks like the tests won't run on |
[rcooke-warwick] I can see you've added the rockpro64 into the rig - does this device successfully flash with the testbot? |
[rcooke-warwick] was |
@rcooke-warwick yes, looks like it was renamed from balena-rockpi to balena-radxa Some more ethernet switches and cables have been ordered and are on their way here, currently the the RockPro64 in the rig is not connected via ethernet. |
[klutchell] undefined
The text was updated successfully, but these errors were encountered: