forgejo/runner
31
87
Fork 91
Code Issues 38 Pull requests 9 Releases 81 Packages 1 Activity Actions

feat: include all integration tests in make integration-test #1247

Merged
mfenniak merged 1 commit from aahlenst/runner:extend-integration-test into main 2025-12-28 20:53:04 +00:00
Conversation 1 Commits 1 Files changed 2 +13 -5
aahlenst commented 2025-12-28 13:50:43 +00:00
Member
Copy link

Previously, integration-test did not run all integration tests. It lacked all those contributed by ./act and there was no target that included them. This change introduces two new targets that are included in integration-test: runner-integration-test (identical with the former integration-test) and act-integration-test. That allows running them independently which is useful for CI.

  • features
    • PR: feat: include all integration tests in make integration-test
Previously, `integration-test` did not run all integration tests. It lacked all those contributed by `./act` and there was no target that included them. This change introduces two new targets that are included in `integration-test`: `runner-integration-test` (identical with the former `integration-test`) and `act-integration-test`. That allows running them independently which is useful for CI. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - features - [PR](https://code.forgejo.org/forgejo/runner/pulls/1247): <!--number 1247 --><!--line 0 --><!--description ZmVhdDogaW5jbHVkZSBhbGwgaW50ZWdyYXRpb24gdGVzdHMgaW4gYG1ha2UgaW50ZWdyYXRpb24tdGVzdGA=-->feat: include all integration tests in `make integration-test`<!--description--> <!--end release-notes-assistant-->
aahlenst force-pushed extend-integration-test from 069f5775c5
Some checks failed
issue-labels / release-notes (pull_request_target) Successful in 10s
Details
checks / validate mocks (pull_request) Successful in 37s
Details
checks / integration tests (docker-latest) (pull_request) Failing after 44s
Details
checks / build and test (pull_request) Successful in 47s
Details
checks / integration tests (docker-stable) (pull_request) Failing after 47s
Details
checks / validate pre-commit-hooks file (pull_request) Successful in 45s
Details
checks / runner exec tests (pull_request) Successful in 29s
Details
checks / runner integration tests (pull_request) Successful in 5m59s
Details
to b9a9016136
All checks were successful
checks / validate mocks (pull_request) Successful in 32s
Details
checks / build and test (pull_request) Successful in 42s
Details
checks / validate pre-commit-hooks file (pull_request) Successful in 40s
Details
checks / runner exec tests (pull_request) Successful in 31s
Details
checks / runner integration tests (pull_request) Successful in 6m13s
Details
checks / integration tests (docker-latest) (pull_request) Successful in 10m22s
Details
checks / integration tests (docker-stable) (pull_request) Successful in 11m46s
Details
cascade / forgejo (pull_request_target) Has been skipped
Details
cascade / debug (pull_request_target) Has been skipped
Details
cascade / end-to-end (pull_request_target) Has been skipped
Details
issue-labels / release-notes (pull_request_target) Successful in 5s
Details
2025-12-28 13:59:13 +00:00 Compare
mfenniak approved these changes 2025-12-28 20:52:28 +00:00
mfenniak left a comment
Owner
Copy link

Great approach, thanks! 👍

Great approach, thanks! 👍
Sign in to join this conversation.
Reviewers
No reviewers
mfenniak
Labels
Clear labels   
FreeBSD

   
Kind/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Chore

It is no fun but it needs to be done, this is a chore.

  
Kind/DependencyUpdate

for pull requests that are created by renovate when updating a dependency

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

  
Windows

Windows ports is an independent project, see https://github.com/Crown0815/Forgejo-runner-windows-builder

  
linux-powerpc64le

powerpc64le

  
linux-riscv64

   
linux-s390x

   
run-end-to-end-tests

Run https://code.forgejo.org/forgejo/end-to-end with a runner compiled from this pull request

  
run-forgejo-tests

Run https://codeberg.org/forgejo/forgejo tests importing the runner from this pull request

No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/runner!1247
No description provided.