785: Failed tag updates are not automatically retried

[rwestberg]

When the issue notifier encounters an error during tag processing, it flags the tag as in need of retry. However, the retry flag was not actually checked in subsequent runs.

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed

Issue

• SKARA-785: Failed tag updates are not automatically retried

Reviewers

• Erik Helin (@edvbld - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/skara pull/1060/head:pull/1060
$ git checkout pull/1060

[bridgekeeper]

👋 Welcome back rwestberg! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (e1897d1)

[edvbld]

Looks good!

[openjdk]

@rwestberg This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

🔍 One or more changes in this pull request modifies files in areas of the source code that often require two reviewers. Please consider if this is the case for this pull request, and if so, await a second reviewer to approve this pull request before you integrate it.

🌎 Applicable reviewers for one or more changes in this pull request are spread across multiple different time zones. Please consider waiting with integrating this pull request until it has been out for review for at least 24 hours to give all reviewers a chance to review the pull request.

After integration, the commit message for the final commit will be:

785: Failed tag updates are not automatically retried

Reviewed-by: ehelin

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 2 new commits pushed to the master branch:

• 763af0c: bot: don't run watchdogTrigger test on Windows
• 902698a: vcs: add ReadOnlyRepository.commitMetadataFor

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[rwestberg]

/integrate

[openjdk]

@rwestberg Since your change was applied there have been 22 commits pushed to the master branch:

• d4d23aa: 323: ArgumentParser should support --version
• cd84028: cli: make it possible to configure forge name
• f16663b: 744: The "Webrevs" link in the PR has confusing link to the changes for just one commit
• 60eb3a6: cli: add --atomic and --manual to git-pr-integrate
• e6502c8: 757: git webrev with file list fails if any file has not changed
• fedf7ad: 823: git fork --setup-pre-push-hook => FAIL
• 77cbb92: pr: add /integrate auto
• a66ee40: Really fix so tests ignore .gitconfig
• 0cf4834: Decrease log level for harmless warning
• 0a43128: pr: do not run commit commands when .jcheck/conf is missing
• ... and 12 more: https://git.openjdk.java.net/skara/compare/b39d50b1475cb91995ae26f8150dfebf9ee620f3...master

Your commit was automatically rebased without conflicts.

Pushed as commit ffeba1a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.