Cannot run inline script when shared library is loaded

[grzegorzgrzegorz]

Jenkins and plugins versions report

Environment

Paste the output here

What Operating System are you using (both controller, and any agents involved in the problem)?

Windows

Reproduction steps

Unable to run this test:

import com.lesfurets.jenkins.unit.BasePipelineTest
import org.junit.Before
import org.junit.Test

import static com.lesfurets.jenkins.unit.global.lib.LibraryConfiguration.library
import static com.lesfurets.jenkins.unit.global.lib.ProjectSource.projectSource

class TestingExamplesFromGithub extends BasePipelineTest {

    @Override
    @Before
    void setUp() throws Exception {
        super.setUp()

        def library = library().name('commons')
                .defaultVersion('<notNeeded>')
                .allowOverride(true)
                .implicit(true)
                .targetPath('<notNeeded>')
                .retriever(projectSource())
                .build()
        helper.registerSharedLibrary(library)
    }

    @Test
    void testSomeScript() throws Exception {
        def script = runInlineScript('''
            node {
                stage('Build') {
                    echo 'make'
                }
            }
        ''')


        printCallStack()
        assertJobStatusSuccess()
    }

}

Expected Results

Test is run, stack is displayed, assertion is made.

Actual Results

Test is hanging.

Anything else?

When library is not loaded, the test can be executed successfully.

[grzegorzgrzegorz]

What is this play with "bug" label about? Should it not be used at all? Could you explain it @nre-ableton ?

[nre-ableton]

I removed all labels except for "dependabot", which gets added automatically by the dependabot service by GitHub and can't be avoided. The labels weren't useful and just cluttered up the backlog.

[turboBasic]

I have encountered the same problem. Test which uses runScript('...') or runInlineScript('...') fails when library is loaded

[jiridanek]

I have one suggestion. Check the groovy version you have on your classpath. It should be

implementation('org.codehaus.groovy:groovy-all:2.4.21')

That's first because this ancient version is what Jenkins actually uses, and second, when I used 3.0.12, I saw a deadlock when loading a shared library, when the test was trying to compile the groovy. Also, this is what JenkinsPipelineUnit tests with.

JenkinsPipelineUnit has self tests for inlineScript functionality, https://github.com/RecuencoJones/JenkinsPipelineUnit/blob/master/src/test/groovy/com/lesfurets/jenkins/TestInlineScript.groovy so it is unlikely this will simply completely break.

[jiridanek]

One more note, are you using Java 11 when running tests? I found that (with groovy 3.0.13) the tests run on java 11 and get stuck the way described in this issue on 17. My colleagues were perfectly happy with that version of groovy and java 11.