Added by dzedro over 2 years ago. Updated over 2 years ago.
0%
Description
Allegedly it's because JeOS: Development group was moved from non-devel to devel group. [1]
I guess it's blocking approx. half of updates on http://dashboard.qam.suse.de/blocked
[1] https://chat.suse.de/channel/qac/thread/MqX5SfykQzpNokELR?jump=J2iRPTz9nZqvrRYsv
I'm sorry, I don't understand. Could you please add more details? I assume you see a problem but I don't know what the problem is. What is the expected result?
okurz wrote:
I'm sorry, I don't understand. Could you please add more details? I assume you see a problem but I don't know what the problem is. What is the expected result?
When you open dashboard http://dashboard.qam.suse.de/blocked and search for JeOS: Development, this group should be not there.
@osukup is this a regression due to the ill-communicated move of incident test approval from openQABot to bot-ng? If yes, please revert that ASAP
https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/9
dashboard_db=# DELETE FROM openqa_jobs WHERE job_group='JeOS: Development';
DELETE 180
dashboard_db=#
this more looks like data from rabbitmq pollutes database with unneded groups @kraih ?
osukup wrote:
this more looks like data from rabbitmq pollutes database with unneded groups @kraih ?
There is no data added to the database from RabbitMQ. There is just one query that updates the state of jobs, that't it.
UPDATE openqa_jobs SET status = ?, updated = NOW() WHERE job_id = ? RETURNING job_id;
kraih wrote:
osukup wrote:
this more looks like data from rabbitmq pollutes database with unneded groups @kraih ?
There is no data added to the database from RabbitMQ. There is just one query that updates the state of jobs, that't it.
UPDATE openqa_jobs SET status = ?, updated = NOW() WHERE job_id = ? RETURNING job_id;oh ... thx for info,
conditions for ignoring jobs simplified and database manually cleaned ..