`drone queue ls` show wrong status (pending)

Drone Support
1

Hi!
I have tested Splunk! Could not find newly deployed instances but then looking closer to the sqlite db and confirmed by the drone UI, the build items are success/error but not pending.

So this may be a problem related with the drone-cli?

Here is the output:

❯ drone queue ls
item #134
Status: pending
Machine:
OS: linux
Arch: amd64
Variant:
Version:

And the corresponding jobs:

screenshot_20201112_161633
screenshot_20201112_161633962×89 9.62 KB

Thanks!

2

drone queue ls returns a list of pending stages, where the id represents the stage id. The screenshot you provided shows a build and build number. These are different objects and ids.

3

Wow, ok sorry for that!
But then how can I see those pending stages in the UI?
And how can I clean them? The CI is all green an nothing should be pending ATM…

4

you can query the database to find the associated build

select * from builds where build_id IN (
  select stage_build_id from stages where stage_id = 134
)
5 
sqlite> select * from builds where build_id IN ( select stage_build_id from stages where stage_id = 134 );
138|1|@hook|97|0|error||push||https://git.example.com/|0||test
|0000000000000000000000000000000000000000|303d2476b84e0d57cb8a319a0ec8902a3f6a26e4|refs/heads/drone-ci-exec||drone-ci-exec|drone-ci-exec|faust|faust|faustin@example.com|https://git.example.com/user/avatar/faust/-1|faust||null|0|0|1605028084|1605028084|1||0

So the status should be “error”?
Anyway, this is a fresh installation and I had some problem with runner not connecting because of a wrong nftables configuration. Is there a way to clean the build history without loosing the rest (repositories configuration, token etc. ?)

Thanks for your help!

6

no need to reset data. you can instead update the individual record

update stages set stage_status = 'error' where stage_id = 134
7

Ok al clear now, thanks again for your help and this great piece of software!