Skip to content
Snippets Groups Projects

Add issue triage

Open Add issue triage
deep.chatterjee/gwcelery:setup-triage into main
Open Deep Chatterjee requested to merge deep.chatterjee/gwcelery:setup-triage into main

Intended effect

[2025-02-28 11:35:02,052 |    INFO] (gwcelery|triage): connected to https://git.ligo.org/api/v4
[2025-02-28 11:35:02,052 |    INFO] (gwcelery|triage): Getting inactive issues
[2025-02-28 11:35:02,394 |    INFO] (gwcelery|triage): Issue #249 inactive for 692 days. Title: Allow alert to be assembled with sky map from a different event than FAR/p-astro/EM-bright.
[2025-02-28 11:35:02,394 | WARNING] (gwcelery|triage): Closing #249
[2025-02-28 11:35:02,395 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,395 |    INFO] (gwcelery|triage): Issue #252 inactive for 638 days. Title: Data file links in comments for PNGs uploaded to GraceDB are not versioned.
[2025-02-28 11:35:02,395 | WARNING] (gwcelery|triage): Closing #252
[2025-02-28 11:35:02,395 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,395 |    INFO] (gwcelery|triage): Issue #420 inactive for 745 days. Title: Review traceability.
[2025-02-28 11:35:02,395 | WARNING] (gwcelery|triage): Closing #420
[2025-02-28 11:35:02,395 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,396 |    INFO] (gwcelery|triage): Issue #503 inactive for 808 days. Title: Nagios check for task queue pileup doesn't appear flag superevent worker going down.
[2025-02-28 11:35:02,396 | WARNING] (gwcelery|triage): Closing #503
[2025-02-28 11:35:02,396 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,396 |    INFO] (gwcelery|triage): Issue #601 inactive for 638 days. Title: Test coverage in views.
[2025-02-28 11:35:02,396 | WARNING] (gwcelery|triage): Closing #601
[2025-02-28 11:35:02,396 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,396 |    INFO] (gwcelery|triage): Issue #619 inactive for 638 days. Title: Update the wiki page with the meaning of the labels..
[2025-02-28 11:35:02,397 | WARNING] (gwcelery|triage): Closing #619
[2025-02-28 11:35:02,397 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,397 |    INFO] (gwcelery|triage): Issue #659 inactive for 367 days. Title: ValueError: TimeSeries with span [1371903775.645935 ... 1371903785.645935) does not cover requested interval ....
[2025-02-28 11:35:02,397 | WARNING] (gwcelery|triage): Closing #659
[2025-02-28 11:35:02,397 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,397 |    INFO] (gwcelery|triage): Issue #716 inactive for 399 days. Title: O4 superevents that failed to be sent to GCN-kafka.
[2025-02-28 11:35:02,397 | WARNING] (gwcelery|triage): Closing #716
[2025-02-28 11:35:02,397 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,398 |    INFO] (gwcelery|triage): Issue #744 inactive for 370 days. Title: Strange igwn alert bootstep behavior.
[2025-02-28 11:35:02,398 | WARNING] (gwcelery|triage): Closing #744
[2025-02-28 11:35:02,398 |   DEBUG] (gwcelery|triage):     not closed (dry run)
[2025-02-28 11:35:02,398 |    INFO] (gwcelery|triage): Issue #767 inactive for 370 days. Title: Add test coverage for ignoring earlywarning events with rapidpe.
[2025-02-28 11:35:02,398 | WARNING] (gwcelery|triage): Closing #767
[2025-02-28 11:35:02,398 |   DEBUG] (gwcelery|triage):     not closed (dry run)
  • Integrate with CI

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
.gitlab-ci.yml
20 23 - test
21 24 - docker
22 25 - deploy
26 - triage
27
28 triage:
29 extends:
30 - .python_base
31 stage: triage
32 rules: !reference [.rules, rules]
  • Deep Chatterjee
    Deep Chatterjee @deep.chatterjee ·
    Author Owner

    This rule should be

    Suggested change
    32 rules: !reference [.rules, rules]
    32 rules:
    33 - if: '$CI_PIPELINE_SOURCE == "schedule" && $CI_PROJECT_ROOT_NAMESPACE == "emfollow"'
    34

    However, leave this rule to run on MRs to see the effect in the pipeline output for the review. Apply changes once review is done.

  • Please register or sign in to reply
  • Deep Chatterjee marked this merge request as ready

    marked this merge request as ready

  • Deep Chatterjee changed title from WIP: add issue triage to Add issue triage

    changed title from WIP: add issue triage to Add issue triage

  • Deep Chatterjee requested review from @cody.messick

    requested review from @cody.messick

  • Deep Chatterjee requested review from @leo-singer

    requested review from @leo-singer

  • Deep Chatterjee
    Deep Chatterjee @deep.chatterjee ·
    Author Owner

    @leo-singer @cody.messick a quick note: I have not set up the pipeline schedule yet for the triage stage. I have left the issue triage to dry run as a part of the MR. If this looks good, I will add a schedule pipeline and change the rule of the triage stage to only run on schedule.

  • Deep Chatterjee requested review from @geoffrey.mo, @sushant.sharma-chaudhary, and @brandon.piotrzkowski

    requested review from @geoffrey.mo, @sushant.sharma-chaudhary, and @brandon.piotrzkowski

  • Deep Chatterjee
    Deep Chatterjee @deep.chatterjee started a thread on the diff
    • triage/triage.py 0 → 100644
    94 sort="asc"
    95 ):
    96 last_update_time = last_update(issue)
    97 time_now = datetime.datetime.now()
    98 inactive_time = time_now - last_update_time
    99 if inactive_time > datetime.timedelta(days=ISSUE_ACTIVE_DURATION):
    100 LOGGER.info(
    101 "Issue #%s inactive for %d days. "
    102 "Title: %s." % (
    103 issue.attributes['iid'],
    104 inactive_time.days,
    105 issue.attributes['title'],
    106 )
    107 )
    108 LOGGER.warning("Closing #%s" % (issue.attributes['iid']))
    109 close_issue(issue)
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
    • Please register or sign in to reply