Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mini] Explicitly turn nunit output on or off based on variable #3318

Merged
merged 1 commit into from Jul 22, 2016

Conversation

akoeplinger
Copy link
Member

Alternative implementation to 8f09214.

In CI we explicitly pass EMIT_NUNIT=1 to generate the nunit xml and run the check-seq-points tests, locally those are omitted. This avoids needing to sniff for Jenkins/Wrench variables.

@vargaz what do you think?

@vargaz
Copy link
Contributor

vargaz commented Jul 21, 2016

Does wrench pass this ?
It would be better if jenkins would pass CI=1 as well.

@akoeplinger
Copy link
Member Author

@vargaz we can change Wrench to pass it, but it does nothing with NUnit anyway. As I said, I'd prefer making it explicit when something happens differently on CI, instead of the Makefile somehow detecting it's run on CI.

@vargaz
Copy link
Contributor

vargaz commented Jul 21, 2016

Its ok.

@vargaz
Copy link
Contributor

vargaz commented Jul 21, 2016

It would better to do the detection in make imho instead of passing an if-then-else to the shell.

@akoeplinger
Copy link
Member Author

I tried this first, but since it is an automake file I can't use the normal ifeq checks I'd do in make, so this seemed like the easiest solution to me. If you know how to fight the automake dragon, please show me 😄

@vargaz
Copy link
Contributor

vargaz commented Jul 21, 2016

Thats what the original change did, we computed a target name and made rcheck depend on it.

@akoeplinger
Copy link
Member Author

akoeplinger commented Jul 21, 2016

@vargaz fixed. I just found the shell solution a bit clearer, but I don't care much about that.

@vargaz
Copy link
Contributor

vargaz commented Jul 21, 2016

Looks ok.

Alternative implementation to 8f09214.

In CI we explicitly pass EMIT_NUNIT=1 and check-seq-points to generate the nunit xml and run the tests,
locally those are omitted. This avoids needing to sniff for Jenkins/Wrench variables.

Same for a9eec21, but we already pass V=1 in Jenkins.
@akoeplinger akoeplinger merged commit dc4aa9d into mono:master Jul 22, 2016
@akoeplinger akoeplinger deleted the cleaner-mini-nunit branch July 22, 2016 12:20
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
[mini] Explicitly turn nunit output on or off based on variable

Commit migrated from mono/mono@dc4aa9d
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.

None yet

3 participants