Jenkins Testing failed after migrating to 2.121 LTS

[Pranav Kv]

Hi I am getting error in a maven build.
There is test fail after migrating jenkins to new server.. But no issues in the old jenkins instance

Error
Validation not trigger.. Expected(abcd.xml) but found()
Java assertion

COULD any please help me to resolve?
Regards
Pranav

[Jan Monterrubio]

Does the maven build only fail in Jenkins? 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b7ce0fa4-273f-4680-a8e7-c10fd7ba08d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Pranav Kv]

Yes. Recently we migrated jenkins to new LTS version 2.121. There is no issues in the older version which is running in on other server. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9K3ZjZQRkFxRTn68q6JynAyupKGV%2Bu5X0GC%2BnTtz%3DoN8w%40mail.gmail.com.

[Pranav Kv]

[Pranav Kv]

Still failing validation error in jenkins LTS 2.121..but no issue with 1.644

Java.lang.AssertionError: file abcd.xml validation rule not trigger, validation error found:[] expected [[abcd.xml]] but found [[]]

org.testing.Assert.fail(Aasert.java94))
org.testing.Assert.failNotEquals(Asser. Java:494)
org.testing.Assert.assertEqual(Assert.java:808)

[Pranav Kv]

Anyone can help on this? 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8a6efbb7-2868-4885-b4c7-ef9294ea4dde%40googlegroups.com.

[Pranav Kv]

Any updates? 

Thanks

[Mark Waite]

You'll need to provide significantly more details before anyone will be able to provide meaningful help.

Some of the questions that arose when I saw your description:

• Is that failure in a specific job or in every job?
• What are the characteristics of that job (if a specific job)?
• Do those tests fail when executed from the command line?
• Do those tests fail when executed from inside a Docker image defined to build and execute the tests?
• Since I've never seen an "org.testing.Assert" library, I assume there is either a typo in your stack trace or you're using a special library.  Is there a typo or are you using a special library?
• Can you duplicate the failure outside Jenkins?
• What JDK are you running in the failing environment?
• What JDK was running in the environment where it worked?
• Is this specific to a certain platform (Windows, Linux, FreeBSD, zLinux, etc.)

By posting minimal information and then repeatedly asking for a status update, you're not showing any indication that you've investigated the issue more deeply yourself, nor that you're willing to spend energy to investigate more deeply.

Persuade the people in the mailing list that you've investigated further by including detailed descriptions of the experiments you've attempted and the results of those experiments.  Describing your investigation will help you and will probably help others who encounter similar problems in the future.

Mark Waite

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAHwQEkKWUpubxR3Hj_yZL-4rs90s%2BsgNL7Bcij5YqhMD3_-yTA%40mail.gmail.com.