cascading-pr from https://codeberg.org/forgejo/forgejo refs/pull/3059/head to forgejo/forgejo-3059 #146

Open
cascading-pr wants to merge 4 commits from cascading-pr/forgejo/forgejo-3059 into main
cascading-pr commented 2024-04-06 07:21:57 +00:00 (Migrated from code.forgejo.org)

cascading-pr from https://codeberg.org/forgejo/forgejo refs/pull/3059/head

verify runs-on variable expansion happens on scheduled workflows

  • Adds the TEST_SCHEDULE_RUNSON=docker variable
  • Use it in a scheduled job
  • Run this test only with Forgejo versions greater or equal to 8.0
    otherwise it is not implemented yet

image

cascading-pr from https://codeberg.org/forgejo/forgejo refs/pull/3059/head verify runs-on variable expansion happens on scheduled workflows * Adds the TEST_SCHEDULE_RUNSON=docker variable * Use it in a scheduled job * Run this test only with Forgejo versions greater or equal to 8.0 otherwise it is not implemented yet ![image](/attachments/b96f6b31-efeb-4b51-b9d8-5e3995d48bb4)
earl-warren commented 2024-04-06 13:32:46 +00:00 (Migrated from code.forgejo.org)

@thefox it looks like this error is relevant.

2024/04/06 10:21:42 ...rvices/cron/tasks.go:93:1() [E] PANIC whilst running task: start_schedule_tasks Value: runtime error: invalid memory address or nil pointer dereference

is relevant.

@thefox it looks like [this error](https://code.forgejo.org/forgejo/end-to-end/actions/runs/1018/jobs/1#jobstep-4-1013) is relevant. ``` 2024/04/06 10:21:42 ...rvices/cron/tasks.go:93:1() [E] PANIC whilst running task: start_schedule_tasks Value: runtime error: invalid memory address or nil pointer dereference ``` is relevant.
thefox commented 2024-04-06 14:09:31 +00:00 (Migrated from code.forgejo.org)

My guess is that the repo wasn't loaded. I'll look into it, maybe the non-scheduled way had an init before which I missed.
EDIT:
That indeed was the case

My guess is that the repo wasn't loaded. I'll look into it, maybe the non-scheduled way had an init before which I missed. EDIT: That indeed was the case
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin cascading-pr/forgejo/forgejo-3059:cascading-pr/forgejo/forgejo-3059
git checkout cascading-pr/forgejo/forgejo-3059

Merge

Merge the changes and update on Forgejo.
git checkout main
git merge --no-ff cascading-pr/forgejo/forgejo-3059
git checkout main
git merge --ff-only cascading-pr/forgejo/forgejo-3059
git checkout cascading-pr/forgejo/forgejo-3059
git rebase main
git checkout main
git merge --no-ff cascading-pr/forgejo/forgejo-3059
git checkout main
git merge --squash cascading-pr/forgejo/forgejo-3059
git checkout main
git merge --ff-only cascading-pr/forgejo/forgejo-3059
git checkout main
git merge cascading-pr/forgejo/forgejo-3059
git push origin main
Sign in to join this conversation.
No reviewers
No labels
l1
l2
No milestone
No project
No assignees
1 participant
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: earl-warren/end-to-end#146
No description provided.