You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Nicolas Lu (Jira)" <ji...@apache.org> on 2026/10/15 05:58:00 UTC

[jira] [Updated] (SPARK-60148) Cover first_spark_call from the shell entry point

     [ https://issues.apache.org/jira/browse/SPARK-60148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nicolas Lu updated SPARK-60148:
-------------------------------
    Summary: Cover first_spark_call from the shell entry point  (was: Add unit tests for pyspark.traceback_utils)

> Cover first_spark_call from the shell entry point
> -------------------------------------------------
>
>                 Key: SPARK-60148
>                 URL: https://issues.apache.org/jira/browse/SPARK-60148
>             Project: Spark
>          Issue Type: Test
>          Components: PySpark
>    Affects Versions: 4.4.0
>            Reporter: Nicolas Lu
>            Priority: Minor
>              Labels: pull-request-available
>
> Lines 41-42 of pyspark/traceback_utils.py (when first_spark_frame == 0 in first_spark_call()) are not exercised by existing tests because the test runner is normally at the bottom of the call stack.
> This ticket adds test_shell_reports_where_the_active_context_was_created to SparkSubmitTests in python/pyspark/tests/test_appsubmit.py to exercise the first_spark_frame == 0 branch via the real PySpark shell entry point (bin/pyspark -> shell.py) without mocks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org