DMC/scipro
7
0
Fork 0
Code Issues 32 Pull Requests 3 Actions Projects 1 Wiki Activity

WIP: Report test coverage on pull request #58

Closed
ansv7779 wants to merge 2 commits from test-coverage into develop
pull from: test-coverage
merge into: DMC:develop
Conversation 3 Commits 2 Files Changed 2 +54
ansv7779 commented 2024-12-05 10:38:33 +01:00
Owner
Copy Link
No description provided.
ansv7779 added 1 commit 2024-12-05 10:38:33 +01:00
Report test coverage on pull request
Some checks failed
Build and test / build-and-test (push) Has been cancelled
Details
9ee361c65d
ansv7779 force-pushed test-coverage from 9ee361c65d to 6d2a78364e 2024-12-05 10:40:40 +01:00 Compare
ansv7779 force-pushed test-coverage from 6d2a78364e to 81ee54a427 2024-12-05 10:41:17 +01:00 Compare
ansv7779 force-pushed test-coverage from 81ee54a427 to 1dea1ab83b 2024-12-05 10:43:02 +01:00 Compare
ansv7779 added 1 commit 2024-12-05 10:59:00 +01:00
Turn on debug-mode
Some checks failed
Build and test / build-and-test (push) Has been cancelled
Details
Coverage report / coverage-report (pull_request) Successful in 8m43s
Details
12319da38c
ansv7779 commented 2024-12-05 12:15:52 +01:00
Author
Owner
Copy Link

Will have to find another way until https://github.com/go-gitea/gitea/issues/32723 is resolved since it prevents comparing to commit hashes which is what the JaCoCo action needs.

Will have to find another way until https://github.com/go-gitea/gitea/issues/32723 is resolved since it prevents comparing to commit hashes which is what the JaCoCo action needs.
ansv7779 commented 2024-12-19 19:52:11 +01:00
Author
Owner
Copy Link

1.23 has been released which include the fix but it is still in release candidate status, but soon.

1.23 has been released which include the fix but it is still in release candidate status, but soon.
ansv7779 commented 2025-01-10 13:33:16 +01:00
Author
Owner
Copy Link

This is unrealistic for now with the chosen action. The Gitea API differs too much from the GitHub API and the coverage action relies on those differences.

This is unrealistic for now with the chosen action. The Gitea API differs too much from the GitHub API and the coverage action relies on those differences.
ansv7779 closed this pull request 2025-01-10 13:33:16 +01:00
Some checks failed
Build and test / build-and-test (push) Has been cancelled
Details
Coverage report / coverage-report (pull_request) Successful in 8m43s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
discussion
duplicate
This issue or pull request already exists
enhancement
New feature
frozen
The issue is not solved, but it will be investigated in the future it the issue arises again
help wanted
Need some help
invalid
Something is wrong
new
To be discussed at the next meeting
po
approved
po
needed
question
More information is needed
size
1
size
2
size
3
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DMC/scipro#58
No description provided.
Delete Branch "test-coverage"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?