Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Tests & Test failures

Hi Sergey,


Thanks for the contributions!

 

The “Papyrus-Test-Failures” jobs are “Known bugs/issues” (As opposed to “New regressions”). So, these jobs are more or less expected to be failing (Especially since some tests are implemented before the feature even exists, and sometimes the feature is not planned to be implemented yet)

 

In theory, all the tests in this Job should have a (Java) comment to explain why they are failing. In the case of Sequence Diagram Tests, I see the following reasons:

 

-          Platform-specific failures: the tests are e.g. designed for Windows, and fail on Linux.

o   Typical reason: They test the layout, and the default Font/Font size is different on different platforms, leading to different pixel positions

-          Invalid Test: The test is not properly implemented (i.e. it doesn’t mean something is actually broken @runtime)

o   Typical reason: The expected behavior has changed, or the test relies on a deprecated component. The test should be fixed/re-implemented

-          Failing Test: The test is properly implemented and is failing. There is probably something which needs to be fixed in the diagram

o   I see only one occurrence of such a bug in the Sequence Diagram Test Failures (org.eclipse.papyrus.uml.diagram.sequence.tests.bug.pro20130916.InteractionOperandStereotypesTest.testDisplayStereotypeWithBrace)

 

So… Nothing really urgent to fix, except maybe the last one.

 

Regards,
Camille

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Sergey Boyko
Envoyé :
vendredi 14 novembre 2014 12:57
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Tests & Test failures

 

Hi All,

 

We've submitted a couple of Gerrits ([1], [2], [3]) which remediate all failures related to sequence diagram for Mars (Papyrus-Master-Tests job configuration). 

 

There are still some test failures in Papyrus-Luna-Tests-Failures [4] and Papyrus-Master-Tests-Failures [5] job configurations related to sequence diagram. Should they also be investigated?

 

 

 

 

Best Regards,

  Sergey Boyko.

 

 

On Sat, Nov 8, 2014 at 1:17 AM, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Camille, team,

 

Also, bug 450536 [1] was reported for the memory leak regressions, which now also are fixed in both Luna SR2 and Mars branches.  These were unrelated to the StereotypeElementListener (obviously, as they happened in the Luna branch also).  They were introduced by a fix for undo/redo action availability in the Model Explorer.

 

This should clear up another eight test failures.  I can’t make any comment about the sequence diagram test failures (one in Luna branch and several more in Mars).

 

Cheers,

 

Christian

 


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=450536


On Nov 7, 2014, at 10:30 AM, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:

 

Hi,

 

 

The following bug has been reported and fixed:

 

450523: [Profiles] Performance bottleneck and exceptions in StereotypeElementListener

 

The Master test builds are now operational, and the tests for plugins/ shows 23 failures:

 

 

The extra-tests are still green

 

 

Regards,

Camille

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxxDe la part de LETAVERNIER Camille
Envoyé : vendredi 7 novembre 2014 12:58
À : Papyrus Project list
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Tests & Test failures

 

Hi all,


It seems that the test build is not « completely » frozen ; only “super-slow” (It’s been running for 1h30 in my computer, and only ~30% of the tests have been covered so far). I have a lot of exceptions related to the new Stereotype listener:

 

!ENTRY org.eclipse.emf.transaction 4 45 2014-11-07 12:53:26.607

!MESSAGE Uncaught exception during post-commit listener notifications

!STACK 0

java.lang.NullPointerException

       at org.eclipse.papyrus.uml.tools.listeners.StereotypeElementListener.handleFilteredNotification(StereotypeElementListener.java:157)

       at org.eclipse.papyrus.uml.tools.listeners.StereotypeElementListener.resourceSetChanged(StereotypeElementListener.java:88)

       at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl$1.run(TransactionalEditingDomainImpl.java:781)

       at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.runExclusive(TransactionalEditingDomainImpl.java:328)

       at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.postcommit(TransactionalEditingDomainImpl.java:771)

       at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.deactivate(TransactionalEditingDomainImpl.java:543)

       at org.eclipse.emf.transaction.impl.TransactionImpl.close(TransactionImpl.java:712)

       at org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:474)

       at org.eclipse.emf.workspace.AbstractEMFOperation.redo(AbstractEMFOperation.java:463)

       at org.eclipse.core.commands.operations.DefaultOperationHistory.doRedo(DefaultOperationHistory.java:357)

       at org.eclipse.core.commands.operations.DefaultOperationHistory.redo(DefaultOperationHistory.java:1110)

       at org.eclipse.papyrus.commands.CheckedOperationHistory.redo(CheckedOperationHistory.java:220)

       at org.eclipse.gmf.runtime.diagram.ui.parts.DiagramCommandStack.redo(DiagramCommandStack.java:366)

       at org.eclipse.papyrus.sysml.diagram.internalblock.tests.utils.TestUtils.defaultExecutionTest(TestUtils.java:742)

       at org.eclipse.papyrus.sysml.diagram.internalblock.tests.utils.TestUtils.setEncapsulationDeleteConnectorTest(TestUtils.java:591)

       at org.eclipse.papyrus.sysml.diagram.internalblock.tests.set.encapsulation.AbstractSetEncapsulationDeleteConnectorTest.setEncapsulationDeleteConnectorWithTargetProperty(AbstractSetEncapsulationDeleteConnectorTest.java:114)

 

And I had already noticed some (apparently major) performances issues with this new Listener (Although I wasn’t sure enough to raise a bug). The filter is invoked on absolutely all model notifications, so it is really important that extra care is brought to its performances (Especially, it shouldn’t have to load any resource, and it should never browse the model tree – only follow forward references. Not sure why it is so slow exactly, I haven’t investigated)

 

Camille

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxxDe la part de LETAVERNIER Camille
Envoyé : vendredi 7 novembre 2014 11:27
À : Papyrus Project list (mdt-papyrus.dev@xxxxxxxxxxx)
Objet : [PROVENANCE INTERNET] [mdt-papyrus.dev] Tests & Test failures

 

Hi all,

 

 

I would like to remind everyone that the Gerrit build only checks that everything compiles properly (plugins/ + extraplugins/), but currently doesn’t run any test. Thus, once your contribution has been accepted, please verify that the tests are still green:

 

 

And especially:

 

 

With the build failures for the last 3 days, a lot of contributions have been merged without being automatically tested, and we have a lot of regressions (Hopefully minor ones):

 

-          Luna-Tests has 9 failures, mainly Memory Leaks

-          Luna-Extra-Tests is still green

 

-          Master-Tests is frozen and cannot complete (And shortly before the failure, showed 5 new regressions)

-          Master-Extra-Tests is frozen and cannot complete

 

Frozen builds are difficult to debug online, so you probably need to run the test suites locally (~30-40 minutes). I will run a complete test suite and hopefully be able to give some more precise information regarding the failures.

 

 

Thanks,
Camille

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

 


Back to the top