github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

TestSearchRepos is broken #3347

New Issue
Closed
opened 2025-11-02 05:09:26 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 05:09:26 -06:00
Owner
Copy Link

Originally created by @zeripath on GitHub (May 17, 2019).

  • Gitea version (or commit ref):1.9.0+dev-262-g96b412bb8

Description

TAGS="bindata sqlite sqlite_unlock_notify" make build test-sqlite\#TestSearchRepo fails

Originally created by @zeripath on GitHub (May 17, 2019). - Gitea version (or commit ref):1.9.0+dev-262-g96b412bb8 ## Description `TAGS="bindata sqlite sqlite_unlock_notify" make build test-sqlite\#TestSearchRepo` fails
GiteaMirror added the type/testingtype/bug labels 2025-11-02 05:09:26 -06:00
GiteaMirror commented 2025-11-02 05:09:27 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 17, 2019):

This has been broken since at least v1.7.0-dev and likely earlier.

@zeripath commented on GitHub (May 17, 2019): This has been broken since at least v1.7.0-dev and likely earlier.
GiteaMirror commented 2025-11-02 05:09:27 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 17, 2019):

I've just spent all evening trying to figure this out and have failed.

The closest I came to actually getting user2/repo1 indexed was after forcibly updating the repo I manage to get to:

6fb58a8cdc/models/repo_indexer.go (L155)

But I never got past this before the search occurred.

Likely there is a timing issue or locking issue her but I don't understand enough to make this work.

@lunny do you have any idea how to solve this? @kolaente is this the issue you're experiencing on golang-ci?

@zeripath commented on GitHub (May 17, 2019): I've just spent all evening trying to figure this out and have failed. The closest I came to actually getting user2/repo1 indexed was after forcibly updating the repo I manage to get to: https://github.com/sanjid133/gitea/blob/6fb58a8cdcd76aa45902e50da8f2b450fe9d3d35/models/repo_indexer.go#L155 But I never got past this before the search occurred. Likely there is a timing issue or locking issue her but I don't understand enough to make this work. @lunny do you have any idea how to solve this? @kolaente is this the issue you're experiencing on golang-ci?
GiteaMirror commented 2025-11-02 05:09:27 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (May 17, 2019):

This issue is preventing #6961 from passing ci

@zeripath commented on GitHub (May 17, 2019): This issue is preventing #6961 from passing ci
GiteaMirror commented 2025-11-02 05:09:27 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 18, 2019):

I know this issue and will also spend some time to investigate it.

@lunny commented on GitHub (May 18, 2019): I know this issue and will also spend some time to investigate it.
GiteaMirror commented 2025-11-02 05:09:28 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 18, 2019):

@zeripath It could be related, but the tests which are failing in #6418 are TestBleveSearchIssues, unit tests, not integration tests.

@kolaente commented on GitHub (May 18, 2019): @zeripath It could be related, but the tests which are failing in #6418 are `TestBleveSearchIssues`, unit tests, not integration tests.
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/bug 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#3347
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?