Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6DD28200CCC for ; Fri, 21 Jul 2017 11:34:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6C78516CEDA; Fri, 21 Jul 2017 09:34:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B15F816CED9 for ; Fri, 21 Jul 2017 11:34:03 +0200 (CEST) Received: (qmail 3393 invoked by uid 500); 21 Jul 2017 09:34:02 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 3382 invoked by uid 99); 21 Jul 2017 09:34:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jul 2017 09:34:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D04D4C0166 for ; Fri, 21 Jul 2017 09:34:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 5LTYKSvUk9Vo for ; Fri, 21 Jul 2017 09:34:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D5DE75FCC6 for ; Fri, 21 Jul 2017 09:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 687BDE090E for ; Fri, 21 Jul 2017 09:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2220521EE4 for ; Fri, 21 Jul 2017 09:34:00 +0000 (UTC) Date: Fri, 21 Jul 2017 09:34:00 +0000 (UTC) From: "DM (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (SUREFIRE-1373) Tests annotated with @NotThreadSafe are not executed in isolation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 21 Jul 2017 09:34:04 -0000 [ https://issues.apache.org/jira/browse/SUREFIRE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096056#comment-16096056 ] DM edited comment on SUREFIRE-1373 at 7/21/17 9:33 AM: ------------------------------------------------------- Can someone let me know if my below understanding is correct or not after reading the documentation:- All the classes marked with {{@NotThreadSafe}} runs in a single thread one after another. This single thread executing {{@NotThreadSafe}} test classes runs after all the threads executing tests in parallel are finished. was (Author: tuk): What is the behavior are the classes marked with @NotThreadSafe running in a single thread after the all the parallel executions are finished? Can someone let me know if my below understanding is correct or not after reading the documentation:- All the classes marked with {{@NotThreadSafe}} runs in a single thread one after another. This single thread executing {{@NotThreadSafe}} test classes runs after all the threads executing tests in parallel are finished. > Tests annotated with @NotThreadSafe are not executed in isolation > ----------------------------------------------------------------- > > Key: SUREFIRE-1373 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1373 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin > Affects Versions: 2.20 > Reporter: Sebastian Kirsch > Assignee: Tibor Digana > Fix For: 2.20.1 > > > The [surefire documentation|http://maven.apache.org/components/surefire/maven-failsafe-plugin/examples/fork-options-and-parallel-execution.html] states that > bq. you can apply the JCIP annotation @net.jcip.annotations.NotThreadSafe on the Java class of JUnit test (pure test class, Suite, Parameterized, etc.) in order to execute it in single Thread instance. The Thread has name maven-surefire-plugin@NotThreadSafe and it is executed at the end of the test run. > However, the thread is run in parallel to the other tests being executed, which contradicts the documentation and defeats the purpose of running tests sequentially in a single thread. > See https://github.com/sebastiankirsch/surefire-nonthreadsafe for a test case. -- This message was sent by Atlassian JIRA (v6.4.14#64029)