Bug 913715

Summary: Scala script tool seems to be broken Fedora 17
Product: [Fedora] Fedora Reporter: tuxdna
Component: scalaAssignee: Geoff Reedy <geoff+fedora>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: geoff+fedora, jochen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 17:04:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description tuxdna 2013-02-21 21:25:26 UTC
Description of problem:

Script keeps waiting for some daemon to initialized and never ends.

Version-Release number of selected component (if applicable):

[tuxdna@tuxdna ~]$ scala -version
Scala code runner version 2.9.2-unknown-unknown -- Copyright 2002-2011, LAMP/EPFL
[tuxdna@tuxdna ~]$ uname -a
Linux tuxdna.in 3.6.6-1.fc17.x86_64 #1 SMP Mon Nov 5 21:59:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[tuxdna@tuxdna ~]$ cat /etc/issue
Fedora release 17 (Beefy Miracle)
Kernel \r on an \m (\l)


How reproducible:


Steps to Reproduce:
1. Created a /tmp/hello.scala file, as follows:

$ echo 'println("Hello world")' > /tmp/hello.scala

2. Run the script

$ scala /tmp/hello.scala

3. The script keeps waiting now for-ever.
  

Actual results:

The script keeps waiting.

Expected results:

Script should print "Hello world" on the terminal.

Additional info:

Adding -nc option is a workaround for now.

$ scala -nc /tmp/hello.scala
Hello world

Apparently the script creates a temporary folder and waits for a daemon to initialize:

In one terminal I again invoke the script ( without -nc ):

[tuxdna@tuxdna ~]$ scala /tmp/hello.scala

And in a separate terminal

[tuxdna@tuxdna ~]$ tail -f /tmp/scala-devel-tuxdna/output-redirects/scala-compile-server-err.log 
...starting server on socket 56891...
tail: /tmp/scala-devel-tuxdna/output-redirects/scala-compile-server-err.log: file truncated
...starting server on socket 54366...
tail: /tmp/scala-devel-tuxdna/output-redirects/scala-compile-server-err.log: file truncated
...starting server on socket 33801...
tail: /tmp/scala-devel-tuxdna/output-redirects/scala-compile-server-err.log: file truncated
...starting server on socket 43063...
tail: /tmp/scala-devel-tuxdna/output-redirects/scala-compile-server-err.log: file truncated
...starting server on socket 40844...
tail: /tmp/scala-devel-tuxdna/output-redirects/scala-compile-server-err.log: file truncated
...starting server on socket 51908...

Comment 1 Jochen Schmitt 2013-02-21 21:55:40 UTC
With scala-2.9.2-4.fc18 on Fedora 18 I could not reproduced
the reported issue.

Comment 2 Fedora End Of Life 2013-07-04 05:49:22 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2013-08-01 17:04:03 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.