Skip to content

Fix dotnet9 eol and angular lockfile#1256

Merged
tnikolova82 merged 7 commits into
masterfrom
fix-dotnet9-eol-and-angular-lockfile
May 11, 2026
Merged

Fix dotnet9 eol and angular lockfile#1256
tnikolova82 merged 7 commits into
masterfrom
fix-dotnet9-eol-and-angular-lockfile

Conversation

@ivanovac
Copy link
Copy Markdown
Contributor

Use it.Pend instead of t.Skip for .NET Core 9 test t.Skip (even from it.Before) still triggers the outer it.After cleanup,
which calls platform.Delete.Execute on an org that was never initialized by platform.Deploy.Execute, causing 'No API endpoint set' failures.

it.Pend marks the spec as pending at registration time — no it.Before or it.After hooks fire for it at all, so cleanup is never attempted.

ivanovac added 7 commits May 8, 2026 20:48
When t.Skip is called inside an it body, runtime.Goexit() fires after
it.Before has already run and it.After is already deferred. The deferred
it.After then calls platform.Delete.Execute, but since platform.Deploy
was never called (we skipped before it), the per-test CF context is
uninitialized and cf delete-org fails with 'No API endpoint set'.

Moving t.Skip to it.Before is consistent with the SkipOnCflinuxfs3
pattern: when skip fires from it.Before, it.After has not yet been
registered and therefore does not run.
t.Skip (even from it.Before) still triggers the outer it.After cleanup,
which calls platform.Delete.Execute on an org that was never initialized
by platform.Deploy.Execute, causing 'No API endpoint set' failures.

it.Pend marks the spec as pending at registration time — no it.Before or
it.After hooks fire for it at all, so cleanup is never attempted.
The it.Before was removed when switching to it.Pend, but keeping it makes
the test self-contained: when the segfault is fixed and it.Pend is changed
back to it, no other edits are needed.
@tnikolova82 tnikolova82 merged commit 0eb1837 into master May 11, 2026
7 checks passed
@tnikolova82 tnikolova82 deleted the fix-dotnet9-eol-and-angular-lockfile branch May 11, 2026 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants