ssrg-bamboo `test` and ssrg-bamboo `proof` actions don't seem to be working about ci-actions

[nomadeel]

Taking a look now.

[kent-mcleod]

seL4/seL4#381 (comment)

[lsf37]

@nomadeel could you please have a look at what's wrong with the bot next week? I don't have access any more. (Happy to help)

[kent-mcleod]

Also seL4/seL4#365 (comment)

[nomadeel]

Seems like the docker container for the bot was never run, I'll try deploying it on the TS Bamboo VM and see if it works.

[kent-mcleod]

Also seL4/seL4#409 (comment)

[nomadeel]

I think I have it running now, let me test it out now.

[nomadeel]

Looks like it's working? seL4/seL4#409 (comment)

[lsf37]

Yes! Very nice.

[lsf37]

Let's see if it also reports results, but when it does we can close here. It has nicely remembered all the missed invocations, it seems.

[kent-mcleod]

No results have been reported yet.

[lsf37]

Yeah, not a good sign. @nomadeel did say there was a huge Bamboo backlog, so something might have gotten stuck somewhere.

[nomadeel]

It's working, just that the results are now in the checks section instead of being reported via a comment.

[lsf37]

It's working, just that the results are now in the checks section instead of being reported via a comment.

The bot should still be responding, though. So the tests kicked off correctly, and it's running on Bamboo (which makes it show up in status), but the bot is not picking up on completed tests (or for the proofs not responding at all). Does the bot log file say anything enlightening?

[kent-mcleod]

The bot still doesn't seem to be working: seL4/seL4#381 (comment)

[lsf37]

It looks like the bot works again.

With the sel4sim action, the ssrg-bot test should now not be necessary any more. I'll have a look at an AWS setup from GitHub for the proofs today and tomorrow. It'll take a bit longer than that to switch everything to that, including the proof testboard, but when we are there, we should be able to retire the bot.