# Nunit marking build as unstable, but not the stage

**URL:** <https://community.jenkins.io/t/nunit-marking-build-as-unstable-but-not-the-stage/9625>\
**Category:** Ask a question\
**Tags:** question\
**Created:** [September 15, 2023, 2:42pm UTC](https://community.jenkins.io/t/nunit-marking-build-as-unstable-but-not-the-stage/9625 "2023-09-15T14:42:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![michig54](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/michig54/32/5508_2.png) [@michig54](https://community.jenkins.io/u/michig54)\
**Post date:** [September 15, 2023, 2:42pm UTC](https://community.jenkins.io/t/nunit-marking-build-as-unstable-but-not-the-stage/9625/1 "2023-09-15T14:42:24Z")

</div>

Jenkins setup:

## Jenkins: 2.414.1 OS: Windows Server 2019 - 10.0 Java: 11.0.17 - Microsoft (OpenJDK 64-Bit Server VM)

ant:497.v94e7d9fffa\_b\_9  
antisamy-markup-formatter:162.v0e6ec0fcfcf6  
apache-httpcomponents-client-4-api:4.5.14-150.v7a\_b\_9d17134a\_5  
atlassian-bitbucket-server-integration:3.6.0  
authentication-tokens:1.53.v1c90fd9191a\_b\_  
basic-branch-build-strategies:81.v05e333931c7d  
blueocean:1.27.6  
blueocean-autofavorite:1.2.5  
blueocean-bitbucket-pipeline:1.27.6  
blueocean-commons:1.27.6  
blueocean-config:1.27.6  
blueocean-core-js:1.27.6  
blueocean-dashboard:1.27.6  
blueocean-display-url:2.4.2  
blueocean-events:1.27.6  
blueocean-git-pipeline:1.27.6  
blueocean-github-pipeline:1.27.6  
blueocean-i18n:1.27.6  
blueocean-jwt:1.27.6  
blueocean-personalization:1.27.6  
blueocean-pipeline-api-impl:1.27.6  
blueocean-pipeline-editor:1.27.6  
blueocean-pipeline-scm-api:1.27.6  
blueocean-rest:1.27.6  
blueocean-rest-impl:1.27.6  
blueocean-web:1.27.6  
bootstrap5-api:5.3.0-1  
bouncycastle-api:2.29  
branch-api:2.1122.v09cb\_8ea\_8a\_724  
build-discarder:139.v05696a\_7fe240  
build-timeout:1.31  
caffeine-api:3.1.8-133.v17b\_1ff2e0599  
checks-api:2.0.0  
cloudbees-bitbucket-branch-source:825.va\_6a\_dc46a\_f97d  
cloudbees-folder:6.848.ve3b\_fd7839a\_81  
command-launcher:107.v773860566e2e  
commons-lang3-api:3.13.0-62.v7d18e55f51e2  
commons-text-api:1.10.0-68.v0d0b\_c439292b\_  
copyartifact:714.v28a\_34f8c563f  
credentials:1271.v54b\_1c2c6388a\_  
credentials-binding:631.v861c06d062b\_4  
data-tables-api:1.13.5-1  
display-url-api:2.3.9  
durable-task:523.va\_a\_22cf15d5e0  
echarts-api:5.4.0-5  
email-ext:2.100  
envinject:2.908.v66a\_774b\_31d93  
envinject-api:1.199.v3ce31253ed13  
favorite:2.4.3  
font-awesome-api:6.4.0-2  
forensics-api:2.3.0  
generic-webhook-trigger:1.87.0  
git:5.2.0  
git-client:4.4.0  
git-forensics:2.0.0  
git-server:99.va\_0826a\_b\_cdfa\_d  
github:1.37.3  
github-api:1.314-431.v78d72a\_3fe4c3  
github-branch-source:1732.v3f1889a\_c475b\_  
github-pullrequest:0.5.0  
gradle:2.8.2  
handy-uri-templates-2-api:2.1.8-22.v77d5b\_75e6953  
htmlpublisher:1.32  
instance-identity:173.va\_37c494ec4e5  
ionicons-api:56.v1b\_1c8c49374e  
jackson2-api:2.15.2-350.v0c2f3f8fc595  
jakarta-activation-api:2.0.1-3  
jakarta-mail-api:2.0.1-3  
javadoc:243.vb\_b\_503b\_b\_45537  
javax-activation-api:1.2.0-6  
javax-mail-api:1.6.2-9  
jaxb:2.3.8-1  
jdk-tool:73.vddf737284550  
jenkins-design-language:1.27.6  
jjwt-api:0.11.5-77.v646c772fddb\_0  
jquery3-api:3.7.0-1  
jsch:0.2.8-65.v052c39de79b\_2  
junit:1217.v4297208a\_a\_b\_ce  
ldap:694.vc02a\_69c9787f  
lockable-resources:1185.v0c528656ce04  
mailer:463.vedf8358e006b\_  
matrix-auth:3.2  
matrix-project:808.v5a\_b\_5f56d6966  
maven-plugin:3.23  
mina-sshd-api-common:2.10.0-69.v28e3e36d18eb\_  
mina-sshd-api-core:2.10.0-69.v28e3e36d18eb\_  
nunit:394.v65c09a\_8408b\_a\_  
okhttp-api:4.11.0-157.v6852a\_a\_fa\_ec11  
pam-auth:1.10  
pipeline-build-step:505.v5f0844d8d126  
pipeline-github:2.8-147.3206e8179b1c  
pipeline-github-lib:42.v0739460cda\_c4  
pipeline-graph-analysis:202.va\_d268e64deb\_3  
pipeline-groovy-lib:671.v07c339c842e8  
pipeline-input-step:477.v339683a\_8d55e  
pipeline-milestone-step:111.v449306f708b\_7  
pipeline-model-api:2.2144.v077a\_d1928a\_40  
pipeline-model-definition:2.2144.v077a\_d1928a\_40  
pipeline-model-extensions:2.2144.v077a\_d1928a\_40  
pipeline-rest-api:2.33  
pipeline-stage-step:305.ve96d0205c1c6  
pipeline-stage-tags-metadata:2.2144.v077a\_d1928a\_40  
pipeline-stage-view:2.33  
pipeline-utility-steps:2.16.0  
plain-credentials:143.v1b\_df8b\_d3b\_e48  
plugin-util-api:3.3.0  
publish-over:0.22  
publish-over-ssh:1.25  
pubsub-light:1.17  
resource-disposer:0.23  
scm-api:676.v886669a\_199a\_a\_  
script-security:1271.vdede89739a\_81  
snakeyaml-api:1.33-95.va\_b\_a\_e3e47b\_fa\_4  
sse-gateway:1.26  
ssh-agent:333.v878b\_53c89511  
ssh-credentials:308.ve4497b\_ccd8f4  
ssh-slaves:2.916.vd17b\_43357ce4  
sshd:3.312.v1c601b\_c83b\_0e  
structs:325.vcb\_307d2a\_2782  
timestamper:1.26  
token-macro:384.vf35b\_f26814ec  
trilead-api:2.84.v72119de229b\_7  
variant:59.vf075fe829ccb  
workflow-aggregator:596.v8c21c963d92d  
workflow-api:1259.vb\_47f14fffc8a\_  
workflow-basic-steps:1042.ve7b\_140c4a\_e0c  
workflow-cps:3769.v8b\_e595e4d40d  
workflow-durable-task-step:1284.v4fcd365b\_75b\_e  
workflow-job:1341.vd9fa\_65f771dd  
workflow-multibranch:756.v891d88f2cd46  
workflow-scm-step:415.v434365564324  
workflow-step-api:639.v6eca\_cd8c04a\_a\_  
workflow-support:848.v5a\_383b\_d14921  
ws-cleanup:0.45

I have an nuint step to publish my nunit results. Everything here seems to work(test results are captured as expected) except when a test fails it doesnt mark the stage as unstable, only the build. So if I have multiple stages with nunit steps, I don’t know which one had the failure at a quick glance without diving in.

`nunit testResultsPattern: 'TestFile.xml', debug: false, keepJUnitReports: true, skipJUnitArchiver: false, failIfNoResults: true`

I have some junit steps that the are marking the build and stage as unstable as expected.  
`junit 'TEST-junit-jupiter.xml'`

Is this a known issue with nunit publisher or am I missing something/doing something wrong?

Thanks

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [September 18, 2023, 3:48pm UTC](https://community.jenkins.io/t/nunit-marking-build-as-unstable-but-not-the-stage/9625/2 "2023-09-18T15:48:44Z")

</div>

Hello @michig54 and welcome to this community. 👋

The `junit` plugin and the `nunit` plugin handle test results differently, which can result in variations in how they affect the build and stage status.

Here are a few things to consider:

1. **NUnit Plugin Behavior** : The `nunit` plugin for Jenkins primarily focuses on publishing NUnit test results for reporting purposes. It doesn’t inherently set the build or stage status based on test results. The `failIfNoResults` option in the `nunit` step only affects whether the build should be marked as failed if there are no test results found. It doesn’t control the build or stage status based on the test results.
2. **JUnit Plugin Behavior** : The `junit` plugin for Jenkins, on the other hand, is designed to work specifically with JUnit-style test reports. It has built-in logic to mark the build and stages as unstable or failed based on the test results. This behavior is specific to the `junit` plugin.

---

<div class="post-metadata">

**Author:** ![michig54](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/michig54/32/5508_2.png) [@michig54](https://community.jenkins.io/u/michig54)\
**Post date:** [September 18, 2023, 6:49pm UTC](https://community.jenkins.io/t/nunit-marking-build-as-unstable-but-not-the-stage/9625/3 "2023-09-18T18:49:09Z")

</div>

Interesting! Thanks for your reply!

Is there a recommended way to use the nunit results to mark the stages as unstable?

Thanks