github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #137] [MERGED] Skip failing test suites #3040

New Issue
Closed
opened 2026-02-28 20:35:26 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:35:26 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/137
Author: @TomAFrench
Created: 7/24/2022
Status: ✅ Merged
Merged: 8/24/2022
Merged by: @TomAFrench

Base: master ← Head: skip-failing-test-suites

📝 Commits (2)

  • c40b5e4 ci: run tests on github actions
  • 5a49d65 test: skip failing test suites

📊 Changes

6 files changed (+26 additions, -129 deletions)

View changed files

➖ .circleci/config.yml (+0 -121)
➕ .github/workflows/test.yml (+18 -0)
📝 packages/loot-core/src/server/accounts/sync.test.js (+2 -2)
📝 packages/loot-core/src/server/accounts/transfer.test.js (+1 -1)
📝 packages/loot-core/src/server/main.test.js (+3 -3)
📝 packages/loot-core/src/server/sync/sync.test.js (+2 -2)

📄 Description

Builds on top of #202 .

We've got a number of test suites failing at the minute so the test CI isn't particularly helpful at the minute as every commit will fail. To avoid this masking new tests failing I feel we should skip these failing test suites until they're fixed.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/137 **Author:** [@TomAFrench](https://github.com/TomAFrench) **Created:** 7/24/2022 **Status:** ✅ Merged **Merged:** 8/24/2022 **Merged by:** [@TomAFrench](https://github.com/TomAFrench) **Base:** `master` ← **Head:** `skip-failing-test-suites` --- ### 📝 Commits (2) - [`c40b5e4`](https://github.com/actualbudget/actual/commit/c40b5e4d5dfd788564c992ae6acdc664f078efec) ci: run tests on github actions - [`5a49d65`](https://github.com/actualbudget/actual/commit/5a49d65b72791b51dfc3bf3cded833ae72e9d83d) test: skip failing test suites ### 📊 Changes **6 files changed** (+26 additions, -129 deletions) <details> <summary>View changed files</summary> ➖ `.circleci/config.yml` (+0 -121) ➕ `.github/workflows/test.yml` (+18 -0) 📝 `packages/loot-core/src/server/accounts/sync.test.js` (+2 -2) 📝 `packages/loot-core/src/server/accounts/transfer.test.js` (+1 -1) 📝 `packages/loot-core/src/server/main.test.js` (+3 -3) 📝 `packages/loot-core/src/server/sync/sync.test.js` (+2 -2) </details> ### 📄 Description Builds on top of #202 . We've got a number of test suites failing at the minute so the test CI isn't particularly helpful at the minute as every commit will fail. To avoid this masking new tests failing I feel we should skip these failing test suites until they're fixed. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 20:35:26 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
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/actual#3040
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?