chore(test): disable flaky Forgejo e2e test by jdx · Pull Request #8211 · jdx/mise

jdx · 2026-02-17T13:54:28Z

Summary

Disable the Forgejo e2e test (e2e/backend/test_forgejo) by adding exit 0 at the top, as it is flaky due to intermittent Codeberg API issues

Test plan

CI passes with the test disabled

🤖 Generated with Claude Code

Note

Low Risk
Low risk: only disables an end-to-end test by exiting early, with no production code changes. The main impact is reduced CI coverage for the Forgejo backend until the flakiness is addressed.

Overview
Disables the e2e/backend/test_forgejo end-to-end test by adding an early exit 0, citing intermittent Forgejo/Codeberg API flakiness.

All existing Forgejo backend assertions remain in the file but are now skipped in CI.

^{Written by Cursor Bugbot for commit 3a3bd07. This will update automatically on new commits. Configure here.}

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

gemini-code-assist · 2026-02-17T13:54:40Z

Summary of Changes

Hello @jdx, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue with a consistently failing end-to-end test by temporarily disabling it. The Forgejo e2e test was causing CI instability due to unreliable external API dependencies, and this change ensures that the continuous integration pipeline remains stable and reliable while a more permanent solution is considered.

Highlights

Flaky Test Disablement: The e2e/backend/test_forgejo end-to-end test has been temporarily disabled due to its flakiness, which is attributed to intermittent issues with the Codeberg API.

Changelog

e2e/backend/test_forgejo
- Disabled the test by adding an exit 0 command at the beginning of the script.

Activity

The author has confirmed that CI passes with the test disabled, indicating the change achieves its immediate goal of stabilizing the pipeline.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request disables a flaky e2e test for Forgejo by adding an exit 0 at the beginning of the test script. While this is a valid approach, my feedback focuses on improving the visibility of this disabled test in the CI logs. I've suggested adding a warning message to make it clear that the test is being skipped rather than just passing quickly. This will help with future maintenance and tracking of disabled tests.

gemini-code-assist · 2026-02-17T13:55:58Z

e2e/backend/test_forgejo

+# Disabled: Forgejo tests are flaky due to intermittent API issues
+exit 0


Using exit 0 makes the test appear as a fast success, which can be misleading. Adding a warn message will make it clear in the CI logs that the test is intentionally skipped, improving visibility for future maintenance.

# Disabled: Forgejo tests are flaky due to intermittent API issues warn "Forgejo e2e test is temporarily disabled due to flakiness." exit 0

Copilot

Pull request overview

Disables the flaky Forgejo backend E2E test to prevent intermittent external API failures (Codeberg) from failing CI.

Changes:

Short-circuits e2e/backend/test_forgejo by exiting successfully at the start.
Adds a brief comment explaining why the test is disabled.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-17T13:58:56Z

e2e/backend/test_forgejo

 #!/usr/bin/env bash

+# Disabled: Forgejo tests are flaky due to intermittent API issues
+exit 0


Unconditionally exit 0 makes this test report as a success (✅) even though it never runs, which can hide regressions and is misleading in CI. Consider conditionally skipping only in CI (e.g., if [[ -n ${CI:-} ]]; then ...; return 0; fi) and emitting a warn/notice message so the logs make it obvious the test was skipped/disabled, while still allowing local runs when needed.

Suggested change

exit 0

if [[ -n "${CI:-}" ]]; then

echo "::warning::Skipping Forgejo backend e2e tests: flaky due to intermittent API issues"

exit 0

fi

github-actions · 2026-02-17T14:12:10Z

Hyperfine Performance

`mise x -- echo`

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
`mise-2026.2.15 x -- echo`	25.0 ± 0.7	23.5	32.5	1.02 ± 0.05
`mise x -- echo`	24.6 ± 1.0	23.6	38.4	1.00

`mise env`

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
`mise-2026.2.15 env`	24.7 ± 1.1	23.0	32.4	1.00
`mise env`	24.8 ± 1.0	23.1	39.4	1.00 ± 0.06

`mise hook-env`

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
`mise-2026.2.15 hook-env`	25.6 ± 0.7	24.2	30.1	1.01 ± 0.03
`mise hook-env`	25.3 ± 0.5	24.2	26.8	1.00

`mise ls`

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
`mise-2026.2.15 ls`	23.0 ± 0.6	21.6	25.8	1.00
`mise ls`	23.2 ± 0.5	22.0	24.8	1.01 ± 0.03

`xtasks/test/perf`

Command	mise-2026.2.15	mise	Variance
install (cached)	135ms	136ms	+0%
ls (cached)	83ms	84ms	-1%
bin-paths (cached)	88ms	89ms	-1%
task-ls (cached)	851ms	842ms	+1%

