github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-10 13:56:06 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Integration test for MySQL is not configured correctly #2460

New Issue
Closed
opened 2025-11-02 04:37:06 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 04:37:06 -06:00
Owner
Copy Link

Originally created by @typeless on GitHub (Oct 28, 2018).

Not sure if it is deliberate or not, the test-mysql tag in .drone.yml is declared twice. As a result, it seems that the integration test for MySQL does not run. What has been run is actually make integration-test-coverage.

Originally created by @typeless on GitHub (Oct 28, 2018). Not sure if it is deliberate or not, the `test-mysql` tag in `.drone.yml` is declared twice. As a result, it seems that the integration test for MySQL does not run. What has been run is actually `make integration-test-coverage`.
GiteaMirror added the type/testing label 2025-11-02 04:37:06 -06:00
GiteaMirror commented 2025-11-02 04:37:07 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Oct 29, 2018):

One is only run when the branch is master, and the other is run several other cases (see when part of the yaml for more details).

Now, I'm not sure if that is deliberate (why only mysql in that case), and so I will leave this open in case anyone has insight into it.

Thank you for raising this ticket.

@techknowlogick commented on GitHub (Oct 29, 2018): One is only run when the branch is master, and the other is run several other cases (see `when` part of the yaml for more details). Now, I'm not sure if that is deliberate (why only mysql in that case), and so I will leave this open in case anyone has insight into it. Thank you for raising this ticket.
GiteaMirror commented 2025-11-02 04:37:07 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Nov 13, 2018):

Yes it is intended so as when pushed to master and for pulls it calculate test coverage but for tags not

@lafriks commented on GitHub (Nov 13, 2018): Yes it is intended so as when pushed to master and for pulls it calculate test coverage but for tags not
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/testing
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2460
Delete Branch "%!s()"

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?