fix-integration-tests #403
Labels
Clear labels
bug
build
ci/cd
critical fix
design
documentation
duplicate
easy-first-issue
enhancement
help wanted
i10n
i18n
installer
invalid
question
release
release-candidate
security
tech-debt
test
wontfix
Something is not working
go build related issues
Building things with CI/CD
https://docs.coopcloud.tech/federation/resolutions/passed/010/
UI/UX
Documenting all the things
This issue or pull request already exists
Something for new people to get stuck into. We hope it's easy!
New feature
Need some help
Everything to do with localisation
Everything to do with internationalisation
Everything to do with the install script.
Something is wrong
More information is needed
Release management
Related to the new release candidate
Security related
Unit/integration testing
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/abra#403
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In preparation for the new abra release, let's fix all integration tests
After merging, this needs to be cherry-picked into the release-0-9 branch.
bd21014fed)08232b74f6), has known regression coop-cloud/organising#5816e99b74c24)bd069d32f6)ad323ad2bd)81897bf4da)Thanks for this work! A few comments...
Also, several instances of shuffling the argument handling order which I think is related to coop-cloud/abra#404? Ideally, this shouldn't be necessary and we can pin and maintain the current behaviour. Possible changes to this can come in a new proposal.
@@ -9,3 +9,2 @@// Init inits a new repo and commits all the stuff if you wantfunc Init(repoPath string, commit bool) error {if _, err := gitPkg.PlainInit(repoPath, false); err != nil {func Init(repoPath string, commit bool, gitUser, gitEmail string) error {This seems like a behaviour change, not a fix? What error were you facing?
I wouldn't mind erroring out here in the case people don't have a
~/.gitconfiginstead of implementing this as additional flags? According to https://pkg.go.dev/github.com/go-git/go-git/v5#CommitOptions 👉 "If Author is empty the Name and Email is read from the config".We could also additionally document to support people to know how to do this inside of Git and not in Abra?
Yeah this is a behavior change. It is for the case when no author is set in the
~/.gitconfig. I think it is a nice addition but probably better to pull it out into a separate pull request@p4u1 yeh I'd say raise an issue and pull it out for now. We can loop back in another change.
Pulled it out into a seperate pull request coop-cloud/abra#405
Also opened a issue coop-cloud/organising#580
@@ -71,3 +71,3 @@run git -C "$ABRA_DIR/recipes/$TEST_RECIPE" statusassert_output --partial 'behind 3'assert_output --partial "Your branch is behind 'origin/main' by 3 commits"Seems a bit brittle, could we instead do a
assert_output --regexp 'behind .* 3 commits'? Because that is the main thing we're matching on. Not the branch name / remote and so on. I think this might save us revisiting mass-edits on this again in the near future.Same applies for the rest of the edits like this elsewhere.
Sound good, changed it
@@ -104,3 +104,3 @@run git -C "$ABRA_DIR/recipes/$TEST_RECIPE" statusrefute_output --partial 'behind 3'assert_output --partial "Your branch is up to date with 'origin/main'"assert_output --partial "up to date"?Sound good, changed it
@@ -108,0 +107,4 @@# TODO: should wait as long as volume is no longer in usesleep 10run $ABRA app volume rm "$TEST_APP_DOMAIN" --no-inputIsn't this covered by coop-cloud/abra#399 now?
It should be, but doesn't seem to work for me without the sleep. Can you check if it works for you without the sleep?
coop-cloud/organising#582
@@ -13,3 +13,3 @@@test "error if not present in catalogue" {run $ABRA recipe versions "$TEST_RECIPE"run $ABRA recipe versions "not-in-catalogue"Ah, this should be reverted because the
exampleshould never be in the catalogue but it can be cloned byabra. So the resulting error is now "can't clone", not "can't find in catalogue". I just realised I can't push to your fork so here is the diff:We are getting closer! Thanks for you feedback to my changes, I will take a closer look soon.
Also you should have edit rights now :)