action #123797

Continuous retriggers of GNOME:Next openQA tests

Added by okurz about 2 months ago. Updated about 1 month ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:



Dimstar reached out to me noticing that is recurringly retriggered.

Impact is wasting ressources although likely this will not have a worse effect than that.


This happens because always detects a change in content in the URL "*", see Likely we also can not use the "last-modified" date as curl --head "" shows that MirrorCache does not seem to deliver that.



#1 Updated by okurz about 2 months ago

  • Description updated (diff)

I enabled "Throttle builds" in with max. 6 builds/day while allowing user triggered builds to skip the rate limit

#2 Updated by okurz about 2 months ago

  • Description updated (diff)

#3 Updated by okurz about 2 months ago

  • Status changed from New to In Progress
  • Assignee set to okurz

Previously the "URLTrigger" monitored* but this is now served by MirrorCache which has no "last-modified" timestamp but also the content always changes as the generated HTML page shows a "csrf-token" changing on each call. I found that by calling

diff <(curl -sS "*") <(curl -sS "*")

which yields:

<       <meta name="csrf-token" content="3a72819665c9adb750ad4d5e8054961c5b1c3efc" />
>       <meta name="csrf-token" content="0b17cbf73c393a1baa4daee989158038caeafc7c" />

I switched the URLTrigger to inspect the URL content of which is small enough to not be a problem to be recurringly downloaded. Let's see if this works.

And I created

#4 Updated by openqa_review about 2 months ago

  • Due date set to 2023-02-14

Setting due date based on mean cycle time of SUSE QE Tools

#5 Updated by okurz about 2 months ago

  • Status changed from In Progress to Feedback

The current build history in looks like we trigger as many as the build throttle allows. But checking for example the latest finished build from Feb 3, 2023, 12:53:00Z, comparing to the latest modified is 1320Z so for sure there had been changes today. Let's monitor for longer.

#6 Updated by okurz about 1 month ago

  • Due date deleted (2023-02-14)
  • Status changed from Feedback to Resolved

It seems the process is working fine. We seem to have sometimes multiple builds per day of GNOME Next but maybe we don't need that. So I will just keep the build throttle in place.

Also available in: Atom PDF