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
Conversation
Does wrench pass this ? |
@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. |
Its ok. |
It would better to do the detection in make imho instead of passing an if-then-else to the shell. |
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 😄 |
Thats what the original change did, we computed a target name and made rcheck depend on it. |
16ea751
to
846ec71
Compare
@vargaz fixed. I just found the shell solution a bit clearer, but I don't care much about that. |
Looks ok. |
846ec71
to
cf24de8
Compare
[mini] Explicitly turn nunit output on or off based on variable Commit migrated from mono/mono@dc4aa9d
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?