@joaommartins

### 🚀 Features - **(mcp)** add run_task tool for executing mise tasks by @joaommartins in [#8179](#8179) - **(node)** suggest setting node.flavor if the flavor is not found in mirror by @risu729 in [#8206](#8206) ### 🐛 Bug Fixes - **(java)** sort order for shorthand versions by @roele in [#8197](#8197) - **(node)** migrate env vars to settings by @risu729 in [#8200](#8200) - **(registry)** apply overrides in shims by @risu729 in [#8199](#8199) - migrate MISE_CARGO_BINSTALL_ONLY to settings by @risu729 in [#8202](#8202) ### 📚 Documentation - **(doctor)** fix subcommand in an example by @risu729 in [#8198](#8198) ### 📦 Registry - add github backend for typst by @3w36zj6 in [#8210](#8210) ### Chore - **(test)** disable flaky Forgejo e2e test by @jdx in [#8211](#8211)

## Summary - Disable the Forgejo e2e test (`e2e/backend/test_forgejo`) by adding `exit 0` at the top, as it is flaky due to intermittent Codeberg API issues ## Test plan - [ ] CI passes with the test disabled 🤖 Generated with [Claude Code](https://claude.com/claude-code)  --- > [!NOTE] > **Low Risk** > Low risk: only disables an end-to-end test by exiting early, with no production code changes. The main impact is reduced CI coverage for the Forgejo backend until the flakiness is addressed. > > **Overview** > Disables the `e2e/backend/test_forgejo` end-to-end test by adding an early `exit 0`, citing intermittent Forgejo/Codeberg API flakiness. > > All existing Forgejo backend assertions remain in the file but are now skipped in CI. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 3a3bd07. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>  Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

@joaommartins

### 🚀 Features - **(mcp)** add run_task tool for executing mise tasks by @joaommartins in [jdx#8179](jdx#8179) - **(node)** suggest setting node.flavor if the flavor is not found in mirror by @risu729 in [jdx#8206](jdx#8206) ### 🐛 Bug Fixes - **(java)** sort order for shorthand versions by @roele in [jdx#8197](jdx#8197) - **(node)** migrate env vars to settings by @risu729 in [jdx#8200](jdx#8200) - **(registry)** apply overrides in shims by @risu729 in [jdx#8199](jdx#8199) - migrate MISE_CARGO_BINSTALL_ONLY to settings by @risu729 in [jdx#8202](jdx#8202) ### 📚 Documentation - **(doctor)** fix subcommand in an example by @risu729 in [jdx#8198](jdx#8198) ### 📦 Registry - add github backend for typst by @3w36zj6 in [jdx#8210](jdx#8210) ### Chore - **(test)** disable flaky Forgejo e2e test by @jdx in [jdx#8211](jdx#8211)

chore(test): disable flaky Forgejo e2e test

3a3bd07

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Copilot AI review requested due to automatic review settings February 17, 2026 13:54

Copilot started reviewing on behalf of jdx February 17, 2026 13:54 View session

jdx enabled auto-merge (squash) February 17, 2026 13:55

gemini-code-assist bot reviewed Feb 17, 2026

View reviewed changes

Copilot AI reviewed Feb 17, 2026

View reviewed changes

jdx merged commit d309bef into main Feb 17, 2026
43 checks passed

jdx deleted the chore/disable-flaky-forgejo-test branch February 17, 2026 14:07

mise-en-dev mentioned this pull request Feb 17, 2026

chore: release 2026.2.16 #8204

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(test): disable flaky Forgejo e2e test#8211

chore(test): disable flaky Forgejo e2e test#8211
jdx merged 1 commit intomainfrom
chore/disable-flaky-forgejo-test

jdx commented Feb 17, 2026 •

edited by cursor bot

Loading

Uh oh!

gemini-code-assist bot commented Feb 17, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 17, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 17, 2026

Uh oh!

Uh oh!

github-actions bot commented Feb 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		# Disabled: Forgejo tests are flaky due to intermittent API issues
		exit 0

-exit 0
+if [[ -n "${CI:-}" ]]; then
+  echo "::warning::Skipping Forgejo backend e2e tests: flaky due to intermittent API issues"
+  exit 0
+fi

Uh oh!

Conversation

jdx commented Feb 17, 2026 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

gemini-code-assist bot commented Feb 17, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 17, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 17, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Feb 17, 2026

Hyperfine Performance

mise x -- echo

mise env

mise hook-env

mise ls

xtasks/test/perf

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jdx commented Feb 17, 2026 •

edited by cursor bot

Loading

`mise x -- echo`

`mise env`

`mise hook-env`

`mise ls`

`xtasks/test/perf`