NEW PROVIDER: CNR (test)

[tlimoncelli]

No description provided.

[github-actions]

Changes detected by Check Git Status Action

[KaiSchwarz-cnic]

@tlimoncelli

I wonder as the tests passed multiple times yesterday evening and they still pass on my end.
Also I double checked if I am using either an outdated branch or having some uncommitted changes. Nothing applies.

...
--- PASS: TestDualProviders (3.83s)
=== RUN   TestNameserverDots
No nameservers found
=== RUN   TestNameserverDots/No_trailing_dot_in_nameserver
--- PASS: TestNameserverDots (0.11s)
    --- PASS: TestNameserverDots/No_trailing_dot_in_nameserver (0.00s)
PASS
ok      github.com/StackExchange/dnscontrol/v4/integrationTest  299.639s

this is how I am running them:

export CNR_ENTITY='OTE'
export CNR_UID='qmtest:REDACTED'
export CNR_PW='REDACTED'
export CNR_DOMAIN="dnscontroltest-cnr.com"
cd integrationTest
go test -v -failfast -verbose -provider CNR

Is there any difference between how the workflow runs the test vs. how we're manually doing that?
I am happy to work on all that, but how to get that reproduced?

[KaiSchwarz-cnic]

I also tried replicating what the workflow is doing:

no idea ...

[KaiSchwarz-cnic]

going for your branch now, maybe that's the difference finally ... hmm I have no access on that one in our fork.

I synced/updated our fork now and rebased our branch. Tests did still pass.

[github-actions]

Changes detected by Check Git Status Action